CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-case-from-live-feature

Build-an-X workflow that produces a test-case matrix from a **live, undocumented feature** - running app at a URL, screen recording, screenshot, or verbal brief - by combining structured exploration (Playwright trace / DevTools / accessibility tree) with the four canonical heuristic test-design models bundled in references/ (Bach's HTSM / SFDPOT product elements, Whittaker's How-to-Break-Software attacks, Bolton's FEW HICCUPPS consistency oracles, ISO/IEC 25010 quality characteristics). Output is a structured case matrix, not an exploratory session charter. Use when there is no story, no AC, and no documentation - only a live feature - or as the heuristic reference layer for zero-documentation test design.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

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

The content is a well-structured, highly actionable workflow with clear sequencing, validation checkpoints, and appropriate offloading of detail to verified bundle references. Its only weakness is length, with a few illustrative sections that could be tightened.

DimensionReasoningScore

Conciseness

The body is long but mostly load-bearing (observation log, matrix schema, worked rows, anti-patterns) with little concept-explanation padding; a few illustrative sections could be trimmed.

4 / 5

Actionability

Provides concrete tools, a full observation-log example, exact matrix column shapes with worked example rows, and explicit downstream-skill routing — fully executable guidance.

5 / 5

Workflow Clarity

A clearly sequenced 5-step workflow with explicit validation checkpoints ([verbal, unconfirmed] tagging, Confidence column gating automation, probe-then-confirm-or-falsify on first run) and anti-pattern failure modes.

5 / 5

Progressive Disclosure

Overview lives in SKILL.md while bulk detail (full heuristic catalog, full worked walk) is split into two one-level-deep, clearly-linked bundle files that both exist.

5 / 5

Total

19

/

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.

The description is concrete, comprehensive, and clearly signals both what the skill produces and when to invoke it. It distinguishes itself well from adjacent test-design skills. Minor tightening of natural trigger synonyms could push trigger_term_quality higher.

DimensionReasoningScore

Specificity

Multiple concrete actions are listed (produces a test-case matrix, structured exploration via Playwright trace / DevTools / accessibility tree, the four named heuristic models) with comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly states both what it does (build a test-case matrix from a live undocumented feature via structured exploration plus four heuristic models) and when to use it ('Use when there is no story, no AC, and no documentation').

5 / 5

Trigger Term Quality

Includes natural trigger phrases like 'no story, no AC, and no documentation' and 'live feature', but leans technical and misses some common synonyms a user might say.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (live, undocumented features only), explicitly distinguishes itself from exploratory session charters and story-driven skills, giving 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents