CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-creator

Create high-quality Claude Code agents from scratch or by adapting existing agents as templates. Use when the user wants to create a new agent, modify agent configurations, build specialized subagents, or design agent architectures. Guides through requirements gathering, template selection, and agent file generation following Anthropic best practices (v2.1.63+).

66

Quality

81%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

This skill is highly actionable with an excellent multi-phase workflow, concrete YAML examples, and thorough validation checkpoints. However, it is severely bloated—the Common Mistakes section (10 items with full examples), Testing section (4 methods with tables), and Anti-Patterns section contain substantial content that either restates earlier guidance or teaches Claude things it already knows. Much of this inline content should be moved to reference files to respect token budget.

Suggestions

Move the 'Common Mistakes' section (10 detailed items) to a reference file like `references/agent-common-mistakes.md` and replace with a brief 2-3 line summary linking to it.

Move the 'Testing Your Agent' section to `references/agent-testing.md`—it's ~150 lines of content that's only needed after creation, not during the main workflow.

Consolidate 'Anti-Patterns to Avoid' into the relevant workflow phases or the common mistakes reference rather than having a separate inline section that partially duplicates the Description Writing Guide and Common Mistakes.

Remove explanatory text that Claude already knows (e.g., explaining what action verbs are, why vague descriptions are bad, what 'single responsibility' means) and keep only the concrete examples and rules.

DimensionReasoningScore

Conciseness

Extremely verbose at ~600+ lines. Contains extensive sections on common mistakes (10 detailed mistakes with examples), testing (multiple methods with tables), and anti-patterns that largely teach Claude things it already knows (e.g., 'don't make descriptions vague', 'don't use wrong model'). The common mistakes section alone is massive and mostly restates guidance already given in earlier sections. Much of this could be condensed to 1/3 the size.

1 / 3

Actionability

Highly actionable with concrete YAML examples for every tool pattern, executable bash commands for discovery, specific validation commands (skilllint, claude plugin validate), complete agent file templates with real frontmatter, and step-by-step workflows with exact file paths and tool invocations.

3 / 3

Workflow Clarity

Excellent 8-phase workflow with clear sequencing from Discovery through Post-Creation Validation. Includes explicit validation checkpoints (Phase 6 checklist, Phase 8 post-creation validation), feedback loops (iterative testing process), and specific verification commands. The plugin agent creation path includes a critical validation step to ensure plugin.json wasn't corrupted.

3 / 3

Progressive Disclosure

References external files well (agent-schema.md, agent-templates.md, agent-examples.md, subagent-contract skill), but the main SKILL.md itself is a monolithic wall containing massive inline sections (Common Mistakes, Testing, Anti-Patterns, Tool Patterns) that should be split into reference files. The testing section alone could be its own reference document.

2 / 3

Total

9

/

12

Passed

Description

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 strong, well-crafted skill description that clearly communicates what the skill does and when to use it. It uses third-person voice, lists specific concrete actions, includes natural trigger terms, and has an explicit 'Use when...' clause. The specificity around Claude Code agents and version numbering makes it highly distinctive.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Create high-quality Claude Code agents from scratch', 'adapting existing agents as templates', 'modify agent configurations', 'build specialized subagents', 'design agent architectures', and 'requirements gathering, template selection, and agent file generation'.

3 / 3

Completeness

Clearly answers both 'what' (create agents from scratch or templates, modify configurations, build subagents, design architectures) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios. Also describes the process (requirements gathering, template selection, file generation).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'create a new agent', 'modify agent configurations', 'build specialized subagents', 'design agent architectures', 'template selection', 'agent file generation'. These cover the natural ways users would phrase requests about agent creation.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche focused specifically on Claude Code agent creation and configuration. The mention of 'Claude Code agents', 'subagents', 'agent architectures', and 'Anthropic best practices (v2.1.63+)' makes it very unlikely to conflict with other skills.

3 / 3

Total

12

/

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 (1007 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
Jamie-BitFlight/claude_skills
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.