This skill should be used when the user asks to create a new skill, repair an existing skill, improve trigger descriptions, reorganize skill structure, or make a Claude skill more reusable and internally consistent.
SkillScore73Maintained
Automatic
◆AI Engineer pack
Last verified 8/8/2026
What it changes
Passed 13 of 18 test cases with the skill, and 7 of 18 without it.
Without skill36%
With skill73%
Checks it passed that the model alone missed
The response includes validating frontmatter syntax parsing
The output declines to treat the git hook as a skill creation request
The response directs moving the large schema example into an examples subfolder
and 7 more in the full report
8 fixed8 passed either way6 still failing0 broke
Pass-rate lift
+36 pp
Tokens
+40%
Agent turns
0%
Response time
-28%
Model gemini-3.6-flashMeasured 8/8/2026v116 of 22 cases passed with skill · 18 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
We are setting up a local skill for Kubernetes log analysis. Write the frontmatter header for this new skill's primary entry file.
What was checked, without and with the skill
Checked
Without skill
With skill
The frontmatter description field uses third-person trigger phrasing containing sample quotes
Missed
Passed
The frontmatter includes a name field matching the skill identifier
Passed
Passed
case-07 · gemini-3.6-flash · 8/8/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md126 lines4 files
Skill Development
Use this skill to create or repair Claude skills in the current local environment, not in an abstract plugin template.
Goal
Produce a skill that is:
easy to trigger,
lean at the SKILL.md layer,
backed by real references/, examples/, and scripts/ files when they are mentioned,
free of dead local references.
Core rules
Keep one skill = one durable job.
Treat the frontmatter description as the main trigger surface.
Keep SKILL.md focused on workflow and boundaries.
Move detailed catalogs, templates, and long explanations into references/ or examples/.
Do not mention files that do not exist.
Do not inherit stale names, agents, or sibling skill references without verifying they exist locally.
Default workflow
1. Inspect the current environment first
Before writing anything:
inspect the target skill directory,
inspect neighboring skills that already solve a similar problem,
verify which agents, commands, and sibling skills actually exist,
identify stale references before adding new ones.
Use the local inventory as the authority. Do not write guidance against an imagined plugin layout.