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. 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

32

Quality

27%

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

Quality

Content

22%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill body is essentially a philosophical preamble plus a table of contents linking to sub-skills, with no actionable content of its own. It lacks any concrete code, commands, examples, or workflows. While the progressive disclosure structure of linking to sub-skills is reasonable in principle, the main file fails to provide even a minimal quick-start or summary of the patterns it covers, making it nearly useless as a standalone reference.

Suggestions

Add a concrete quick-start section showing a minimal ReAct agent loop implementation (executable code) so the skill body itself is actionable without requiring sub-skill navigation.

Include a brief workflow showing the recommended sequence for building an autonomous agent (e.g., 1. Define constrained scope → 2. Implement ReAct loop → 3. Add guardrails → 4. Validate with logging → 5. Expand scope), with explicit validation checkpoints.

Remove the 'Capabilities' bullet list—it's redundant metadata that belongs in frontmatter, not the body.

Add a concise comparison table or decision guide (e.g., when to use ReAct vs Plan-Execute) so the overview file provides value beyond just linking to sub-skills.

DimensionReasoningScore

Conciseness

The introductory narrative about agent architecture philosophy is somewhat verbose and tells Claude things it already knows (compounding error rates, autonomy concepts). The capabilities list is redundant tag-like content that doesn't add actionable value. However, it's not excessively padded.

2 / 3

Actionability

There is no concrete code, no executable examples, no specific commands, and no actionable guidance in the body itself. The content is entirely abstract philosophy and links to sub-skills. A reader of just this file learns no concrete technique.

1 / 3

Workflow Clarity

There are no steps, no sequences, no validation checkpoints, and no workflow described. The content is a philosophical framing plus a list of links. For a skill covering agent loops and goal decomposition, the absence of any workflow guidance is a significant gap.

1 / 3

Progressive Disclosure

The skill does reference six sub-skill files with clear one-level-deep links, which is good structure. However, since no bundle files are provided, we cannot verify these references exist. The main file itself contains almost no substantive content—it's essentially just a table of contents with a philosophical preamble, which over-delegates rather than providing a useful overview.

2 / 3

Total

6

/

12

Passed

Description

32%

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 more like an educational overview or essay introduction than a skill description for Claude's skill selection. It is truncated mid-sentence, lacks any explicit 'Use when...' trigger guidance, and focuses on conceptual explanations (e.g., 'compounding error rates kill autonomous agents') rather than concrete actions Claude would perform. The tone is expository rather than functional.

Suggestions

Add an explicit 'Use when...' clause with natural trigger terms like 'build an agent,' 'agentic workflow,' 'tool-use loop,' 'autonomous system,' or 'agent reliability.'

Replace the expository/educational tone with concrete action verbs describing what Claude does with this skill, e.g., 'Designs agent architectures, implements ReAct loops, adds reflection and error-recovery patterns.'

Fix the truncated description and remove editorial commentary (e.g., 'The challenge isn't making them capable - it's making them reliable') that doesn't help with skill selection.

DimensionReasoningScore

Specificity

The description names the domain (autonomous agents) and mentions some specific concepts like 'agent loops (ReAct, Plan-Execute), goal decomposition, reflection patterns, and production reliability,' but these are more conceptual topics than concrete actions Claude would perform. It reads more like a course syllabus than actionable capabilities.

2 / 3

Completeness

The description covers 'what' at a conceptual level (agent loops, goal decomposition, reflection patterns) but completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent trigger guidance, and the description appears truncated mid-sentence.

1 / 3

Trigger Term Quality

Contains some relevant keywords like 'autonomous agents,' 'ReAct,' 'Plan-Execute,' 'goal decomposition,' 'reflection patterns,' but these are fairly technical terms. Missing more natural user phrases like 'build an agent,' 'agent framework,' 'tool use loop,' or 'agentic workflow.'

2 / 3

Distinctiveness Conflict Risk

The focus on autonomous agents and specific patterns like ReAct and Plan-Execute provides some distinctiveness, but the broad scope covering 'production reliability' and 'goal decomposition' could overlap with general software architecture or AI system design skills.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
Dokhacgiakhoa/antigravity-ide
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.