Claude / Skill setup
Create a Claude Skill with /skill-creator
A Claude Skill is a reusable bundle of instructions, resources, and optional scripts that Claude can load when a task matches the workflow.
Claude open4 minutesBeginner
Use /skill-creator from the composer
Open Claude and choose the project that should own the Skill (or ask for a general Skill if you want it everywhere). Type /skill-creator and describe the repeated work you want Claude to preserve. Give the Skill a short name you will remember, then test it with one small prompt.
Follow the setup path in Claude
- 1
Decide whether the Skill is for one project or all of them
- Why
- A project Skill sees that project's files, conversations, and working context. A general Skill is available across every project you open in Claude.
- Action
- Open Claude and use the project selector if the Skill belongs to one project. If you want the Skill available everywhere, tell Claude you want a general Skill rather than a project-specific one.
- Result
- Claude is open in the workspace where the Skill should be created and tested.
- Tip
- Paste a completed example thread as source material so skill-creator can learn the pattern from a real output.
- 2
skill-creator turns the rough workflow into a Skill
- Why
- Claude Skills need a clear description, reusable instructions, and sometimes supporting files. The skill-creator entry gives Claude a focused path for turning an example workflow into that durable package.
- Action
- Type /skill-creator in the composer and tell Claude what repeated task the Skill should handle.
- Result
- Claude switches from a normal reply into Skill-building mode and asks for any missing details before drafting the Skill.
- Tip
- The /skill menu can show several existing Skills. Use /skill-creator when you are making or improving a Skill. Choose a finished Skill name only when you want to use it.
- 3
A short trigger name makes the Skill easy to call
- Why
- The name is what you will type later, and the description is what helps Claude decide when the Skill applies automatically.
- Action
- Ask for a short lowercase name such as meeting-recap, source-audit, or ui-builder. Include one trigger sentence that names the real request a future thread should recognize.
- Result
- The Skill has a memorable name, a specific trigger, and instructions grounded in your source example.
- Tip
- Avoid broad names like writing-helper or productivity. A good Skill name points to the concrete output or workflow.
- 4
One small test proves Claude can find the Skill
- Why
- A Skill is not finished until Claude can select it in a realistic thread and produce the saved kind of result.
- Action
- Start with a low-risk prompt and invoke the Skill deliberately with its slash command or a phrase like "use the meeting-recap skill." Give it a small sample input.
- Result
- Claude loads the Skill and follows the workflow closely enough that you can trust the next larger run.
- Tip
- If Claude misses an important rule, ask skill-creator to update the Skill before you rely on it for real work.