BD improvement
Guide for making improvements to existing ClaudeBar functionality using TDD. Use this skill when: (1) Enhancing existing features (not adding new ones) (2) Improving UX, performance, or code quality (3) User asks "improve X", "make Y better", or "enhance Z" (4) Small enhancements that don't require full architecture design For NEW features, use implement-feature skill instead.
Guide for making improvements to existing ClaudeBar functionality using TDD.
As a process D 35/100 · Unfinished process — References files that are not bundled: ../../../AGENTS.md, ../../../docs/architecture/USER_JOURNEYS.md, ../../../docs/architecture/CANONICAL_MODEL.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 · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../../AGENTS.md - warning
missing-refreference to a missing file: ../../../docs/architecture/USER_JOURNEYS.md - warning
missing-refreference to a missing file: ../../../docs/architecture/CANONICAL_MODEL.md - warning
missing-refreference to a missing file: ../../../docs/architecture/TARGET_ARCHITECTURE.md - warning
missing-refreference to a missing file: ../implement-feature/references/domain-shape.md - warning
missing-refreference to a missing file: ../implement-feature/references/tdd-patterns.md - warning
missing-refreference to a missing file: ../../../docs/architecture/MODULAR_DESIGN.md - warning
missing-refreference to a missing file: ../../../docs/architecture/ARCHITECTURE.md - warning
missing-refreference to a missing file: ../implement-feature/SKILL.md - warning
missing-refreference to a missing file: scripts/demo-screenshots.sh
Process rating: all ten parameters 35/100
- 0Tools and files. 10 referenced file(s) missing: ../../../AGENTS.md, ../../../docs/architecture/USER_JOURNEYS.md, ../../../docs/architecture/CANONICAL_MODEL.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2255 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 379: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.