CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-development

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

65

Quality

57%

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 ./plugins/plugin-dev/skills/agent-development/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

72%

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 excels at trigger term coverage and distinctiveness, providing many natural phrases users would say when needing agent development help for Claude Code plugins. However, it is weak on specifying what the skill actually does — it reads more like a trigger list than a capability description. Adding concrete actions (e.g., 'Generates agent YAML files with frontmatter, writes system prompts, configures tool permissions') would significantly improve it.

Suggestions

Add explicit capability statements describing what the skill does, e.g., 'Generates agent definition files with YAML frontmatter, writes system prompts, configures tool permissions and color schemes for Claude Code plugin agents.'

Restructure to lead with 'what it does' followed by 'Use when...' to clearly separate capabilities from trigger conditions, rather than having the entire description be trigger-focused.

DimensionReasoningScore

Specificity

The description mentions some domain-specific concepts like 'agent structure', 'system prompts', 'triggering conditions', 'agent frontmatter', and 'agent development best practices for Claude Code plugins', but it doesn't list concrete actions the skill performs (e.g., 'generates agent YAML frontmatter', 'writes system prompts'). It focuses more on when to trigger than what it actually does.

2 / 3

Completeness

The description has a strong 'when' component with explicit trigger phrases, but the 'what does this do' part is weak — it says 'needs guidance on agent structure, system prompts, triggering conditions' but doesn't clearly state what the skill produces or does (e.g., generates agent files, provides templates, writes configurations). The 'what' is only implied through the trigger terms.

2 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'create an agent', 'add an agent', 'write a subagent', 'agent frontmatter', 'agent tools', 'agent colors', 'autonomous agent'. These are realistic phrases a user would naturally use when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The description is clearly scoped to Claude Code plugin agent development, with very specific trigger terms like 'agent frontmatter', 'subagent', and 'Claude Code plugins'. This is a distinct niche unlikely to conflict with other skills.

3 / 3

Total

10

/

12

Passed

Implementation

42%

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 suffers significantly from verbosity and redundancy—the same information (naming rules, DO/DON'T lists, field descriptions) appears multiple times. While the structure and progressive disclosure are well done, the content would benefit greatly from being cut by 40-50%, removing duplicate sections and trusting Claude's existing knowledge of YAML, markdown, and basic naming conventions.

Suggestions

Eliminate redundant sections: the Quick Reference repeats the frontmatter fields and DO/DON'T lists already covered in detail above. Consolidate into a single occurrence of each.

Remove explanations of concepts Claude already knows (what YAML frontmatter is, what lowercase-hyphens means, what markdown format is) and focus only on the plugin-specific schema and conventions.

Add a complete, copy-paste-ready agent file example (not just a template with placeholders) showing a realistic agent like a code-reviewer with filled-in description, examples, and system prompt.

Add explicit feedback loops to the workflow: what specific errors to look for during validation, how to fix common issues, and concrete verification criteria for testing agent triggering.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~300+ lines, with significant redundancy. The frontmatter fields summary table repeats information already covered in detail. The DO/DON'T lists appear twice (in System Prompt Design and Quick Reference). Validation rules repeat naming constraints already stated. Much of this content (what YAML frontmatter is, how markdown files work, basic naming conventions) is knowledge Claude already possesses.

1 / 3

Actionability

The skill provides concrete format templates and examples of agent file structure, which is helpful. However, much of the guidance is descriptive rather than executable—there are no actual runnable code snippets, the referenced scripts (validate-agent.sh, test-agent-trigger.sh) don't exist inline, and the AI-assisted generation section provides a prompt template but not a complete working example of a finished agent file.

2 / 3

Workflow Clarity

The Implementation Workflow section provides a 9-step sequence, and there's a validation step mentioned (step 7), but the validation is delegated to an external script without showing what it checks. There are no explicit feedback loops (e.g., what to do if validation fails, how to iterate). The testing section is vague—'Check Claude loads the agent' lacks concrete verification steps.

2 / 3

Progressive Disclosure

The skill has a clear overview section, well-organized headers, and appropriately references external files (references/, examples/, scripts/) for detailed content. Navigation is one level deep with clearly signaled references at the end. The Quick Reference section provides a good summary for quick access.

3 / 3

Total

8

/

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
anthropics/claude-plugins-official
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.