Analyze large prompts, system instructions, or runbooks to identify sections extractable as standalone skills, then build them.
SkillScore73Maintained
Automatic
◆AI Engineer pack
Last verified 9/6/2026
What it changes
Passed 16 of 22 test cases with the skill, and 9 of 22 without it.
Without skill41%
With skill73%
Checks it passed that the model alone missed
Classifies the chunk as not a skill.
Assigns the chunk a marginal verdict classification.
Rejects the section from being built into a standalone skill.
and 7 more in the full report
9 fixed7 passed either way4 still failing2 broke
Pass-rate lift
+32 pp
Tokens
+100%
Agent turns
0%
Response time
-23%
Model gemini-3.6-flashMeasured 9/6/2026v216 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
Assess a prompt chunk that passes 1 evaluation criterion out of 6 (it is self-contained, but lacks distinct trigger, repeatable steps, baseline delta, focused scope, and sibling boundaries). What is the candidate classification?
What was checked, without and with the skill
Checked
Without skill
With skill
Classifies the chunk as not a skill.
Missed
Passed
case-16 · gemini-3.6-flash · 9/6/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md229 linessingle file
Prompt Decomposer
Accept a large prompt, system instruction set, or runbook. Identify which sections could become standalone skills, present candidates with rationale, and route approved candidates into the Skill Maker for creation.
When to use
You have a long system prompt and want to modularize it into skills
You inherited a monolithic instruction set and want to break it apart
You want to audit a prompt for skill-worthy patterns
You pasted a big block of text and want to know what's reusable
Workflow
Phase 1: Intake
Accept one of:
A pasted prompt (inline text in the chat)
A file path to a .md, .txt, or any text file containing instructions
A directory path containing multiple instruction files
If no input provided, ask:
"Paste your prompt or give me the file path. I'll analyze it for sections that could become standalone skills."
If the input is under 20 lines, push back:
"This is pretty short -- it might work better as a single skill. Want me to send it to the Skill Maker instead?"
Phase 2: Chunk
Segment the prompt into logical sections. Look for boundaries at:
Heading markers (H1/H2/H3, ##, bold headers)
Topic shifts (different task domains or tool contexts)
Behavioral blocks ("when X, do Y" conditional patterns)
Distinct workflow sequences (numbered steps with a clear start/end)
Tool-specific sections (sections scoped to one tool, API, or platform)
Ignore:
Preamble / personality / tone directives (these are rules, not skills)