Name: testland/state-transition-test-design
Rating: 78.60000000000001 (1 reviews)
Author: testland

testland/state-transition-test-design

Derives human-readable manual test cases from stateful behavior: identify states, events, transitions, and guard conditions, draw the state table including invalid (empty-cell) transitions, choose a coverage level (all states, valid transitions / 0-switch, transition pairs / 1-switch per Chow, all transitions including invalid ones), then derive one test case per coverage item as an event sequence with per-step expected states (ISTQB CTFL v4.0 section 4.2.4). A deep single-technique walkthrough rather than a broad multi-lens case matrix; the output is manual step/expected cases rather than parameterized test code, and it covers how cases are derived rather than how a case record is structured. Use for lifecycle entities (accounts, orders, subscriptions), workflows, and UI wizards where the response to an event depends on the current state.

0.81x

Quality

93%

Does it follow best practices?

Impact

77%

0.81x

Average score across 10 eval scenarios

Securityby

Passed

No findings from the security scan

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.

A thorough, well-sequenced walkthrough of a single test-design technique with a consistently worked example and clear navigation. The main opportunity is trimming the repeated syllabus quotations and link restatements to tighten token efficiency.

Suggestions

Reduce repeated ISTQB/CTAL-TA syllabus quotations to short cited phrases and cite the section once, rather than re-quoting and re-linking the PDF in nearly every step.

Consolidate the fetch dates and PDF links into the References section instead of restating them inline in Step 1, Step 2, Step 3, Step 4, and Step 5.

Consider moving the full TC-ST-1/2/3 case tables into a reference file so the body reads as an overview, since the skill already points to manual-test-script-author for expansion.

Dimension	Reasoning	Score
Conciseness	Dense and mostly assumes Claude's competence, but it repeatedly embeds long ISTQB/CTAL-TA syllabus quotations and re-states PDF links every step, which adds tokens a reader could do without.	4 / 5
Actionability	Carries one worked example (account lockout) through all five steps with concrete state tables, labeled transitions, and fully worked test cases (TC-ST-1/2/3, TC-INV-1/2, TC-SW-1) showing action and expected observable state - copy-paste-ready guidance for an instruction-only skill.	5 / 5
Workflow Clarity	Five-step sequence (identify -> draw table -> choose coverage -> derive cases -> add invalid tests) with explicit checkpoints: coverage percentages computed, defect-masking warning, anti-patterns table, and a 'Why 1-switch catches what 0-switch misses' feedback section.	5 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent); the body is well split into Overview, When to use, Steps 1-5, Anti-patterns, Limitations, and References, with one-level-deep sibling-skill references (decision-table-test-design, manual-test-script-author) clearly signaled.	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.

A strong, specific description that clearly states the technique's actions, coverage levels, and trigger domains while distinguishing it from neighboring skills. It could nudge trigger_term_quality to 5 by foregrounding a few more colloquial synonyms, but it is otherwise exemplary.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions - 'identify states, events, transitions, and guard conditions', 'draw the state table', 'choose a coverage level', 'derive one test case per coverage item as an event sequence' - with comprehensive coverage of the technique.	5 / 5
Completeness	Explicitly answers both what ('Derives human-readable manual test cases from stateful behavior') and when ('Use for lifecycle entities (accounts, orders, subscriptions), workflows, and UI wizards where the response to an event depends on the current state') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('state transition', 'state machine', 'state table') plus concrete lifecycle entity examples (accounts, orders, subscriptions, workflows, UI wizards), though the language leans somewhat academic/ISTQB-coded.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (stateful behavior / state machines) and explicitly contrasts with sibling skills decision-table-test-design and test-case-ideation-from-story, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Reviewed

13 days ago

Table of Contents

Discovery Implementation Validation