Use when users want to create, revise, or scaffold a Codex skill from a plain-language brief. Especially relevant when they ask for a new SKILL.md, want to convert workflow requirements into a reusable skill, or need help defining trigger conditions, structure, bundled resources, or UI metadata for a skill.
SkillScore91Maintained
Automatic
◆AI Engineer pack
Last verified 8/3/2026
What it changes
Passed 20 of 22 test cases with the skill, and 3 of 22 without it.
Without skill14%
With skill91%
Checks it passed that the model alone missed
Generates an agents/openai.yaml file
Includes a clear Goal section at the top
Includes an agents/openai.yaml metadata file
and 19 more in the full report
19 fixed1 passed either way0 still failing2 broke
Pass-rate lift
+77 pp
Tokens
-11%
Agent turns
0%
Response time
-36%
Model gemini-3.6-flashMeasured 8/3/2026v120 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 19 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 19
Prompt
Update this existing skill draft that helps convert JavaScript files to TypeScript. Make the triggers clearer and eliminate unnecessary filler text without altering core steps.
What was checked, without and with the skill
Checked
Without skill
With skill
Preserves existing valid workflow steps
Passed
Passed
Refactors the description to start with 'Use when...'
Missed
Passed
case-12 · gemini-3.6-flash · 8/3/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md131 linessingle file
Meta Skill Generator
Turn a user's workflow brief into a concise, production-ready SKILL.md. Prefer shipping a minimal useful skill over an ornate one.
Default to English unless the user explicitly asks for another language.
Goal
Create or update skills that:
trigger on the right requests
encode only task-specific knowledge Codex would not already know
use the lightest structure that still keeps execution reliable
Intake
Collect only the minimum inputs needed to design the skill:
what job the skill should do
what kinds of user requests should trigger it
what output the skill should help produce
whether the task needs scripts/, references/, or assets/
any required tone, constraints, frameworks, or file formats
If the brief is incomplete, infer sensible defaults and note assumptions briefly after the draft instead of blocking.
Workflow
Distill the request into a one-sentence mission.
Choose the simplest structure that fits:
workflow-based for stepwise procedures
task-based for multiple operations
reference-based for policies or specifications
capability-based for multi-feature systems
Write frontmatter:
name: short, stable, hyphen-case
description: explicit trigger conditions; start with Use when...
Draft the body with only the sections the skill actually needs. Common sections:
Create new skills, improve existing skills, and test skill quality. Use when the user wants to build a skill from scratch, turn a workflow into a reusable skill, improve or refactor an existing SKILL.md, test how well a skill performs, optimize a skill's description so it triggers correctly, or asks "how do I make a skill for X". This is the meta-skill — it builds all other skills.