CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/test-case-anatomy-reference

Use when writing a test case template, reviewing a batch of test cases for quality, or migrating cases between tools. Lists the ISO/IEC/IEEE 29119-3 and ISTQB test case fields, maps them to TestRail, Xray, Zephyr Scale, Allure TestOps and Qase, and gives a PASS, WEAK or FAIL review rubric.

Quality

91%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%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 strong pure-reference skill: the nine-field anatomy, cardinality table, and the Gate 0 + per-axis/set-axis rubric are directly usable decision-time content, with heavy detail correctly offloaded to two well-signaled reference files. The main cost is token redundancy — the anti-patterns, common-mistakes, conventions, and judgment-calls sections restate each other, and glossary quotes are reproduced in full.

Suggestions

Merge the Anti-patterns table with the 'Common mistakes' column of the nine-fields table — implicit preconditions, generic inputs, combined steps, and missing per-step results appear in both — keeping only entries unique to each.

State the A6 missing-vs-stale distinction once (in the axes table) and drop either the dedicated 'A6 note' paragraph or the repeating 'Judgment calls' bullet.

In the rubric's Basis column, cite ISTQB term names with a single link instead of reproducing full glossary quotations with inline URLs in every row.

DimensionReasoningScore

Conciseness

The body is information-dense with no basic-concept padding, but there is real redundancy: the anti-patterns table repeats ~5 entries from the nine-fields "Common mistakes" column (implicit preconditions, generic inputs, combined steps, missing per-step results), the A6 missing-vs-stale rule is stated three times (axis table, dedicated note, judgment calls), and full ISTQB glossary quotations with inline URLs inflate the Basis column. This fits "mostly efficient but could be tightened" better than the "minor instances" of the 4 anchor.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: each axis has a PASS bar and FAIL trigger with quoted concrete examples ("Applies a 10 percent coupon to the subtotal before tax"), Gate 0 is an explicit pre-scoring checklist, verdict derivation is mechanical (worst axis, never average), and the inline worked example walks a real draft case field by field through to the TestRail mapping. Specific examples cover the common cases.

5 / 5

Workflow Clarity

"How to use" gives a 7-step authoring sequence that ends in an explicit checkpoint ("Run the draft past the anti-patterns table; fix any match before the case is considered done"), and the review workflow has explicit validation (Gate 0 before any axis verdicts), a feedback loop (UNSCORABLE cases returned to the author with the missing field named), and checklists for the complex process. Checkpoints and recovery loops are explicit, not implicit, so it matches the 5 anchor over 4.

5 / 5

Progressive Disclosure

Two real, verified one-level-deep references — references/tracker-schema-map.md and references/review-rubric-worked-examples.md — each clearly signaled with when-to-consult guidance ("Consult it when migrating cases between tools or writing to a specific tracker's fields"). The bulk per-tracker field maps and extended rubric re-scoring examples are split out, and both reference files point back to the parent SKILL.md rather than nesting deeper, so navigation is easy.

5 / 5

Total

18

/

20

Passed

Description

92%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 description: it states what the skill contains (field list, tracker mapping, PASS/WEAK/FAIL rubric), when to use it via three explicit trigger scenarios, and names the five target trackers. The only gap is a few missing natural synonyms such as "test suite" or "test management".

DimensionReasoningScore

Specificity

Names three concrete deliverables — "Lists the ISO/IEC/IEEE 29119-3 and ISTQB test case fields", "maps them to TestRail, Xray, Zephyr Scale, Allure TestOps and Qase", "gives a PASS, WEAK or FAIL review rubric" — each with named standards, tools, and outputs. Coverage of the skill's functions is complete rather than leaving minor gaps, so it matches the top anchor better than 4.

5 / 5

Completeness

Opens with an explicit "Use when..." clause listing three concrete trigger scenarios, then answers 'what' with the field list, the five-tracker mapping, and the review rubric. Both what and when are explicit with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"writing a test case template", "reviewing a batch of test cases for quality", "migrating cases between tools", plus all five tracker names are phrases users would naturally say. Common synonyms like "test suite", "test management", or "QA review" are missing, which keeps it just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — test case anatomy, quality review, and tracker migration for five named tools — and triggers like "test case template" or "TestRail" are unlikely to fire an unrelated skill. Minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page