Claude Skill prompts that produce a SKILL.md you can actually install
Write the front matter, the when-to-use rule, the never-do list, and a second-input test. Official Skills only. Steal-ready examples live on the other Skills page.
In short: This page contains 15 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Spec the Skill
3 promptsOne trigger, one job
1/15✨ What it does
Claude specs a one-trigger Skill from [JOB] and [TRIGGER]. If the job needs two triggers, split it. Keep the never-do list.
Help me spec a Claude Skill. Job: [JOB]. Trigger: when the user [TRIGGER]. Never: [NOT]. Write: name, description for the front matter, 5 must-do, 5 never-do. Do not invent tools the Skill cannot call.
Pro tip: A Skill with five triggers is a personality. A Skill with one trigger is a tool.
When not to write a Skill
2/15✨ What it does
Claude picks Skill vs Project vs Cowork vs a pasted prompt. If it says no Skill, stop. Save the prompt in a doc instead.
I think I need a Skill for [JOB]. Tell me if a Project, Cowork, or a pasted prompt is enough. 5 rows. If [JOB] happens once a quarter, do not make a Skill.
Pro tip: Skills have a load cost. Do not spend it on a birthday email.
Front matter only
3/15✨ What it does
Claude writes valid YAML front matter for [NAME]. Paste it at the top of SKILL.md. Then write the body in a second step.
Write only the YAML front matter for a Skill: name [NAME], description [ONE SENTENCE], and any required extra fields I named: [FIELDS]. Valid YAML. No body yet.
Pro tip: Bad YAML is why Skills fail to load. Check the spaces before you write the essay.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Write SKILL.md
3 promptsFull SKILL.md draft
4/15✨ What it does
Claude writes a full SKILL.md from [NOTES] with a missing-input rule and never-do. Save it. Test on a second input before you trust it.
Write SKILL.md for [JOB]. Include: front matter, When to use, Inputs, Steps, Output, [VERIFY] if an input is missing, Never-do (no send, no pay, no delete unless I listed them). Markdown I can save. Use only [NOTES].
Pro tip: Never-do belongs in the file, not in your head. Future-you will forget.
Steps a second Claude can follow
5/15✨ What it does
Claude rewrites [STEPS] as numbered verbs with inputs. Paste that into SKILL.md. If a step needs chat history, it is not a Skill step.
Rewrite these steps so a second Claude, with no chat history, can run them: [STEPS]. Number them. Each step is one verb plus the input it needs.
Pro tip: If the step is use your judgment, it will not survive a new thread.
Output contract
6/15✨ What it does
Claude writes an 80-word Output contract for [NAME]. Put it in SKILL.md. If the last line is not a next action, the Skill will ramble.
Write the Output section for Skill [NAME]: sections, max length, and the last line the user must see (next action). Job: [JOB]. 80 words.
Pro tip: Skills without an output contract write novels. Put the cap in the file.
Test
3 promptsSecond-input test
7/15✨ What it does
Claude runs SKILL.md on [B] and lists 5 drifts. Fix those 5 lines in the file. Keep B only if the facts are yours.
Here is SKILL.md: [PASTE]. Here is input A I liked: [A]. Here is input B: [B]. Run as the Skill on B. Then list 5 places you left the file. Do not invent facts in B.
Pro tip: Install after B works. Not after A, which you already coached in chat.
Missing input test
8/15✨ What it does
Claude should stop and ask for [INPUT]. If it invents that input, the [VERIFY] line is too weak. Tighten it and retest.
Run as this Skill: [PASTE]. I will omit [INPUT]. You must stop and ask for it. Do not invent [INPUT].
Pro tip: This is the test that stops a Skill from inventing a client address.
Trigger test
9/15✨ What it does
Claude marks fire or ignore on 6 user lines. If a line wrongly fires, rewrite When to use. Save that sentence.
Here is SKILL.md: [PASTE]. Here are 6 user lines: [LINES]. For each, say fire or ignore. If it would fire on a line I did not intend, rewrite the When to use sentence.
Pro tip: A greedy trigger is how your finance Skill eats a joke about invoices.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Shrink and port
3 promptsCut a fat Skill
10/15✨ What it does
Claude cuts SKILL.md and lists removed sections. Save the small file. Restore one section only if a test fails.
Cut this SKILL.md to the smallest file that still does [JOB]: [PASTE]. Keep front matter, When to use, Never-do, Output. List removed sections.
Pro tip: Long Skills get partially loaded or skipped. Short wins.
Port from a chat you liked
11/15✨ What it does
Claude turns the reusable part of the chat into SKILL.md and drops secrets. Read the [VERIFY] list. Do not port a key or a customer name.
Here is a chat I liked: [PASTE]. Turn the reusable part into SKILL.md. Drop one-off jokes, names, and secrets. Add Never-do: no send. Tag anything unclear [VERIFY].
Pro tip: A good chat is not a Skill until you strip the names.
Port from the steal page
12/15✨ What it does
Claude rewrites a library Skill for [JOB] using [SAMPLES]. Save yours. Do not keep their never-do if it conflicts with yours.
I copied a Skill from a library: [PASTE]. Rewrite it for [JOB] and [CONSTRAINTS]. Keep the structure. Replace their company voice with mine from [SAMPLES]. Add my never-do.
Pro tip: The steal page is a start. Your never-do is the part that makes it yours.
Ship
3 promptsInstall checklist
13/15✨ What it does
Claude writes an install checklist for [NAME]. Tick every box. If the YAML is invalid, fix that before any other test.
Write a checklist to install Skill [NAME]: file path, YAML valid, trigger tested, second input tested, no secrets in the file, owner [OWNER].
Pro tip: Path mistakes are the common fail. Write the path down.
Team readme
14/15✨ What it does
Claude writes a 120-word teammate readme from [NOTES]. Put it next to SKILL.md, and name the person who may edit it.
Write a 120-word readme for teammates: what Skill [NAME] does, when to @ it, when to ignore it, who edits SKILL.md. From [NOTES] only.
Pro tip: If two people edit a Skill, you get a merge fight in prose. One editor.
Retire the Skill
15/15✨ What it does
Claude writes a retire note from [NOTES]. Archive the Skill file until [DATE], then tell the team what replaces it.
Write a retire note for Skill [NAME]: why we are turning it off, what to use instead, and that the file will be archived not deleted until [DATE]. From [NOTES].
Pro tip: Deleted Skills come back as folklore. Archive with a date.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides