Claude Code · Skills guide
How to add, use, and fix Claude Code Skills
Start with one small skill. Add it to your project, try it with sample notes, and check the result.
1. Add Claude Code Skills
This example uses a local project. You need Claude Code installed and a folder you can edit.
- Open the project where you use Claude Code. Create a meeting-recap folder inside .claude/skills.
- Save the example below as SKILL.md inside that folder. Keep the name and description between the two --- lines.
- For access across projects, use the personal path instead. When adding an existing skill, keep its supporting files together.
- For this project
.claude/skills/meeting-recap/SKILL.md- For your projects on this computer
~/.claude/skills/meeting-recap/SKILL.md
The project path starts in your project folder. ~ means your home folder. Choose one location.
Practice example: your SKILL.md file
---
name: meeting-recap
description: Turn meeting notes into decisions and actions. Use when the user asks for a meeting recap.
---
Read the notes supplied by the user.
1. List the decisions.
2. Make an action list with an owner and due date.
3. Write "Not provided" for missing details. Do not invent them.
4. Return a draft for review. Do not send messages or change files.Using a downloaded skill? Read its instructions and supporting files before adding it.
2. Use Claude Code Skills
- In Claude Code, enter /meeting-recap with the sample notes below.
- Claude can also choose the skill when your request matches its description.
/meeting-recap
Sample meeting notes:
Maya will draft the proposal by Friday.
The team agreed to offer a two-week trial.
Someone needs to check the budget; no owner was chosen.Check the draft: Maya owns the proposal, Friday is its deadline, and the budget task has no named owner. If the answer adds facts, ask for a correction before using it.
3. Fix Claude Code Skills
- The skill does not appear
- Check the folder and SKILL.md filename. Ask Claude “What skills are available?” to check discovery.
- Claude does not choose it
- Try /meeting-recap directly. Make the description match the words you use in your request and check that the YAML header is valid.
- It runs on unrelated requests
- Narrow the description. Set disable-model-invocation: true in the header if you want to start it only by command.
If a downloaded skill fails after starting, read the first error. Check its required tools, files, and access. A skill folder does not install those for you.
Skills to try in Claude Code
71 skills in the JuicyAgents library include Claude Code setup steps. Start with one of these and try its fictional example first.
- Sales call preparationPrepare a focused sales-call brief from meeting notes and customer history, with evidence, questions, and a realistic next step.
- Content strategyChoose what to publish, improve or stop using audience evidence, existing content and production capacity.
- Website copywritingWrite page-specific website copy with a message map, supported claims and visible commercial terms.
- Visual designCreate an original, readable visual from a brief, with editable SVG artwork and optional exports when rendering tools are available.
- Business process documentationTurn team notes into a repeatable process with clear owners, decisions, exceptions, and completion checks.
- Support ticket triageOrganize customer issues into a review queue with evidence-based priorities and draft first responses.
