Agent Skills
Reusable bundles for specialized capabilities
Prerequisites
- Basic Claude Code usage
- Familiarity with slash commands
What You'll Learn
- Understand skill structure and triggers
- Use built-in skills effectively
- Create custom skills for your team
- Compose skills into workflows
Anatomy of a Skill
# .claude/skills/deploy.md
# Deploy to Production
When deploying to production, follow these steps:
1. Run `npm test` and ensure all tests pass
2. Build the project with `npm run build`
3. Check for type errors with `npm run typecheck`
4. Deploy using `vercel --prod`
5. Verify the deployment at production URL
6. Report success with the deployed URL
## Error Handling
If tests fail, fix errors before deploying.
If deployment fails, check Vercel logs.Numbered steps that Claude follows sequentially
Guidance for when things go wrong
How to Invoke Skills
/commitType the skill name as a slash command. Claude expands it into the full skill instructions.
/vercel:deployPlugin skills use namespace:skill format. The plugin provides specialized expertise.
Note: Skills are different from built-in commands like /help, /clear, or /compact. Those are CLI commands; skills are instruction bundles.
Popular Plugin Skills
/vercel:deployDeploy projects to Vercel with production settings
/code-review:code-reviewDeep code review for pull requests
/stripe:stripe-best-practicesStripe integration patterns and security practices
/feature-dev:feature-devGuided feature development with architecture focus
Where Skills Come From
PluginsInstalled plugins provide skills. View with /plugins. Example: Vercel, Stripe, Code Review plugins.
.claude/skills/Custom markdown files for project-specific workflows. Commit to git to share with your team.
~/.claude/skills/Personal skills available across all your projects.
Creating Your Own Skills
Create a markdown file in .claude/skills/ with clear instructions:
Good Skill Practices
- βClear, numbered steps
- βSpecific commands to run
- βError handling guidance
- βSuccess criteria
Avoid
- βVague instructions
- βOverly long prompts (adds to context)
- βSecrets or credentials
- βDuplicate plugin functionality
π‘ Pro Tips
- 1.Install plugins for specialized skillsβthe Vercel plugin gives you
/vercel:deploy, Stripe gives best practices. - 2.Skills expand into Claude's prompt, so keep them focused. Long skills use more context tokens.
- 3.Your skill instructions can reference other skills: "After testing passes, run the deploy workflow."
- 4.Commit project skills to git in
.claude/skills/βshare workflow knowledge with your whole team.
Master Claude Code faster
Get notified when new animated guides are released.
Subscribe to the newsletter