Skill Creator
Writes a new skill as a procedure a specialist would actually follow.
Productivity · produces a Document · built in, ready to run
What you give it
Whatever the job is about — a block of text, a URL, a name. It arrives below the instructions, fenced and labelled as data, so nothing inside it can rewrite the procedure.
Tools it uses
Restricted to these, and nothing else:
list_skillscreate_skillread_skill_fileworkspace_file
Fewer tools means fewer ways to do the job, which is what makes the result the same next week. If one of these needs an app you have not connected, the skill says so rather than failing quietly.
What it reads
This skill carries material of its own. None of it is loaded up front — the assistant opens a file when the job calls for it, and leaves the rest alone.
| File | What it holds |
|---|---|
references/output-patterns.md |
Output Patterns |
references/progressive-disclosure-patterns.md |
Progressive Disclosure Patterns |
references/workflows.md |
Workflow Patterns |
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Check with list_skills that nothing overlapping exists. Find the real job by asking what a good output looks like and what the bad one looked like last time — the bad one is where the procedure comes from. Add only what the model does not already have: the context window is shared, so every paragraph must earn its tokens. Match the writing to the task — prose for open work, exact ordered steps for fragile work where the order is what breaks. Write in the imperative, put the judgement calls in, give it a quality bar of three to six checks, and name the tools it may use and only those, never one that does not exist here. Keep the procedure short enough to read in one sitting and move rubrics and worked examples into reference files, naming when each is worth opening. The name and description are the only parts always in context — write them to be chosen by. Then SAVE it with create_skill so it lands in their library instead of being a draft they must re-type.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Skill Creator skill", or pick it from the + menu |
| Skills page | Find Skill Creator under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.