CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-creator

Create or adapt Claude Code agent definitions. Use when creating an agent, changing subagent configuration, selecting agent scope, or designing a specialized delegation role.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

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

Exemplary instruction-only skill body: a gated five-step workflow with explicit validation commands and a fix-before-complete loop, a lean overview that delegates detail to three real, condition-signaled reference files, and an exact caller-visible output contract. No structural weaknesses found.

DimensionReasoningScore

Conciseness

The body contains no re-explanations of concepts Claude already knows and no padding; even the portability paragraph ("Every path, command, fact, and cross-plugin reference... must be available in every target environment") is dense, non-obvious instruction. Lean and efficient — anchor 5.

5 / 5

Actionability

Guidance is fully concrete: exact commands ("uvx skilllint@latest check {agent-path}", "claude plugin validate {plugin-root}"), exact destination paths per scope, a complete minimal agent template, and an exact output contract. The template's placeholders are inherent to a creation skill and the flexibility is contextually justified. Anchor 5.

5 / 5

Workflow Clarity

Five ordered steps (Discover, Resolve Requirements, Write, Place, Validate) each end with an explicit "Gate:" checkpoint, and the Validate step gives exact commands with a fix-every-error-before-completion feedback loop plus a session-restart instruction. This matches anchor 5 (clear sequence, explicit validation, error-recovery loop).

5 / 5

Progressive Disclosure

The body is a lean overview with an Authority Pointers section giving each of three references (agent-schema.md, agent-templates.md, agent-examples.md) a precise read-condition; all three files exist in the bundle, are reached by relative paths, and are one level deep. Anchor 5.

5 / 5

Total

20

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with a clear what and an explicit multi-branch "Use when" trigger clause in third-person voice. Its main weakness is thin action specificity and some missing natural synonyms, which slightly limit trigger coverage and distinctiveness from neighboring creation skills.

Suggestions

Expand the 'what' with 1-2 more concrete actions, e.g. "Create or adapt Claude Code agent definitions: frontmatter, tool permissions, and body workflow for .claude/agents files."

Add natural trigger synonyms users actually say, such as "writing an agent definition", "setting up a subagent", or ".claude/agents", to broaden matching.

Sharpen distinctiveness from adjacent creation skills by naming the artifact explicitly ("agent definition files in .claude/agents") rather than the general phrase "specialized delegation role".

DimensionReasoningScore

Specificity

"Create or adapt Claude Code agent definitions" names the domain plus exactly two concrete actions (create, adapt), but does not enumerate the work involved (frontmatter fields, placement, validation). This matches anchor 3 (domain and 1-2 concrete actions, not comprehensive); anchor 4 would require several specific listed actions.

3 / 5

Completeness

The description clearly answers "what" ("Create or adapt Claude Code agent definitions") and "when" with an explicit "Use when" clause listing four concrete trigger branches. This matches the anchor-5 example pattern of explicit what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

Triggers like "creating an agent", "changing subagent configuration", "selecting agent scope", and "designing a specialized delegation role" are natural phrases users would say, but common synonyms such as "agent definition", "subagent setup", or ".claude/agents" are missing. Good coverage with a few natural terms absent — anchor 4, not the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (Claude Code agent definitions) is mostly distinct with precise triggers, but it sits directly adjacent to plugin- and skill-creation skills, so a request like "create a specialized role" carries minor overlap risk. Anchor 4 (minor overlap with closely related skills) fits better than anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

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.