CtrlK
BlogDocsLog inGet started
Tessl Logo

autonomous-agent-patterns

Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows. Use when building AI agents, designing tool APIs, implementing permission systems, or creating autonomous coding assistants.

52

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/autonomous-agent-patterns/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 is essentially a table of contents with no substantive content in the body itself. It provides no actionable guidance, no code examples, no workflow descriptions, and no concrete patterns—everything is deferred to 16 sub-skill files that cannot be verified. While the progressive disclosure structure is reasonable in principle, the complete absence of any overview content, quick-start guidance, or even brief descriptions of the linked patterns makes this skill body nearly useless on its own.

Suggestions

Add a concise quick-start section with at least one concrete, executable pattern (e.g., a minimal agent loop implementation) so the skill provides immediate value without requiring sub-skill navigation.

Add 1-2 sentence descriptions next to each sub-skill link so readers can understand what each module covers and navigate effectively (e.g., '**Agent Loop** - Core perceive→think→act cycle with tool execution and error recovery').

Include a recommended workflow or reading order that sequences the sub-skills logically (e.g., 'Start with Agent Loop → Tool Schema → Permission Levels → then specialize').

Remove the redundant 'When to Use This Skill' section and fold any essential context into a single introductory sentence to improve conciseness.

DimensionReasoningScore

Conciseness

The content is relatively short, but the 'When to Use This Skill' section is somewhat unnecessary padding since Claude can infer applicability. The numbered list of sub-skills is lean but the dual numbering (e.g., '### 1. [1.1 Agent Loop]') is redundant.

2 / 3

Actionability

The skill body contains zero concrete guidance, no code, no commands, and no examples. It is entirely a table of contents pointing to sub-skill files, providing no actionable content on its own.

1 / 3

Workflow Clarity

There is no workflow, sequence, or process described. The content is purely a list of links with no indication of how to approach these patterns, in what order, or how they relate to each other.

1 / 3

Progressive Disclosure

The skill does use one-level-deep references to sub-skills, which is good structure. However, since no bundle files were provided, we cannot verify the references exist. The overview itself provides no summary content for any topic—it's purely a link list with no context about what each sub-skill covers, making navigation harder than it should be.

2 / 3

Total

6

/

12

Passed

Description

92%

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 is a well-structured description that clearly communicates both what the skill covers and when to use it. It lists concrete topics and includes an explicit 'Use when' clause with relevant trigger terms. The only minor weakness is that some individual trigger terms like 'tool APIs' and 'permission systems' are broad enough to potentially overlap with other skills, though the overall context of 'autonomous coding agents' helps disambiguate.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions/topics: tool integration, permission systems, browser automation, and human-in-the-loop workflows. These are distinct, identifiable capabilities rather than vague abstractions.

3 / 3

Completeness

Clearly answers both 'what' (design patterns for autonomous coding agents covering tool integration, permission systems, browser automation, human-in-the-loop workflows) and 'when' (explicit 'Use when' clause with four specific trigger scenarios).

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'AI agents', 'tool APIs', 'permission systems', 'autonomous coding assistants', 'browser automation', 'human-in-the-loop'. These cover a good range of terms a developer would naturally use when seeking this kind of guidance.

3 / 3

Distinctiveness Conflict Risk

While 'autonomous coding agents' and 'human-in-the-loop workflows' are fairly distinctive, terms like 'tool integration' and 'permission systems' are broad enough to potentially overlap with general software architecture or security-related skills. The combination narrows it but individual triggers could conflict.

2 / 3

Total

11

/

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.