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.

Quality

40%

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

Quality

Content

40%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 thin activation shell over a well-structured reference file, but the shell itself is padded with a verbatim description repeat, editorial commentary, twelve redundant trigger bullets, and a circular example that quotes the description back as a user request. The one inline code sample is incomplete and context-free, and no executable workflow exists in the body. Structure and reference signaling are the strongest aspects; content discipline is the weakest.

Suggestions

Delete the opening paragraph that repeats the frontmatter description verbatim, and compress the 12 'User mentions or implies:' bullets into a single trigger list on one line.

Either make the ContextManager example executable (define or import token_count and summarize_messages, show usage) or move it into references/detailed-guide.md alongside the other code patterns.

Replace the circular Example section (which quotes the description back as a user request) with a real input/output example, and add a short numbered workflow with validation checkpoints so the body is actionable without opening the guide.

Dimension	Reasoning	Score
Conciseness	The opening paragraph repeats the frontmatter description verbatim, the '2025 lesson' paragraph is editorial commentary Claude does not need, and the 'When to Use' section uses 12 near-identical 'User mentions or implies: X' bullets that could be one line. Several padded sections with little added value, matching anchor 2 rather than 3 because the duplication and repetition are pervasive, not incidental.	2 / 5
Actionability	The only concrete artifact is the ContextManager class, which calls undefined functions (token_count(), summarize_messages()) and lacks any usage context, functioning as illustrative pseudocode with missing key details. Everything else is conceptual ('covers agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns') or delegated to the reference file, matching the anchor-3 pseudocode example.	3 / 5
Workflow Clarity	The body contains no step sequence at all - its sole directive is 'Read [the detailed guide](references/detailed-guide.md) before executing this skill', with no ordered steps and no validation checkpoints. This sits between anchor 1 (steps missing) and anchor 2 (rough sequence with many gaps); a single read-first directive is not a sequence, but it is at least a coherent entry point.	2 / 5
Progressive Disclosure	The bundle has one real, well-signaled, one-level-deep reference (references/detailed-guide.md, 1065 lines, no nested .md links) with explicit guidance on when to read it fully vs. by section. It falls short of anchor 5 because the body inlines content that duplicates or belongs in the guide (the verbatim description repeat, the orphan ContextManager sample) and section ordering is disorganized (code before 'When to Use').	4 / 5
	Total	11 / 20 Passed

Description

41%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 reads as a topic definition plus opinion rather than a capability statement: it says what autonomous agents are and why reliability matters, but never what the skill does or when to invoke it. Concrete verbs in the first sentence keep it above the vague baseline, and the niche is identifiable, but missing trigger guidance and the editorial second half hold it well below the good examples. This is the primary fixable weakness of the skill.

Suggestions

State what the skill does in a leading verb phrase, e.g. 'Design and build autonomous agents: agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and reliability guardrails', instead of defining what autonomous agents are.

Add an explicit trigger clause: 'Use when the user mentions autonomous agents, agent loops, AutoGPT, BabyAGI, LangGraph, ReAct, or agentic AI, or asks about self-correcting or self-directing agents.'

Cut the editorial commentary ('The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.') - it conveys no capability or trigger information and reads as marketing copy.

Dimension	Reasoning	Score
Specificity	Phrases like 'independently decompose goals, plan actions, execute tools, and self-correct' list several concrete actions, but they describe what autonomous agents are rather than what this skill does, and the back half ('The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.') is pure editorial with no capability content. This lands between anchor 3 and anchor 4 - concrete action verbs are present, but the skill's own capabilities are never stated.	3 / 5
Completeness	There is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3, and the 'what' is weaker than anchor 3 requires: the description defines the concept of autonomous agents but never states what the skill does (design agent loops? implement patterns? evaluate reliability?). With a vague skill-level 'what' and no 'when', anchor 2 is the better fit.	2 / 5
Trigger Term Quality	'Autonomous agents', 'decompose goals', 'plan actions', and 'self-correct' are relevant keywords, but common natural variations users actually say - agent loop, AutoGPT, BabyAGI, LangGraph, ReAct, agentic AI - are missing from the description (they appear only in the body's When-to-Use list). Anchor 3 ('some relevant keywords but missing common variations or synonyms') is the best fit.	3 / 5
Distinctiveness Conflict Risk	'Autonomous agents... decompose goals... self-correct' carves out a fairly specific niche, but the description's framing as a general capability statement ('AI systems that can independently...') plus the absence of any trigger guidance gives it real overlap risk with neighboring agent/tool-use/multi-agent skills. Anchor 3 ('somewhat specific but could still overlap with similar skills') fits better than anchor 4.	3 / 5
	Total	11 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/autonomous-agents/SKILL.md
Commit: 7b534bc

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.