CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

48

Quality

51%

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-agents/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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 well-structured with a real one-level reference and a useful trigger list, but it leans conceptual: it repeats the description, editorializes, offers only incomplete code, and lacks any validated execution workflow. Tightening the prose and adding a concrete, checkpointed procedure would raise the score.

Suggestions

Remove the verbatim repeat of the description from the intro and cut the '2025 lesson' editorializing to reduce redundancy and token cost.

Make the ContextManager example fully executable by defining token_count() and summarize_messages(), or explicitly mark it as illustrative pseudocode with a note.

Add a short numbered execution workflow with explicit validation checkpoints (e.g., verify plan against goal, validate tool outputs before proceeding) since autonomous agents perform batch/destructive operations.

DimensionReasoningScore

Conciseness

The intro repeats the description verbatim and the '2025 lesson' plus reliability philosophy re-explain concepts Claude already knows, but the body retains enough useful material (ContextManager, When to Use, Limitations) to stay mostly efficient, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than 2.

3 / 5

Actionability

The only concrete code (ContextManager) calls undefined helpers token_count() and summarize_messages(), making it incomplete rather than copy-paste ready, while the surrounding prose ('covers agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns') describes rather than instructs — matching 'some concrete guidance but incomplete; pseudocode…missing key details'.

3 / 5

Workflow Clarity

The body presents no sequenced execution procedure with validation checkpoints, and because autonomous agents perform batch/destructive tool operations the missing-validation cap applies; only the ContextManager's compaction flow gives a rough, unvalidated sequence, so it sits at 'rough sequence present but many gaps; validation absent' rather than 3.

2 / 5

Progressive Disclosure

It points to one clearly-signaled, one-level-deep reference (references/detailed-guide.md, verified to exist) with good section headers and easy navigation, but inlines the full ContextManager class and editorial commentary that could live in the guide, leaving minor organization gaps that keep it below 5.

4 / 5

Total

12

/

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 clearly conveys what autonomous agents do via several named capabilities, but omits any explicit 'when to use' trigger guidance and relies on a single natural keyword, limiting trigger quality and completeness. The philosophical padding adds length without specificity.

Suggestions

Add an explicit 'Use when...' clause listing concrete trigger phrases (e.g., autonomous agent, agentic AI, agent loop, ReAct pattern, goal decomposition) so the description answers 'when' as well as 'what'.

Replace the philosophical closing ('The challenge isn't making them capable...') with one or two more concrete capabilities (e.g., context compaction, reflection loops) to raise specificity.

Include synonyms users naturally say (agentic AI, self-prompting, langgraph) directly in the description to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Lists four named actions ('decompose goals, plan actions, execute tools, and self-correct') but the second half ('The challenge isn't making them capable - it's making them reliable. Every extra decision multiplies failure probability.') is philosophical framing rather than capability, so it is not comprehensive enough for a 5.

4 / 5

Completeness

It clearly answers 'what' (independently decompose goals, plan actions, execute tools, self-correct) but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The only natural user term present is 'autonomous agents'; common variations and synonyms users say (agentic AI, agent loop, react pattern) appear in the body's 'When to Use' list but are absent from the description, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Autonomous agents' is a recognizable niche but a broad conceptual domain with no concrete distinguishing triggers in the description, so it could still overlap with general agent, langgraph, or planning 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-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.