ai-agents-architect

Expert in designing and building autonomous AI agents. Masters tool use, memory systems, planning strategies, and multi-agent orchestration. Use when: build agent, AI agent, autonomous agent, tool ...

1.13x

Quality

51%

Does it follow best practices?

Impact

82%

1.13x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-ai-agents-architect/SKILL.md

Quality

Discovery

67%

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 establishes a clear domain focus on AI agents and includes an explicit 'Use when' clause, which is good. However, it relies on high-level capability categories rather than concrete actions, and the truncated trigger term list ('...') reduces both trigger quality and distinctiveness. The description would benefit from more specific actions and a complete list of trigger terms.

Suggestions

Replace high-level categories with concrete actions (e.g., 'Designs agent architectures, implements tool-calling loops, builds memory/retrieval systems, orchestrates multi-agent workflows').

Complete the trigger term list without truncation, adding natural variations like 'chatbot', 'agentic', 'LLM agent', 'ReAct', 'agent framework'.

Dimension	Reasoning	Score
Specificity	Names the domain (AI agents) and lists some capability areas (tool use, memory systems, planning strategies, multi-agent orchestration), but these are high-level categories rather than concrete actions like 'design agent architectures' or 'implement tool calling loops'.	2 / 3
Completeness	Clearly answers both what (designing and building autonomous AI agents with specific capability areas) and when (explicit 'Use when:' clause with trigger terms), meeting the rubric requirement for explicit trigger guidance.	3 / 3
Trigger Term Quality	Includes some natural keywords (build agent, AI agent, autonomous agent, tool) but the list is truncated with '...' and misses common variations users might say like 'chatbot', 'assistant', 'agentic workflow', 'LLM agent', or 'agent framework'.	2 / 3
Distinctiveness Conflict Risk	The AI agent focus provides some distinctiveness, but 'tool use' and 'planning strategies' are broad enough to potentially overlap with general coding skills or LLM integration skills. The truncated trigger list also reduces clarity.	2 / 3
	Total	9 / 12 Passed

Implementation

35%

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

This skill provides a reasonable conceptual overview of agent architecture patterns but fails to deliver actionable, executable guidance. The Sharp Edges table is particularly problematic with truncated solutions, and the code blocks contain bullet-point pseudocode rather than working examples. The anti-patterns section has headers but no content.

Suggestions

Replace pseudocode bullet points in Patterns section with actual executable code examples (e.g., a working ReAct loop implementation)

Complete the Sharp Edges table solutions - each 'Solution' cell currently ends with a colon and no actual code or guidance

Add content to the Anti-Patterns section or remove the empty headers entirely

Include concrete tool schema examples and actual function calling code rather than abstract descriptions

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some unnecessary framing (role description, capabilities list) that Claude already knows. The patterns section could be tighter.	2 / 3
Actionability	The code blocks contain pseudocode/bullet points rather than executable code. The Sharp Edges table references solutions but doesn't show them - entries like 'Always set limits:' are incomplete with no actual code.	1 / 3
Workflow Clarity	Patterns describe workflows conceptually (ReAct, Plan-and-Execute) but lack concrete implementation details, validation checkpoints, or error recovery steps. The Sharp Edges table hints at issues but solutions are truncated.	2 / 3
Progressive Disclosure	References related skills at the end but doesn't link to detailed documentation. The content is somewhat organized into sections but anti-patterns are empty headers with no content, and there's no clear navigation to deeper resources.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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: boisenoise/skills-collections
Commit: 5c5ae21

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.