CtrlK
BlogDocsLog inGet started
Tessl Logo

loop-library

Discover, find, compare, audit, repair, adapt, and design repeatable AI-agent loops with explicit triggers, actions, verification, stopping conditions, guardrails, and handoffs. Use when a user asks to analyze a codebase for potential loops, mine coding-thread history for work done more than once, turn repeated engineering work into a loop, find or recommend a published loop, create a recurring agent workflow or automation cadence, turn an outcome into a bounded copy-ready loop, or review an existing loop for weak checks, unsafe authority, unbounded repetition, stale state, or unclear stopping behavior.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-engineered instruction-only skill body: concrete routing, verbatim scripts, an explicit validation preflight, and clean two-file progressive disclosure. The only real cost is redundancy between the design rules and the preflight checklist, which repeats four rules nearly verbatim.

Suggestions

In 'Validate every crafted loop', reference the design rules by name instead of restating them (e.g., 'confirm each rule in Design the feedback cycle holds'), keeping only the checklist framing to remove the near-verbatim duplication of the one-shot, error-as-success, approval, and grounding rules.

The 'Keep discovered loops, adaptations, and repairs grounded' section and the final grounding bullet in the validation checklist both enumerate invented-detail categories; state the full list once and point to it from the other location.

Consider folding the 'Do not expose this internal preflight' and delivery-privacy rules ('Keep its internal design private') into a single 'what to keep internal' note to avoid scattering the same disclosure guidance across two sections.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence throughout and never explains background concepts, but several rules appear twice in near-verbatim form: "one-shot workflow instead of a loop" (Design the feedback cycle vs. Validate every crafted loop), errors-never-reported-as-success, approval for destructive actions, and grounding against invented tools/limits. The design-rules-versus-preflight-checklist mirroring is deliberate but could be trimmed, fitting the 4 anchor (efficient, minor instances that could be trimmed) rather than the 5 anchor where every token earns its place. It is not a 3 because there is no padded explanation or over-teaching anywhere.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact routing criteria for all six routes, a numbered find procedure with ranking dimensions, verbatim interview questions ("What would you like the agent to get done?"), a copy-ready delivery template, and a concrete compression guide script. This matches the 5 anchor (copy-paste-ready guidance covering the common cases); the absence of code is not penalized per the scoring notes.

5 / 5

Workflow Clarity

The multi-step process is clearly sequenced (route the request -> per-route workflow -> design interview -> six-step feedback cycle -> validation preflight -> delivery) with an explicit validation checkpoint section ("silently trace one complete cycle and repair material weaknesses") and error-recovery guidance ("ask one short question or report why the candidate is not ready"). Explicit checkpoints and feedback loops match the 5 anchor; the 4 anchor's 'minor validation gaps' does not apply since validation is central to the skill.

5 / 5

Progressive Disclosure

The two heaviest workflows are split into verified, well-signaled one-level-deep references (references/discover.md and references/audit.md), each loaded only at its point of use with a clear condition, and the reference files point back to SKILL.md rather than nesting deeper. Core interview, design, validation, and delivery rules stay inline where they belong, matching the 5 anchor (clear overview with well-signaled one-level-deep references, content appropriately split, easy navigation).

5 / 5

Total

19

/

20

Passed

Description

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

A strong description: it enumerates concrete capabilities in third person and pairs them with an explicit, comprehensive 'Use when' clause spanning all six usage routes. The only weakness is minor overlap risk between the 'recurring agent workflow / automation cadence' trigger and generic workflow/scheduling skills.

DimensionReasoningScore

Specificity

The description lists seven concrete actions ("Discover, find, compare, audit, repair, adapt, and design repeatable AI-agent loops") qualified with domain-specific mechanics ("explicit triggers, actions, verification, stopping conditions, guardrails, and handoffs"), matching the anchor for multiple specific concrete actions with comprehensive coverage. It is not a 4 because no route is left at a generic level; each action names what is actually done.

5 / 5

Completeness

The first sentence explicitly answers "what" with concrete capabilities, and "Use when a user asks to..." provides an explicit, multi-clause "when" with concrete trigger phrases. This matches the 5 anchor (clearly and explicitly answers both what AND when with concrete trigger phrases), not the 4 anchor whose 'when' could be more specific.

5 / 5

Trigger Term Quality

Trigger phrasing covers the natural ways a user would ask for this: "analyze a codebase for potential loops", "mine coding-thread history for work done more than once", "turn repeated engineering work into a loop", "find or recommend a published loop", "create a recurring agent workflow or automation cadence", and "review an existing loop for weak checks, unsafe authority, unbounded repetition, stale state, or unclear stopping behavior". Synonym coverage across all six routes is comprehensive, fitting the 5 anchor rather than the 4 anchor (no common variation is missing).

5 / 5

Distinctiveness Conflict Risk

The loop niche is consistently and clearly framed ("repeatable AI-agent loops", "published loop", "bounded copy-ready loop"), but the trigger "create a recurring agent workflow or automation cadence" overlaps with generic workflow/scheduling skills and could pull the wrong skill for that request. This fits the 4 anchor (mostly distinct; minor overlap risk with closely related skills) better than the 5 anchor, and it is well above the 3 anchor since every other trigger is loop-specific.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.