Skills testing-qa
📦
testing-qa
v1.0.0 Content revision r1 Safe ⚙️ External commands
Coordinate Testing and QA Workflows
Teams often miss quality gaps when testing work is split across tools. This skill organizes unit, integration, E2E, browser, performance, and review workflows.
Supports: Claude Codex Code(CC)
This skill is part of a pack
Install the whole pack to get every skill the task needs, in one command.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "testing-qa" from https://skillstore.io/skills/sickn33-testing-qa.md and its manifest at https://skillstore.io/api/skills/sickn33-testing-qa/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "testing-qa". Plan QA for a new user registration feature.
Expected outcome:
- Recommended phases: strategy, unit tests, integration tests, E2E tests, browser checks, and release gates.
- Key checks: validation rules, API errors, account creation flow, responsive screens, and coverage threshold.
- Gate result: release is ready only after tests pass, review is complete, and linting is clean.
Using "testing-qa". Prepare browser testing for a marketing site launch.
Expected outcome:
- Recommended browser tasks: headless checks, screenshot review, visual regression, and responsive layout verification.
- Safety note: capture only approved test pages and avoid pages with private customer data.
- Gate result: publish after screenshots are reviewed and critical paths pass on supported viewports.
Using "testing-qa". Create release quality gates for an API service.
Expected outcome:
- Recommended gates: unit coverage, integration paths, mocked external services, performance benchmark, security scan, and code review.
- Required evidence: passing test report, benchmark summary, review approval, and clean lint result.
- Gate result: block release when a critical path, security scan, or benchmark fails.
Security Audit
Safev5 • 7/9/2026 Open versioned report
All Ruby shell backtick findings are false positives caused by Markdown inline code and fenced prompt text in SKILL.md. The screen-capture and system-reconnaissance blocker findings lack malicious context: one is a QA screenshot prompt and one is a testing pyramid diagram. No prompt injection, data exfiltration intent, or hidden abuse was found.
1
Files scanned
232
Lines analyzed
0
Review items
0
False positives ignored
Risk Factors
⚙️ External commands (50)
SKILL.md:32 SKILL.md:33 SKILL.md:43-45 SKILL.md:45-47 SKILL.md:47-49 SKILL.md:49-54 SKILL.md:54-55 SKILL.md:55-56 SKILL.md:56-57 SKILL.md:57-67 SKILL.md:67-69 SKILL.md:69-71 SKILL.md:71-73 SKILL.md:73-75 SKILL.md:75-77 SKILL.md:77-82 SKILL.md:82-83 SKILL.md:83-93 SKILL.md:93-95 SKILL.md:95-100 SKILL.md:100-101 SKILL.md:101-102 SKILL.md:102-112 SKILL.md:112-114 SKILL.md:114-116 SKILL.md:116-118 SKILL.md:118-123 SKILL.md:123-124 SKILL.md:124-125 SKILL.md:125-135 SKILL.md:135-137 SKILL.md:137-139 SKILL.md:139-141 SKILL.md:141-146 SKILL.md:146-147 SKILL.md:147-148 SKILL.md:148-158 SKILL.md:158-160 SKILL.md:160-165 SKILL.md:165-166 SKILL.md:166-167 SKILL.md:167-168 SKILL.md:168-178 SKILL.md:178-180 SKILL.md:180-182 SKILL.md:182-184 SKILL.md:184-189 SKILL.md:189-190 SKILL.md:190-200 SKILL.md:200-202
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-testing-qa/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-testing-qa?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-testing-qa?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-testing-qa/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-testing-qa.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). testing-qa security audit report (audit version 5) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/sickn33-testing-qa/audits/5BibTeX citation
@techreport{sickn33-sickn33-testing-qa-2026,
author = {sickn33},
title = {testing-qa security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-testing-qa/audits/5},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "testing-qa security audit report (audit version 5)"
version: "1.0.0"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/sickn33-testing-qa/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-testing-qa:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
100
Maintainability
87
Content
69
Community
83
Spec Compliance
What You Can Build
Set Up a Test Plan
Create a phased testing plan before a new project or major feature starts.
Build Web App QA Coverage
Coordinate unit, integration, E2E, browser, visual, and responsive testing for a web application.
Prepare Release Quality Gates
Define release checks for coverage, performance, security scans, code review, and linting.
Try These Prompts
Create a QA Checklist
Use the testing-qa workflow to create a checklist for a small web app release. Include unit, integration, E2E, and lint checks.
Plan Test Coverage
Use the testing-qa workflow to plan test coverage for a new API feature. Include fixtures, mocks, integration paths, and CI gates.
Coordinate Browser QA
Use the testing-qa workflow to coordinate browser automation, visual checks, screenshots, and responsive testing for a checkout flow.
Design Release Gates
Use the testing-qa workflow to design release quality gates for a production service. Include coverage, E2E, performance, security, and review criteria.
Best Practices
- Confirm each referenced helper skill is installed and trusted before use.
- Run tests in isolated environments with test data, not production accounts.
- Tie every quality gate to a measurable result or reviewer decision.
Avoid
- Using this workflow as a substitute for project-specific test design.
- Capturing browser screenshots on pages with secrets or customer data.
- Approving releases from generated plans without running the actual tests.
Frequently Asked Questions
Does this skill write test code automatically?
No. It coordinates testing phases and prompts. Separate testing skills or manual work create the actual tests.
Can it support both frontend and backend testing?
Yes. It covers unit, integration, API, E2E, browser, performance, and release quality checks.
Does it require other skills to work well?
Yes. The workflow references specialized helper skills, so availability depends on the user environment.
Is it safe to use with production data?
Use test data where possible. Browser screenshots and automation should avoid secrets and customer information.
Can it define release gates?
Yes. It includes checks for coverage, passing tests, E2E paths, benchmarks, scans, review, and linting.
Which tools can use this skill?
The report lists support for Claude, Codex, and Claude Code.