CtrlK
BlogDocsLog inGet started
Tessl Logo

iterative-development

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

60

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with strong workflow clarity and an explicit feedback loop, though conciseness and progressive disclosure are held back by duplicated inline scripts and the absence of split reference files.

Suggestions

Extract the npm and Python loop-check scripts into scripts/ files and reference them, reducing duplication and the inline token cost.

Trim the "Core Philosophy" ASCII box to a one-line principle or fold it into the existing flow diagram.

Keep the iteration-count mechanism explanation but drop restating exit-code semantics twice across both variants.

DimensionReasoningScore

Conciseness

Mostly efficient concrete code and tables, but the two near-duplicate script variants and the "Core Philosophy" ASCII box add tokens that could be tightened without losing clarity.

2 / 3

Actionability

Provides fully executable bash scripts and copy-paste-ready JSON hook configs with specific commands, paths, and exit-code semantics.

3 / 3

Workflow Clarity

The numbered 1-7 flow diagram plus the hook itself as an explicit validate-fix-retry feedback loop, with max-iteration safety and an error-classification table, gives clear sequenced validation checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist; content is a single well-sectioned file but the npm and Python script variants are inline where they could be split into separate reference files for cleaner navigation.

2 / 3

Total

10

/

12

Passed

Description

67%

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 distinctive, but it relies on technical jargon for triggers and omits an explicit "Use when" clause, capping completeness and trigger quality.

Suggestions

Add a "Use when..." clause with natural user phrasings (e.g., "Use when you want automated test loops or red-green-refactor after each response").

Soften jargon by including everyday terms like "automated testing loop" alongside "Stop hooks".

Mirror the existing when-to-use field inside the description so the trigger travels with it.

DimensionReasoningScore

Specificity

Names multiple concrete actions in third person — "runs tests after each response" and "feeds failures back automatically" — tied to a specific mechanism (Stop hooks).

3 / 3

Completeness

Clearly states what the skill does but the description field lacks any "Use when..." trigger clause; per guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant terms (TDD, tests, iteration) but leans on technical jargon ("Claude Code Stop hooks") and omits common user phrasings like "automated testing loop" or "red-green-refactor".

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (TDD loops via Stop hooks) unlikely to overlap with other skills, so conflict risk is low.

3 / 3

Total

10

/

12

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.

Validation14 / 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/claude-bootstrap
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.