CtrlK
BlogDocsLog inGet started
Tessl Logo

subagent-creator

Guide for creating AI subagents with isolated context for complex multi-step workflows. Use when users want to create a subagent, specialized agent, verifier, debugger, or orchestrator that requires isolated context and deep specialization. Works with any agent that supports subagent delegation. Triggers on "create subagent", "new agent", "specialized assistant", "create verifier". Do NOT use for Cursor-specific subagents (use cursor-subagent-creator instead).

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/skills-catalog/skills/(creation)/subagent-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body is well-structured with concrete templates and complete example subagents, and the creation process is clearly sequenced with a checklist. Its main weaknesses are conceptual padding Claude does not need and the total absence of progressive disclosure — four full examples are inlined in SKILL.md rather than split into reference files.

Suggestions

Remove or drastically shorten the 'What are Subagents?' concept section — Claude already knows what subagents are; keep only the subagent-vs-skill decision tree, which is the genuinely novel guidance.

Move the four full example subagents (verifier, debugger, security-auditor, code-reviewer) into a references/examples.md file and keep one-line summaries in SKILL.md, cutting the body roughly in half.

Add an explicit final validation step to the creation process, e.g., confirm the written frontmatter parses as YAML and mentally test the description against the 'does this trigger correctly' check from the Quality Checklist.

DimensionReasoningScore

Conciseness

The body is mostly efficient template-driven guidance, but the 'What are Subagents?' section and its characteristics bullets explain a concept Claude already knows, and the best-practices/checklist sections could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.

3 / 5

Actionability

Four complete, copy-paste-ready example subagents (verifier, debugger, security-auditor, code-reviewer) plus a concrete frontmatter template give mostly executable guidance; the bracketed placeholder templates are the only minor gap, fitting anchor 4 rather than the fully-executable anchor at 5.

4 / 5

Workflow Clarity

The creation process is a clear three-step sequence (Define the Purpose → Configure the Metadata → Write the Subagent Prompt) with a Quality Checklist checkpoint, but there is no explicit step validating the created file (e.g., that frontmatter parses or the description triggers correctly as a test), matching the 'minor validation gaps' anchor.

4 / 5

Progressive Disclosure

There are no bundle files at all; everything lives in a single ~300-line SKILL.md, with roughly half of it being four full example subagents inlined that clearly belong in a separate references file, matching the 'content that should be separate is inline' anchor despite good in-file section organization.

3 / 5

Total

14

/

20

Passed

Description

82%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 an explicit use-when clause, quoted trigger phrases, role synonyms, and a negative trigger that disambiguates the closest competing skill. Its only weakness is that the 'what' stays at the level of one general capability rather than enumerating the concrete creation actions the skill guides.

DimensionReasoningScore

Specificity

The description names the domain and one concrete capability ("creating AI subagents with isolated context for complex multi-step workflows") but does not enumerate several specific actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

It clearly answers both 'what' (guide for creating AI subagents with isolated context) and 'when' ("Use when users want to create a subagent, specialized agent, verifier, debugger, or orchestrator...") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Explicit quoted triggers ("create subagent", "new agent", "specialized assistant", "create verifier") plus role synonyms (verifier, debugger, orchestrator) give good natural keyword coverage, though a few common variations users might say (e.g., delegate/spawn an agent, agent definition) are missing, placing it just below the comprehensive-coverage anchor.

4 / 5

Distinctiveness Conflict Risk

The skill has a clear niche (subagent creation) and explicitly disambiguates the nearest conflict ("Do NOT use for Cursor-specific subagents (use cursor-subagent-creator instead)"), giving minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-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.