Name: testland/decision-table-test-design
Rating: 74.4 (1 reviews)
Author: testland

testland/decision-table-test-design

Derives human-readable manual test cases from a business-rule spec via a decision table: identify conditions and actions, build the full 2^n-column matrix, collapse columns with irrelevant entries, strike infeasible combinations, then emit one test case per remaining column (each feasible column is one coverage item per ISTQB CTFL v4.0 section 4.2.3). 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 when a spec's outcome depends on interacting conditions (pricing, eligibility, discounts, routing rules) rather than the boundaries of a single input.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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, actionable derivation skill with a clear five-step workflow, explicit validation/feedback checkpoints, and proper progressive disclosure to a real reference file. The only weakness is mild verbosity from repeated syllabus quoting and example commentary that could be trimmed.

Suggestions

Trim repeated verbatim ISTQB quotes and commentary like 'already smell' to tighten the body without losing the technique — paraphrase once and cite §4.2.3 afterward.

Move the full 8-column intermediate table (or the verbatim syllabus quotes) into the existing reference file, keeping the body focused on the collapsed final table and the test cases.

The dated reference note ('fetched 2026-06-10') and version revision date are time-sensitive; consider consolidating them into the References section only to avoid penalizing conciseness elsewhere.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence, but the repeated verbatim syllabus quotes, the extended worked-example prose, and phrases like 'already smell' add length beyond what the technique requires; it could be tightened without losing clarity.	2 / 3
Actionability	Provides concrete, copy-ready guidance throughout — notation definitions, a fully built 8-column table, a collapsed 5-column table, and a complete test-case table with setup/action/expected — exactly executable instruction for an instruction-only skill.	3 / 3
Workflow Clarity	Sequenced as Steps 1–5 with explicit checkpoints: flag `?` in Step 2, hold merges in Step 3 pending Step 4, delete infeasible columns, and add an external constraint check; feedback loop for a failing constraint check is present, matching the score-3 anchor.	3 / 3
Progressive Disclosure	The body is a concise overview that offloads the extended-entry/anti-pattern detail to a real one-level-deep file, signaled as [references/decision-table-details.md](references/decision-table-details.md), which exists; navigation is clear and content is appropriately split.	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 pairs a precise multi-step action sequence with an explicit 'Use when' trigger and positive distinctiveness framing against sibling skills. It is dense but every clause earns its place; no over-claims or vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions sequentially — 'identify conditions and actions, build the full 2^n-column matrix, collapse columns with irrelevant entries, strike infeasible combinations, then emit one test case per remaining column' — matching the score-3 anchor of several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what it does ('Derives human-readable manual test cases...via a decision table') and when to use it ('Use when a spec's outcome depends on interacting conditions'), with an explicit 'Use when' clause, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Surfaces natural terms a user would say — 'decision table', 'business-rule spec', 'pricing, eligibility, discounts, routing rules' — giving good coverage of phrasings users actually invoke, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche — 'A deep single-technique walkthrough rather than a broad multi-lens case matrix' and 'manual step/expected cases rather than parameterized test code' — actively distinguishing it from sibling skills, so it is unlikely to trigger for the wrong skill.	3 / 3
	Total	12 / 12 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

3 days ago

Table of Contents

Discovery Implementation Validation