Awesome Claude Prompts Unofficial

Turn a repeated task into a skill

Describe a workflow you repeat and have Claude Code save it as a skill, so you or your team can run it later as a slash command.

Task: Turn a repeated task into a skill · Other tasks

Fill in the details

Lowercase letters, numbers and hyphens. It becomes the command, for example /release-check.

List the steps the way you would explain them to a new teammate.

Copy your prompt

This site doesn't run Claude or show model output. Results depend on your input and the model you use.

2 required fields are empty.

What you type is kept in this tab's session storage so a reload doesn't lose it. Use "Clear this task" to remove it. Browsers can restore session data when they reopen tabs, so closing a tab isn't a guaranteed way to erase it.

When to use this template

  • You keep typing the same multi-step instructions into Claude Code, such as a pre-release check, a review checklist or a data export.
  • A workflow lives in one person's head, and you want the team to run it the same way with one command.
  • You have just finished a task in a session and want to keep the steps that worked, while the details are still fresh.

When not to use it

  • The thing you want is a standing rule rather than a workflow, such as "use named exports". Put it in CLAUDE.md instead.
  • The action must happen every time without exception, such as formatting after every edit. A hook runs deterministically; a skill depends on being invoked.
  • You have only done the task once. Wait until the steps have settled, or the skill will record a process you are still changing.

Why this structure

  • The name field becomes the slash command, so the prompt states it once and reuses it for the folder name, matching how Claude Code finds skills: a folder per skill with a SKILL.md inside.
  • The location choice decides who gets the skill. A project skill in .claude/skills/ travels with the repository; a personal skill in ~/.claude/skills/ stays on your machine.
  • The invocation choice matters for workflows with side effects. disable-model-invocation: true means Claude does not start the skill on its own, only when you type the command.
  • Asking for a description of what the skill does and when to use it matters because Claude reads that description to decide when a skill is relevant.
  • Telling Claude to look up the project's real commands keeps the skill from recording guessed commands that fail the first time someone runs it.
  • The closing rule shows you the file before anything runs, and keeps a skill that deploys, deletes or sends something from being tried out on the spot.

Example input (fictional)

Skill name
release-check
What the skill should do
Run the linter and the full test suite. If both pass, list the commits since the last tag and draft a commit message for the staged changes. Stop and report if anything fails.
Where to save it
a project skill in .claude/skills/, which the team gets once it is committed to the repository
Who can start it
only me, by typing the command; add disable-model-invocation: true to the frontmatter

Follow-ups to send Claude

  • Run /release-check now. The steps only read files and run tests, so it is safe here.
  • Add a step that stops if there are uncommitted changes outside the staged files.
  • Look through this repository's scripts, Makefile and README. Which other multi-step tasks are repeated often enough to become skills?

Common mistakes

  • Writing a vague description, such as "helps with releases". Claude uses it to decide when the skill applies, and you will not recognize it in a list later.
  • Letting Claude start a skill with side effects on its own. Keep deploys, data changes and messages to manual invocation.
  • Packing every detail into SKILL.md. A long file is harder to maintain; move reference material into separate files next to it.

See all templates

Sources