CtrlK
BlogDocsLog inGet started
Tessl Logo

qa-testing

Run QA testing on a page, feature, or full site at one of three depth tiers (smoke, standard, full). Use this skill whenever the user asks to QA a page or site, run a smoke test after a deploy, verify a page before launch, or run a regression sweep. Triggers on QA, QA sweep, smoke test, regression test, post-deploy check, pre-launch check, verify the deploy, test this page, does the page render, broken link, 404, image not loading. Also triggers proactively after a deploy or a new page launch where verification matters. Covers accessibility, performance, and SEO at the surface-signal level only: deep audits belong to `accessibility-audit`, `performance-optimization`, and `seo-technical`, and code-level debugging to `code-review-web`.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, code-driven QA skill with executable snippets, concrete pass criteria, and a clean tiered structure. The main improvement room is minor prose trimming and making the smoke-failure retry loop more explicit.

DimensionReasoningScore

Conciseness

The body is mostly lean: executable snippets, checklists, and pass criteria with little explanation of concepts Claude already knows. A few prose asides (e.g. the hardcoded contrast '#FFFFFF'/'#9CA3AF' example comments and tier taglines) could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Provides copy-paste-ready executable JavaScript console snippets for every tier and each specific QA task (image audit, heading hierarchy, contrast, forms, external links), with concrete numeric pass criteria covering the common cases.

5 / 5

Workflow Clarity

A clear six-step sequenced workflow with an explicit checkpoint ('If any of these fail, do not proceed with deeper testing until the smoke issue is fixed') and a fix-or-file known-issue rule. It stops short of the explicit validate->fix->retry loop pattern that defines a 5.

4 / 5

Progressive Disclosure

SKILL.md serves as a well-sectioned overview with the only bundle file, references/qa-report-template.md, kept one level deep and clearly signaled via markdown links in the Workflow, Output format, and Reference files sections; the referenced file exists and is appropriately split out.

5 / 5

Total

18

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states what the skill does, when to use it, and how it differs from adjacent specialist skills. Trigger coverage is comprehensive and uses natural user phrasing.

DimensionReasoningScore

Specificity

Names the domain ('QA testing on a page, feature, or full site') and several concrete actions (smoke test, verify before launch, regression sweep) across three explicit depth tiers, with only minor coverage gaps versus a fully comprehensive action list.

4 / 5

Completeness

Explicitly answers both what ('Run QA testing ... at one of three depth tiers (smoke, standard, full)') and when ('Use this skill whenever the user asks to QA ...', 'Triggers on ...', 'Also triggers proactively after a deploy ...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Lists a comprehensive set of natural phrases users actually say ('QA', 'smoke test', 'regression test', 'post-deploy check', 'pre-launch check', 'verify the deploy', 'test this page', 'does the page render', 'broken link', '404', 'image not loading'), including synonyms and specific failure signals.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear QA niche with distinct triggers and explicitly carves out boundaries ('deep audits belong to `accessibility-audit`, `performance-optimization`, and `seo-technical`, and code-level debugging to `code-review-web`'), minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.