Name: autonomous-loops
Rating: 59.2 (1 reviews)
Author: affaan-m

autonomous-loops

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/autonomous-loops/SKILL.md

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

Quality

Content

81%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 content is highly actionable and workflow-rich, with executable examples and strong validation/feedback loops throughout. Its main weakness is progressive disclosure: a large, self-contained reference monolith that would benefit from splitting detailed patterns into referenced files.

Suggestions

Split the six loop patterns into separate reference files (e.g. references/sequential-pipeline.md, references/ralphinho-dag.md) and keep SKILL.md as a concise overview with a spectrum table and one-level-deep links.

Move the Ralphinho RFC schema, complexity-tier table, and data-flow diagrams into a dedicated reference file, leaving only the decision guidance inline.

Move the project credits/links out of an inlined References table into a references/credits.md file or a compact one-line pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and action-oriented with executable bash and tables, though ASCII diagrams and explanatory prose add some tokens that could be trimmed without losing clarity.	4 / 5
Actionability	Provides copy-paste-ready bash scripts, concrete command flags, file templates, and a slash-command spec — specific examples cover the common cases end to end.	5 / 5
Workflow Clarity	Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops (set -e propagation, CI failure recovery, validate→fix→retry, merge-queue eviction with conflict context).	5 / 5
Progressive Disclosure	A monolithic single-file skill with substantial inlined reference material (WorkUnit schema, tier tables, data-flow diagrams, references table) that belongs in separate files; no references/ bundle exists and external pointers are buried.	2 / 5
	Total	16 / 20 Passed

Description

58%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 conveys a clear, specific niche and concrete architectural archetypes, but it omits any explicit 'Use when' trigger guidance, which limits completeness and trigger-term quality. Adding natural trigger phrases would lift the description from adequate to strong.

Suggestions

Add an explicit 'Use when' clause with concrete triggers, e.g. 'Use when setting up autonomous Claude Code workflows, CI/CD dev loops, or multi-agent DAG orchestration.'

Include natural user-facing synonyms and file/flag terms (e.g. 'claude -p pipelines', 'continuous PR loops', 'infinite agent loops') to broaden trigger-term coverage.

Reframe the opening from abstract 'Patterns and architectures' toward the concrete actions the skill helps perform (set up, orchestrate, coordinate).

Dimension	Reasoning	Score
Specificity	Names the domain (autonomous Claude Code loops) and several concrete architectural archetypes — 'simple sequential pipelines', 'RFC-driven multi-agent DAG systems' — but describes patterns/architectures rather than discrete executable actions, leaving minor coverage gaps.	4 / 5
Completeness	Clearly answers 'what' (patterns and architectures for autonomous loops) but provides no 'when' guidance or explicit trigger clause, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes relevant terms like 'autonomous Claude Code loops', 'sequential pipelines', and 'multi-agent DAG', but lacks common natural synonyms users would say and has no explicit 'Use when' trigger phrase.	3 / 5
Distinctiveness Conflict Risk	Targets a fairly distinct niche — autonomous loop orchestration — with only minor overlap risk against general agent-orchestration or CI/CD skills.	4 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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: affaan-m/ECC
Path: .kiro/skills/autonomous-loops/SKILL.md
Commit: d8409a4

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.