BD tdd-guide
Guide red-green-refactor TDD with test generation, coverage-gap analysis, and multi- framework support. Use when writing tests first, analyzing coverage, generating test stubs, or converting tests between Jest, Pytest, JUnit, and Vitest.
Guide red-green-refactor TDD with test generation, coverage-gap analysis, and multi- framework support.
As a process D 44/100 · Unfinished process — References files that are not bundled: assets/sample_coverage_report.lcov, assets/sample_coverage_gaps.lcov, references/*.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:108Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Security-focused test generation (fuzz testing, penetration testing) -- see `senior-security` and `senior-secops` skills
Files scanned: 21. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/sample_coverage_report.lcov - warning
missing-refreference to a missing file: assets/sample_coverage_gaps.lcov - warning
missing-refreference to a missing file: references/*.md
Process rating: all ten parameters 44/100
- 0Tools and files. 3 referenced file(s) missing: assets/sample_coverage_report.lcov, assets/sample_coverage_gaps.lcov, references/*.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 55Failures and branches. 1 branches
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2159 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 237: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
- +3All 9 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.