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.
69
Quality
68%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/autonomous-agent-patterns/SKILL.mdQuality
Discovery
100%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-crafted skill description that excels across all dimensions. It provides specific capabilities (tool integration, permission systems, browser automation, human-in-the-loop workflows), uses natural trigger terms users would actually say, and includes an explicit 'Use when...' clause with clear selection criteria. The description carves out a distinct niche for agent-building that won't conflict with general coding skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'tool integration, permission systems, browser automation, and human-in-the-loop workflows'. These are distinct, actionable capabilities rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Design patterns for building autonomous coding agents. Covers tool integration, permission systems, browser automation, and human-in-the-loop workflows') and when ('Use when building AI agents, designing tool APIs, implementing permission systems, or creating autonomous coding assistants'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'AI agents', 'tool APIs', 'permission systems', 'autonomous coding assistants', 'browser automation'. These cover common variations of how users might describe agent-building tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on autonomous agent design patterns with distinct triggers like 'AI agents', 'tool APIs', 'permission systems', and 'autonomous coding assistants'. Unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a pure index/table of contents with no substantive content in the main file. While concise, it provides zero actionable guidance - a reader must click through to sub-skills to learn anything. The organization of sub-skills is confusing with redundant numbering schemes and no grouping or descriptions to help navigate.
Suggestions
Add a brief 'Quick Start' section with a concrete example or minimal code showing the core agent loop pattern before directing to sub-skills
Group the sub-skills into logical categories (e.g., 'Core Architecture', 'Tools', 'Permissions', 'Browser', 'Advanced') with 1-sentence descriptions of each
Include a recommended reading order or decision tree for which sub-skills to consult based on the user's specific goal
Fix the confusing dual-numbering system - either use the hierarchical numbers (1.1, 1.2, 2.1) OR sequential numbers, not both
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean - just a brief description of when to use the skill and a clean index of sub-skills. No unnecessary explanations or padding. | 3 / 3 |
Actionability | The skill body contains no concrete guidance, code, commands, or examples - it's purely a table of contents pointing to other files with no actionable content itself. | 1 / 3 |
Workflow Clarity | No workflow is described. The numbered list appears to be a navigation index rather than a sequence of steps. There's no guidance on how to approach building an agent or in what order to consult the sub-skills. | 1 / 3 |
Progressive Disclosure | References are one level deep and clearly linked, but the organization is poor - the numbered list is confusing (mixing section numbers like '1.1', '2.1' with sequential numbers 1-16), and there's no categorization or description of what each sub-skill covers. | 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
3395991
- 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.