CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autonomous-loops

Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.

Quality

67%

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/autonomous-loops/SKILL.md

The canonical home for this skill is autonomous-loops in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

70%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-organized, highly actionable reference: workflows are explicitly sequenced with validation gates and genuine recovery loops, and concrete code and commands dominate over abstraction. Its weaknesses are structural and editorial — the six patterns are inlined in one long file with no one-level-deep references, the de-sloppify material is repeated across sections, and several external pointers (continuous-claude, claw.js, verification-loop) lack real, resolvable targets.

Suggestions

Split each of the six pattern sections (Sequential Pipeline, NanoClaw, Infinite Agentic Loop, Continuous Claude, De-Sloppify, Ralphinho DAG) into one-level-deep reference files, keeping a compact overview, comparison table, and decision matrix in SKILL.md with clearly signaled links.

Consolidate the de-sloppify material into its single dedicated section and reference it from Section 1 and the anti-patterns list instead of restating it four times.

Replace the placeholder Links column with actual repository URLs for continuous-claude, Ralphinho, and the Infinite Agentic Loop, and either ship or drop the referenced in-repo targets (scripts/claw.js, skills/verification-loop/).

DimensionReasoningScore

Conciseness

The body is dense and largely assumes Claude's competence rather than explaining known concepts, but it repeats the de-sloppify material across four places (Sequential Pipeline step 2 and principle 3, the full Section 5, Anti-Pattern 4, and Combining Patterns) and opens with a compatibility-note preamble that earns little. This fits anchor 3 (mostly efficient but could be tightened), not 4, because the repetition and preamble are noticeable, not minor.

3 / 5

Actionability

Most guidance is executable and copy-paste ready: full bash pipeline scripts, the .claude/commands/infinite.md command file, a continuous-claude flags table, and concrete prompt text per step. It misses 5 because of small gaps — "Install continuous-claude from its repository" gives no URL, node scripts/claw.js and skills/verification-loop/ reference files that are not present in any bundle, and the References table's Link column holds only credit attributions rather than actual links.

4 / 5

Workflow Clarity

Each pattern is sequenced explicitly with validation checkpoints (dedicated Verify steps, test suite after cleanup, CI gates before merge) and genuine error-recovery feedback loops (CI auto-fix pass with retry cap, merge-queue eviction with captured conflict context fed to the next pass, three-signal completion threshold). The decision matrix and anti-pattern checklist round out anchor 5's requirements; batch operations here do include validation, so no cap applies.

5 / 5

Progressive Disclosure

There are no bundle files at all, so the entire ~600-line body is inlined in SKILL.md. Headers and an anchor-linked navigation table provide real structure, but the six distinct pattern write-ups — especially the long Ralphinho and Continuous Claude sections — are exactly the content that would naturally live in one-level-deep reference files. This matches anchor 3 (some structure, content that should be separate is inline), not 2, because section headers and navigation are present and clear.

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 communicates a clear, distinctive subject area with concrete scope boundaries, but it is a noun-phrase inventory rather than a capability statement: no action verbs, no "Use when" trigger clause, and few of the natural synonyms a user would actually say when needing this skill. It would reliably find the right audience once found, but is weak at being triggered from a user's phrasing.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up autonomous/continuous Claude Code loops, unattended multi-agent orchestration, or CI-style development pipelines."

Rephrase the opening with third-person action verbs — e.g. "Provides patterns and reference implementations for building autonomous Claude Code loops..." — so the skill states capabilities, not just subject matter.

Include natural user phrasings and synonyms such as "agentic loop", "continuous development", "run Claude in a loop", and "background/CI-style agent pipelines" to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names its domain ("autonomous Claude Code loops") and the concrete endpoints of coverage ("simple sequential pipelines to RFC-driven multi-agent DAG systems"), but contains no action verbs at all — it says what the skill contains, not what it does. It sits between anchor 2 (minimal/generic actions) and anchor 3 (domain plus 1-2 concrete actions), and is not above 3 because no capability is phrased as an action.

3 / 5

Completeness

The "what" is clear — patterns and architectures for autonomous Claude Code loops across a named spectrum — but there is no "Use when..." clause or any equivalent explicit trigger guidance, which the judging guidelines cap at 3. It is not a 2 because the "what" half is concrete and specific, not vague.

3 / 5

Trigger Term Quality

"autonomous", "loops", "sequential pipelines", "multi-agent", and "DAG" are relevant keywords a user working in this space might say, but common natural variations are missing — "agentic loop", "continuous", "run Claude in the background/unattended", "CI-style development". This matches anchor 3 (some relevant keywords, missing common variations and synonyms), not 4, because several frequently-used phrasings are absent.

3 / 5

Distinctiveness Conflict Risk

The pairing of "autonomous Claude Code loops" with "RFC-driven multi-agent DAG systems" stakes a clear niche with distinct triggers and minimal overlap risk. It falls just below 5 because "patterns and architectures" as a framing is broad enough to brush against general agent-orchestration or CI/CD skills.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/autonomous-loops/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.