CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/test-case-ideation-from-story

Use for any question or task about turning a user story, ticket or spec into test cases, including one-line stories whose gaps QA finds only after coding. Produces a markdown test case matrix (id, title, precondition, steps, expected, tier) covering happy, alternate, boundary and negative paths, agreed before automation and ready for TestRail, Qase or Xray.

Quality

87%

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

81%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.

Highly actionable content with a clearly sequenced workflow, explicit halt-on-incomplete-input validation, and a concrete worked example that pins the output format. The main weakness is token efficiency: duplicated citation links, twice-repeated report statistics, and motivational overview padding that could be trimmed without losing instructional value.

Suggestions

Drop the duplicate References section or strip the inline URLs from the body, keeping each link in only one place - all seven references are currently listed twice.

Mention the PractiTest 2026 'shallow output' failure mode once (either Overview or Anti-patterns) instead of twice; the time-sensitive statistics (70%, 40.7%) add tokens without instructing the model.

Consider moving the per-tool CI/tracker integration details (Step 4) into a reference file to shorten SKILL.md, keeping only the one-line hand-off summary inline.

DimensionReasoningScore

Conciseness

The body is mostly dense and actionable, but the PractiTest 2026 statistics ("70% of teams already use AI... only 40.7%") appear twice as motivation and the References section re-lists all seven URLs already linked inline - more than the minor trimmable instances of anchor 4.

3 / 5

Actionability

The guidance is fully concrete: a 6-field extraction checklist, an equivalence-class table keyed by parameter type, an explicit boundary rule (min, min-1, max, max+1), a required-column spec, a complete 5-row worked example, and per-tool import instructions - copy-paste-ready for an instruction-only skill.

5 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with an explicit validation checkpoint and feedback loop ("If any of (1) - (5) is missing from the story, stop and request clarification"), plus anti-pattern review criteria that function as a post-hoc checklist on the emitted matrix.

5 / 5

Progressive Disclosure

Well-organized single file with clear section headers and a dedicated references list, and all links are external URLs (no nested or dead references); at ~130 lines it exceeds the under-50-line simple-skill exception, and nothing is split into separate files, so it matches anchor 4's 'good structure, minor organization gaps' rather than anchor 5's explicit split-and-navigate layout.

4 / 5

Total

17

/

20

Passed

Description

88%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 a concrete, well-scoped output artifact with explicit column structure and coverage paths, and opens with an explicit 'Use for' trigger clause naming the natural input terms. The only gaps are a few missing trigger synonyms (e.g., 'acceptance criteria') and unstated boundaries against adjacent automation skills.

DimensionReasoningScore

Specificity

"Produces a markdown test case matrix (id, title, precondition, steps, expected, tier) covering happy, alternate, boundary and negative paths, agreed before automation and ready for TestRail, Qase or Xray" names the concrete artifact, its columns, coverage dimensions, and downstream targets - comprehensive concrete actions with no significant gaps.

5 / 5

Completeness

"Use for any question or task about turning a user story, ticket or spec into test cases..." explicitly answers 'when' with concrete trigger phrases, and the artifact specification explicitly answers 'what' - both are present and explicit, matching anchor 5 rather than anchor 4's weaker 'when'.

5 / 5

Trigger Term Quality

"user story", "ticket", "spec", "test cases", "QA" are natural terms users would say, matching the anchor-4 example's coverage level; common variations like "acceptance criteria", "three amigos", or "test plan" are missing, so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The story-to-test-case-matrix niche is mostly distinct with clear triggers, but sibling test-authoring skills (Gherkin generation, test-code generation) occupy adjacent trigger territory and the description does not fence them off - minor overlap risk per anchor 4 rather than anchor 5's minimal conflict.

4 / 5

Total

18

/

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