CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-case-ideation-from-story

Takes a user story or feature spec and emits a markdown test-case matrix - one row per case (id, title, precondition, steps, expected, tier) covering happy path, alternate paths, boundaries, and negative paths - before any test code is written. Output is the human-reviewable matrix that goes into TestRail / Qase / Xray. Emits the human-reviewable case matrix itself - not Gherkin scenarios written against locked acceptance criteria, and not executable test code. Use as the first artifact a manual tester or three-amigos session produces from a story, ahead of automation.

92

Quality

92%

Does it follow best practices?

Impact

Average score across 10 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

88%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 high-quality, actionable QA skill body with clear sequenced workflow, validation checkpoints, and concrete examples. Conciseness is good with minor trim opportunities, and progressive disclosure is solid though entirely single-file.

Suggestions

Trim the PractiTest 70%/40.7% statistic sentence in the Overview to one clause; the failure-mode point stands without the full citation.

De-duplicate the 'human-reviewable matrix' phrasing which appears in both the Overview and the description to save tokens.

Consider extracting the full worked-example matrix and the per-tool CI integration details into a references/ file, keeping SKILL.md as an overview that signals one-level-deep references.

DimensionReasoningScore

Conciseness

Efficient and mostly lean, assuming Claude's competence; the PractiTest stat sentence and repeated "human-reviewable matrix" phrasing could be trimmed, but no padded explanations of basic concepts.

4 / 5

Actionability

Fully actionable: required column table, a complete worked example matrix, concrete integration endpoints/commands (TestRail CSV import, Qase cases/bulk), and explicit per-lens generation instructions.

5 / 5

Workflow Clarity

Clear Step 1-4 sequence with an explicit validation checkpoint ("If any of (1)-(5) is missing... stop and request clarification") and an anti-patterns table that functions as a feedback/checklist for error recovery.

5 / 5

Progressive Disclosure

Well-sectioned single-file skill with clearly signaled external reference URLs; no nested file references. Not a 5 because no bundle files exist and the inline worked-example table and integration details could arguably live in separate reference files.

4 / 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 tightly scoped, trigger-rich description that clearly states what it produces and when to use it while distinguishing itself from adjacent QA skills. The only minor gap is synonym/extension trigger coverage, which is largely N/A for this process-oriented skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("emits a markdown test-case matrix - one row per case (id, title, precondition, steps, expected, tier) covering happy path, alternate paths, boundaries, and negative paths") with comprehensive coverage of the output shape.

5 / 5

Completeness

Explicitly answers both what ("emits a markdown test-case matrix...") and when ("Use as the first artifact a manual tester or three-amigos session produces from a story, ahead of automation") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keyword coverage ("user story", "feature spec", "test-case matrix", "TestRail / Qase / Xray", "three-amigos", "manual tester", "Gherkin") but a few synonymous trigger phrases are absent and no file-extension triggers apply to this process-oriented skill.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers; explicitly differentiates from Gherkin scenarios ("not Gherkin scenarios written against locked acceptance criteria") and executable test code, minimizing 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents