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 heuristic models in `heuristic-test-design-reference` (SFDPOT, Whittaker attacks, FEW HICCUPPS, ISO 25010). 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.

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable instruction-only skill with clear sequencing, gating checkpoints, and a properly disclosed single reference file. Its only weakness is mild redundancy between the downstream-reconciliation step and the hand-off section, plus an over-long external links list.

Suggestions

Merge 'Step 4 - Reconcile with downstream skills' and the 'Hand-off targets' section into one block to remove the duplication.

Trim the external References list to the load-bearing sources (HTSM, DevelopSense, ISO 25010, Better Gherkin); drop the generic glossary/Wikipedia entries that the skill does not actually consume.

Consider moving the worked matrix rows into the existing references file alongside the heuristic walk to keep the overview leaner.

DimensionReasoningScore

Conciseness

The body is dense and operational with no concept padding, but 'Step 4 - Reconcile with downstream skills' overlaps the later 'Hand-off targets' section, and the eight-link external References list exceeds what the skill functionally needs.

2 / 3

Actionability

Provides concrete tooling columns, a complete observation-log template with real URL paths and HTTP status codes, and worked matrix rows (e.g. CHECKOUT-LIVE-07) with exact column definitions and confidence tags - effectively copy-paste ready.

3 / 3

Workflow Clarity

Five steps are clearly sequenced with explicit gates: observation log produced first, the Confidence column gating inferred cases to first-run probing, [unverified] tagging, and an Anti-patterns table acting as a checklist.

3 / 3

Progressive Disclosure

The body is an overview that signals one well-scoped one-level-deep reference, [references/heuristic-walk-example.md], which exists and matches its described purpose; no nested reference chains.

3 / 3

Total

11

/

12

Passed

Description

100%

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, third-person description that states concrete capabilities, names specific tools and heuristic models, and provides an explicit trigger clause for when to use it. It carves a distinct niche and contrasts cleanly with sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and tools ('Playwright trace / DevTools / accessibility tree') plus named heuristic models (SFDPOT, Whittaker attacks, FEW HICCUPPS, ISO 25010) and input modalities (URL, screen recording, screenshot, verbal brief).

3 / 3

Completeness

Explicitly answers both what ('produces a test-case matrix... by combining structured exploration with the heuristic models') and when ('Use when there is no story, no AC, and no documentation - only a live feature').

3 / 3

Trigger Term Quality

The 'Use when there is no story, no AC, and no documentation - only a live feature' clause plus 'live, undocumented feature' and the input-type list give good coverage of natural tester phrasings.

3 / 3

Distinctiveness Conflict Risk

Clear narrow niche (test-case matrix from a live undocumented feature) with explicit contrast against 'test-case-ideation-from-story' and 'not an exploratory session charter', making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

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