CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

iterative-development

TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically

54

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/iterative-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

The body is highly actionable with complete, executable scripts and a genuine feedback-loop design, and the setup workflow is well sequenced. It is held back by motivational/ASCII padding, a redundant flowchart, and a second full script variant that inflates the file instead of being split out.

Suggestions

Remove the 'Core Philosophy' ASCII box and the opening flowchart, or compress them to one or two lines — the prose already conveys the mechanism and Claude doesn't need motivation.

Replace the duplicated Python variant with a short delta note (e.g. 'swap the test command for pytest and ruff/mypy') or move both scripts into a scripts/ bundle file referenced from SKILL.md.

Add the missing setup detail: instruct users to chmod +x scripts/tdd-loop-check.sh (and note the shebang requirement) since the hook invokes the script path directly.

DimensionReasoningScore

Conciseness

The scripts and configs are tight, but the 'Core Philosophy' ASCII box ("ITERATION > PERFECTION", "FAILURES ARE DATA") is motivational padding Claude doesn't need, the opening flowchart duplicates the prose explanation, and the near-duplicate Python variant doubles the script length — 'mostly efficient with some unnecessary sections' (anchor 3).

3 / 5

Actionability

Everything is copy-paste ready: complete settings.json hook configs, two fully executable bash scripts (npm and pytest stacks) with iteration caps and error handling, plus a gitignore snippet — concrete and covering the common cases.

5 / 5

Workflow Clarity

Setup is clearly sequenced (configure hook → create script → gitignore) and the core validate→fix→retry feedback loop is explicit, but it never tells the user to make the script executable (chmod +x) even though it is invoked directly as scripts/tdd-loop-check.sh — a minor validation gap keeping it below 5.

4 / 5

Progressive Disclosure

Section headers are clear, but this is a ~300-line single file whose full scripts (especially the second Python variant) arguably belong in a separate scripts/ or reference file; structure is good yet content that should be separate is inline (anchor 3).

3 / 5

Total

15

/

20

Passed

Description

53%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.

The description is specific and honest about the mechanism, with a well-defined niche, but it lacks any 'when to use' trigger clause and misses natural synonyms like 'test-driven development'. Adding an explicit 'Use when...' clause with concrete trigger phrases would lift completeness and trigger-term quality simultaneously.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to set up TDD, test-driven development, or automatic test-feedback loops, or wants tests to run automatically after each response.'

Include natural synonyms such as 'test-driven development' and 'auto-run tests' so the description matches how users actually phrase the request.

Mention the full verification scope (tests, lint, typecheck) to make the capability listing more comprehensive.

DimensionReasoningScore

Specificity

"runs tests after each response, feeds failures back automatically" names the domain and two concrete actions, but omits lint/typecheck, iteration capping, and setup guidance, so coverage is not comprehensive (anchor 3, not 4 — the gaps exceed 'minor').

3 / 5

Completeness

The 'what' is clear ("runs tests after each response, feeds failures back"), but the description contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"TDD", "tests", and "Stop hooks" are relevant keywords, but common variations users would say are missing ("test-driven development", "auto-run tests", "continuous testing"), matching the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

"TDD iteration loops using Claude Code Stop hooks" carves a clear niche tied to specific Claude Code infrastructure, with only minor overlap risk against generic testing skills; not a 5 because "TDD" and "tests" alone could collide with plain test-writing requests.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

alinaqi/maggy

Path

skills/iterative-development/SKILL.md

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.