CtrlK
BlogDocsLog inGet started
Tessl Logo

qa-review

QA review for code changes — test coverage analysis, edge case identification, test plan generation, regression detection, test health tracking over time.

60

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/qa-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 well-structured, actionable instruction-only skill with clear templates and a sound methodology sequence. The main gap is the absence of explicit validation/recovery checkpoints in the review workflow, which holds workflow clarity at 3.

Suggestions

Add an explicit validation/review checkpoint step (e.g., verify findings against the actual diff before emitting the output format) to lift workflow clarity above 3.

Specify how test-health metrics are computed and persisted (e.g., where the weekly retro reads them from) to strengthen actionability.

Consider moving the detailed test-health metrics or signal-integration details into a one-level-deep reference file to push progressive disclosure toward 5.

DimensionReasoningScore

Conciseness

The body is mostly efficient — tight bullet lists and ready-to-use templates assume Claude's competence, with only minor phrasing that could be trimmed.

4 / 5

Actionability

Concrete output-format templates, a specific edge-case taxonomy, and a test-plan template give mostly executable guidance, though test-health metric computation/storage is left implicit.

4 / 5

Workflow Clarity

The five numbered methodology steps provide a clear sequence, but there are no explicit validation checkpoints or error-recovery loops in the review workflow.

3 / 5

Progressive Disclosure

A single self-contained file with well-organized sections and no nested references; minor organization gaps keep it just below the top anchor.

4 / 5

Total

15

/

20

Passed

Description

71%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 specific, capability-rich description with strong trigger terms, but it omits an explicit 'when to use' clause, which caps completeness. Adding a 'Use when...' sentence would lift the completeness and overall score.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when reviewing code changes for test coverage, edge cases, or regression risk before merging.') to satisfy the completeness anchor.

Include a couple of natural synonym phrases (e.g., 'testing review', 'quality check') to push trigger-term coverage toward comprehensive.

Keep the concrete action list as-is — it already hits the specificity ceiling.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'test coverage analysis', 'edge case identification', 'test plan generation', 'regression detection', 'test health tracking' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

The 'what' is clear, but there is no explicit 'Use when...' clause; per the judging guidelines a missing when-trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like 'QA review', 'test coverage', 'edge cases', and 'regression' appear, but a few common variations/synonyms are missing, so it sits just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The QA/testing niche is distinct with specific triggers and only minor overlap risk with general code-review skills.

4 / 5

Total

16

/

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
nearai/ironclaw
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.