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.

38

Quality

24%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-autonomous-agents/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

22%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description reads more like the opening paragraph of a blog post or essay about autonomous agents than a functional skill description. It explains a concept rather than describing what the skill does or when it should be selected. It completely lacks actionable triggers and concrete capability statements needed for Claude to choose this skill appropriately.

Suggestions

Replace the conceptual overview with concrete actions the skill performs, e.g., 'Guides design and implementation of autonomous agent architectures, including goal decomposition, tool orchestration, error recovery, and loop control.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about building agents, agentic workflows, tool-use loops, ReAct patterns, or multi-step autonomous systems.'

Remove the editorial commentary ('The challenge isn't making them capable - it's making them reliable') and replace with functional information about what this skill teaches or enables.

DimensionReasoningScore

Specificity

The description discusses autonomous agents conceptually but lists no concrete actions the skill performs. Phrases like 'decompose goals, plan actions, execute tools, and self-correct' describe what agents are, not what this skill does. There are no actionable capabilities like 'creates agents', 'debugs agent loops', or 'designs agent architectures'.

1 / 3

Completeness

The description provides a conceptual overview of what autonomous agents are but never explains what this skill actually does or when Claude should use it. There is no 'Use when...' clause or equivalent trigger guidance, and the 'what' is philosophical rather than functional.

1 / 3

Trigger Term Quality

Contains some relevant keywords like 'autonomous agents', 'AI systems', 'plan actions', 'execute tools', and 'self-correct' that a user interested in agent design might use. However, it misses common variations like 'agentic workflows', 'tool use', 'ReAct', 'agent loop', 'multi-step reasoning', or 'LLM agents'.

2 / 3

Distinctiveness Conflict Risk

The focus on 'autonomous agents' and reliability gives it some distinctiveness, but the vague framing around AI systems, goals, planning, and tools could overlap with many AI/coding-related skills. Without specific actions or triggers, it's unclear what domain this skill uniquely serves.

2 / 3

Total

6

/

12

Passed

Implementation

27%

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

This skill is comprehensive in coverage but severely bloated - it tries to be an entire textbook on autonomous agents rather than a concise, actionable reference. The extensive prose explanations of concepts Claude already understands (error compounding, API costs, hallucination) waste significant token budget. While it contains useful code patterns, many are pseudocode with undefined dependencies, and the monolithic structure makes it hard to navigate.

Suggestions

Cut the content by 60-70%: remove all 'Why this breaks' explanations, concept definitions Claude already knows, and verbose symptom descriptions in Sharp Edges. Keep only the 'Recommended fix' code blocks with brief labels.

Split into multiple files: move Sharp Edges to SHARP_EDGES.md, Validation Checks to VALIDATION.md, and detailed pattern implementations to PATTERNS.md. Keep SKILL.md as a concise overview with links.

Make code examples truly executable: replace undefined functions like `summarize()`, `planner.plan_next()`, and `verify_restaurant_exists()` with actual implementations or clearly mark them as interfaces to implement.

Remove the 'Capabilities', 'Scope', 'When to Use', and 'Collaboration' metadata sections from the body content - these belong in YAML frontmatter, not in the skill body consuming tokens.

DimensionReasoningScore

Conciseness

Extremely verbose at 500+ lines. Repeats concepts Claude already knows (what ReAct is, why LLMs hallucinate, how error probability compounds). Extensive prose explanations before code blocks, redundant 'Why this breaks' sections that explain obvious failure modes, and the 'Sharp Edges' section alone is massive with explanations of basic concepts like quadratic cost scaling.

1 / 3

Actionability

Contains numerous code examples that are mostly concrete and executable, but many are pseudocode-like (e.g., undefined functions like `summarize()`, `planner.plan_next()`, `verify_restaurant_exists()`). The code references undefined classes and methods, making it not truly copy-paste ready. However, the LangGraph examples with checkpointing and interrupt patterns are reasonably concrete.

2 / 3

Workflow Clarity

The patterns section provides reasonable sequencing (ReAct loop steps, Plan-Execute phases, Reflection iterations), and the guardrails section includes validation checkpoints. However, there's no clear end-to-end workflow for building an agent from scratch - it's more of a reference catalog. The validation checks section lists anti-patterns but doesn't integrate them into a coherent build workflow.

2 / 3

Progressive Disclosure

Monolithic wall of text with everything inline. The skill is 500+ lines with no references to external files for detailed content. The Sharp Edges section alone could be its own document. Patterns, guardrails, validation checks, and collaboration info are all crammed into one file with no signposting to separate detailed guides.

1 / 3

Total

6

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (1081 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

9

/

11

Passed

Repository
boisenoise/skills-collections
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.