CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-iterative-loop

Run tasks in a loop until goals are met — use for iterative refinement, polling, or convergence

Quality

69%

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 ./.claude/skills/skill-iterative-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers a well-sequenced, genuinely actionable loop process with strong safety machinery: checklists, three explicit exit conditions, self-regulation scoring with configurable weights, and a careful metric-verification procedure that preserves the user's workspace. Its weaknesses are systematic verbosity — the same safety rules are restated across Best Practices, Red Flags, Self-Regulation, and Safety Mechanisms, including two conflicting stall protocols — and a monolithic structure that inlines material belonging in separate reference files.

Suggestions

Deduplicate the safety material: 'Safety Mechanisms' items 1–4 restate the Self-Regulation section and the 'Red Flags' table repeats Best Practices — keep one authoritative version of each rule, which would also resolve the conflicting stall protocols between 'Progress Detection' (stop immediately) and 'Sliding-Window Stuck Detection' (one diagnostic retry, then halt).

Move the four 'Common Patterns' worked examples and the 'Metric Verification Mode' procedure into references/ files, leaving SKILL.md as a concise overview with clearly signaled one-level-deep links.

Trim explanations of concepts Claude already knows, e.g., the good/poor example pairs in Best Practices, the 'Why It's Dangerous' column of the Red Flags table, and 'The Bottom Line' section that restates the Overview's core principle.

DimensionReasoningScore

Conciseness

Multiple sections restate the same rules: "Safety Mechanisms" items 1–4 repeat the Self-Regulation section (e.g., "Track last 10 iterations. If repeated pattern detected twice: STOP" vs. the sliding-window rules), the Red Flags table ("No max iterations | Could loop forever") repeats Best Practices #1, and "The Bottom Line" restates the Overview's core principle. It also over-explains what Claude already knows ("Keep trying until it works (What if it never works? Infinite loop!)"), fitting "several unnecessary explanations or padded sections" rather than the incidental tightening of anchor 3.

2 / 5

Actionability

Mostly concrete and executable: literal templates ("**Iteration [current] / [max]**"), exact thresholds ("WTF score exceeds 20%", "Hard cap: 50 iterations"), a config file format with key=value pairs, and a JSON ledger example with specific budgets ("five iterations, 30 elapsed minutes, and 14 additional model calls"). Not anchor 5 because some guidance is underspecified — the "strategy-rotation hook" is invoked without how to detect it, and "Track mentally during the loop" leaves execution vague.

4 / 5

Workflow Clarity

Clear phased sequence (Setup → Execution → Exit Conditions) with an explicit safety checklist ("Never proceed without max iterations defined") and feedback loops (Exit Condition 3 stalls → reassess). Not anchor 5 because stall handling conflicts: "### 4. Progress Detection: If last 3 iterations show same result: Stop and ask user" contradicts Self-Regulation's "On first detection: ... Attempt ONE diagnostic retry ... On second detection: HALT immediately".

4 / 5

Progressive Disclosure

Section headers are good, but this is a monolithic ~675-line file with no bundle files; the four "Common Patterns" worked examples and the detailed "Metric Verification Mode" procedure are inlined content that clearly belongs in separate reference files. This matches anchor 3 ("content that should be separate is inline") rather than anchor 4, where most content is appropriately placed.

3 / 5

Total

13

/

20

Passed

Description

70%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 concise, third-person, and explicitly answers both what the skill does and when to use it, with good natural keyword coverage around looping and iteration. Its main limitation is that it states one high-level action rather than several concrete capabilities, and its when-clause names use categories instead of concrete trigger phrases. No over-claims or buzzwords are present.

DimensionReasoningScore

Specificity

"Run tasks in a loop until goals are met" names the domain and one core action, matching the anchor "Names domain and 1-2 concrete actions, but not comprehensive". It does not list several specific concrete actions (anchor 4), but is more concrete than a bare domain label (anchor 2).

3 / 5

Completeness

"Run tasks in a loop until goals are met" answers what, and "use for iterative refinement, polling, or convergence" is an explicit when-clause, so both are present. It is below anchor 5 because the when lists use categories rather than concrete user-utterance trigger phrases like "when the user says 'loop N times'".

4 / 5

Trigger Term Quality

Natural terms users would say are present — "loop", "iterative refinement", "polling", "convergence" — fitting "good keyword coverage; a few natural terms missing". It falls short of anchor 5 because common variations like "repeat", "retry", or "keep trying until" are absent, but coverage exceeds the single-keyword anchor 3.

4 / 5

Distinctiveness Conflict Risk

The looping niche ("until goals are met", "convergence") is mostly distinct with only minor overlap risk against closely related retry/debug skills, matching anchor 4. It is not anchor 5 because "polling" and the generic "tasks" leave slight trigger ambiguity with neighboring skills.

4 / 5

Total

15

/

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

skill_md_line_count

SKILL.md is long (676 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-iterative-loop/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.