AI skills are reusable sets of instructions saved as plain text files (SKILL.md format). When triggered by a slash command, Claude Code follows the skill's instructions to complete a specific task. They encode expert-level workflows that can be shared and reused.

Run the install command from the skill's page on cucinalabs.com/skills. For example: 'npx cucina-skills install review-pr'. The skill file is downloaded to your project's .claude/skills/ directory and becomes available immediately.

Yes. Create a plain text file in .claude/skills/ with a frontmatter header (name and description) and instruction body. The file name should match the skill name. Any repeated prompt with consistent structure is a good candidate for a custom skill.

When you type a slash command, Claude searches for a matching skill file in your project's .claude/skills/ folder and your home directory's ~/.claude/skills/ folder. It loads the skill's instructions into the current session and follows them to complete the task.

Browse the skill directory at cucinalabs.com/skills. Skills are organized by product lifecycle phase: Discovery, Strategy, Design, Build, Launch, and Measure. Each skill has a description and an install command.

Project skills live in .claude/skills/ inside your project and apply to that project only. Global skills live in ~/.claude/skills/ in your home directory and are available in every project. If both have the same name, the project skill takes precedence.

Yes. When you invoke a skill, Claude has both the skill's instructions and your CLAUDE.md active simultaneously. Your project conventions, don'ts, and domain context still apply. Skills add to your configuration rather than replacing it.

Commit the .claude/skills/ folder to your repository. When teammates clone or pull the project, they get the skills automatically. For cross-project skills, maintain a shared skills repository that team members install from.

No. Skills are written in plain text, not code. If you can write clear instructions for a colleague — what to do, what format to use, what to avoid — you can write a skill. The file format is straightforward: a short header followed by your instructions.

Check three things: the file exists in .claude/skills/ with the correct name, the frontmatter header has a valid name field, and the instructions are specific enough. If the skill runs but produces wrong output, refine the instructions the same way you would refine a prompt — add constraints, examples, and don'ts.