Turn your checklists into Claude skills
If you keep pasting the same instructions into Claude, write them once as a skill: one SKILL.md file that Claude Code uses when the job comes up, or when you call it by name.
Skip the reading: hand it to Claude
Copy the whole guide and paste it into Claude, or install it as a Claude Code skill so it’s always there.
Save it as ~/.claude/skills/turn-your-checklists-into-skills/SKILL.md, then ask Claude Code to “turn your checklists into claude skills”.
The prompts
Write my first skill
Paste into Claude Code.
Help me turn a task I repeat into a Claude Code skill. The task: [DESCRIBE IT]. Interview me first, one question at a time (no more than 8): what a good result looks like, the steps in order, what to check before finishing, the files or links it needs, the tone, and what it must never do. Then write ~/.claude/skills/[short-name]/SKILL.md with: - a name and a one-sentence description saying when to use it (start with "Use when...") - the steps as a numbered list - a short "Never" list - a final check before saying it's done Keep it under 80 lines. Show it to me before saving.
Setup
Pick the task you explain to Claude (or a person) most often: a weekly report, replying to reviews, writing product descriptions.
Open Claude Code and paste the prompt below. Answer its questions.
It saves the skill as ~/.claude/skills/<name>/SKILL.md.
Use it by describing the job, or type a slash and the skill's name.
/your-skill-nameWhen it gets something wrong, ask Claude to update the skill so it doesn't happen again.
What I use
- Claude CodeLoads skills from your skills folder.
- Skills docsOfficial guide to writing skills.
- My guidesEvery guide has a 'Download as a Claude skill' button.
Worth knowing
- Write the skill like a brief for a new hire: the order, the checks and the never-do list. Vague skills give vague results.
- The description line matters most. It's how Claude decides when to use the skill.