test-case-reducer
Shrinks a failing test input to its minimal form while preserving the failure — delta debugging and structured shrinking to find the smallest input that still triggers the bug. Use when a fuzzer or property test finds a failure with a huge input, when a bug report has an unwieldy reproduction, or when you need a minimal test case for a regression suite.
Install with Tessl CLI
npx tessl i github:santosomar/general-secure-coding-agent-skills --skill test-case-reducer100
Quality
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Discovery
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.
This is an excellent skill description that hits all the marks. It clearly articulates the specific capability (test input shrinking/minimization), uses appropriate technical terminology that developers would naturally use, and provides explicit trigger scenarios via a well-structured 'Use when' clause. The description is concise yet comprehensive, establishing a distinct niche that won't conflict with other testing or debugging skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Shrinks a failing test input to its minimal form', 'delta debugging', 'structured shrinking', 'find the smallest input that still triggers the bug'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Shrinks a failing test input to its minimal form while preserving the failure') AND when with explicit 'Use when' clause covering three distinct scenarios: fuzzer failures, unwieldy bug reports, and regression suite needs. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'fuzzer', 'property test', 'failure', 'huge input', 'bug report', 'reproduction', 'minimal test case', 'regression suite', 'delta debugging', 'shrinking'. These are terms developers naturally use when facing this problem. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on test input minimization/shrinking. The combination of 'delta debugging', 'shrinking', 'minimal test case', and 'fuzzer' creates a clear, unique domain unlikely to conflict with general testing or debugging skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill document that demonstrates mastery of concise technical writing. It efficiently teaches test case reduction through concrete examples, executable code, and clear workflows. The worked example is particularly valuable, showing exactly how structured shrinking reveals the bug, and the 'Do not' section addresses common pitfalls without being preachy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely efficient use of tokens. No unnecessary explanations of basic concepts - jumps straight into the interestingness test, algorithm, and practical examples. Every section earns its place with actionable content. | 3 / 3 |
Actionability | Provides executable Python code for the interestingness test, clear pseudocode for ddmin algorithm, concrete shrink operations tables, a complete worked example with step-by-step reduction, and specific tool recommendations. Copy-paste ready where appropriate. | 3 / 3 |
Workflow Clarity | The worked example provides an explicit step-by-step sequence with validation at each step (checking 'still interesting?'). The output format includes verification requirements. The 'Do not' section explicitly addresses validation gaps and checkpointing. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections progressing from concept (interestingness test) → algorithm (ddmin) → optimization (structured shrinking) → example → tools → edge cases → output format. Appropriate length for a single file with no need for external references. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.