CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autonomous-agents

Autonomous agents are AI systems that can independently decompose goals, plan actions, execute tools, and self-correct without constant human guidance. The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability. This skill covers agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and production reliability. Key insight: compounding error rates kill autonomous agents. A 95% success rate per step drops to 60% b

Quality

48%

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 ./cli-tool/components/skills/ai-research/autonomous-agents/SKILL.md

The canonical home for this skill is autonomous-agents in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

18%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 is a placeholder skeleton rather than usable guidance: patterns get one abstract line each, anti-patterns have no explanations, the Sharp Edges table contains placeholder 'Issue' labels and corrupted '##'-prefixed solution fragments, and the text cuts off mid-word. A reader gains nothing actionable about how to actually implement a ReAct loop, decompose goals, or validate agent reliability.

Suggestions

Replace the one-line pattern descriptions with concrete, executable guidance — e.g. a minimal ReAct loop sketch with an explicit stop condition and a Plan-Execute example showing plan format, execution step, and replanning trigger.

Repair the Sharp Edges table: give each row a real named issue (e.g. 'compounding per-step error rates', 'unbounded tool spend') instead of the placeholder 'Issue' label, and a concrete solution instead of the corrupted '## Reduce step count' fragments.

Expand each anti-pattern ('Unbounded Autonomy', 'Trusting Agent Outputs', 'General-Purpose Autonomy') with why it fails and what to do instead, and add a sequenced workflow for building an agent (constrain → test at scale → validate against ground truth → add autonomy) with explicit validation checkpoints.

Fix the truncation: the intro paragraph ends mid-word at 'logging befor', and remove the verbatim duplication of the description's statistics.

DimensionReasoningScore

Conciseness

The body is short and avoids re-explaining known concepts, but it duplicates the description's statistics verbatim ('a 95% success rate per step means only 60% by step 10'), opens with a padded persona paragraph ('You are an agent architect who has learned the hard lessons...'), and carries a bare kebab-case capabilities list that adds no value. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; not 4 because the duplication and filler are clear waste.

3 / 5

Actionability

Every pattern is a single abstract line ('Alternating reasoning and action steps', 'Separate planning phase from execution'), the anti-patterns are bare headers with no explanation ('❌ Unbounded Autonomy'), and the Sharp Edges 'solutions' are corrupted fragments ('## Reduce step count', '## Set hard cost limits') with placeholder 'Issue' labels. This matches 'entirely vague or abstract; no concrete code or commands; only describes rather than instructs' — no tool, command, or concrete step is ever named.

1 / 5

Workflow Clarity

There is no sequence of steps anywhere in the body — no process for designing, building, or validating an agent, and the one table that could anchor a workflow is malformed. Matches 'steps missing or incoherent; no sequence; no validation for risky operations'.

1 / 5

Progressive Disclosure

Section headers exist (Capabilities, Patterns, Anti-Patterns, Sharp Edges, Related Skills) and there are no nested references, but the structure is skeletal: the Sharp Edges table is broken, the Anti-Patterns sections are empty, and the body is truncated mid-sentence ('logging befor'). Fits 'minimal structure'; not 3 because the organization is actively misleading rather than merely improvable.

2 / 5

Total

7

/

20

Passed

Description

55%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 domain and enumerates several specific topics (ReAct, Plan-Execute, goal decomposition, reflection patterns), but it is written more as a domain explainer than a skill description. It lacks any 'Use when...' trigger guidance, is truncated mid-sentence, and includes generic reliability commentary that could apply to many agent-related skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing, building, or debugging autonomous AI agents, agent loops (ReAct, Plan-Execute), or agentic workflows in production.'

Fix the truncation — the description cuts off mid-sentence at 'drops to 60% b', losing the closing thought.

Trim domain exposition ('The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.') in favor of natural trigger terms and synonyms users would actually say.

DimensionReasoningScore

Specificity

Lists several concrete coverage areas — 'agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and production reliability' — though the opening describes the domain rather than the skill itself and the text is truncated mid-sentence ('drops to 60% b'). Not 5 because 'production reliability' is generic and coverage is cut off; clearly above anchor 3's 1-2 actions.

4 / 5

Completeness

A clear 'what' is present ('This skill covers agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and production reliability') but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is explicit and detailed.

3 / 5

Trigger Term Quality

Contains relevant keywords ('autonomous agents', 'agent loops', 'ReAct', 'Plan-Execute', 'reflection patterns') but misses natural variations users would say such as 'AI agents', 'agentic workflows', or 'building agents'. Matches 'some relevant keywords but missing common variations or synonyms', not 4 since natural phrasings are largely absent.

3 / 5

Distinctiveness Conflict Risk

'ReAct' and 'Plan-Execute' give it some distinct identity, but 'autonomous agents' as a domain broadly overlaps closely related skills such as agent-memory-systems, multi-agent-orchestration, and agent-reliability. Fits 'somewhat specific but could still overlap with similar skills'.

3 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

davila7/claude-code-templates

Path

cli-tool/components/skills/ai-research/autonomous-agents/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.