A collection of real-world SKILL.md examples and installation guides for AI coding tools.
A SKILL.md is a structured profile that tells AI tools who you are — your skills, experience, and how you work. When you add one to your environment, tools like Claude Code, VS Code Copilot, Cursor, and Codex give you better, more relevant output from the first message.
This repo contains:
- Example SKILL.md files for different roles
- Installation guides for the major AI coding tools
- Everything you need to hand-write your own
Need one generated automatically from your CV? Try skillmdcreator.ai — it builds a personalised SKILL.md in 60 seconds from your CV, a job description, or a short form.
| Role | File |
|---|---|
| Full-Stack Engineer | examples/fullstack-engineer.md |
| Data Analyst | examples/data-analyst.md |
| Product Manager | examples/product-manager.md |
| Marketing Director | examples/marketing-director.md |
| UX Designer | examples/ux-designer.md |
| Tool | Guide |
|---|---|
| Claude Code | guides/claude-code.md |
| VS Code Copilot | guides/vscode-copilot.md |
| Cursor | guides/cursor.md |
| OpenAI Codex | guides/codex.md |
SKILL.md files follow the Agent Skills open standard — a YAML frontmatter block plus markdown content that any compatible AI tool can load as context.
---
name: your-profile-name
description: When to load this skill (used by AI tools to decide)
---
# Your Name — Role
## Expertise areas
- Skill 1
- Skill 2
## How you work
- Preference 1
- Preference 2The description field is important — AI tools read it to decide when to activate the skill. Make it specific about when the profile should be loaded.
- Claude Code:
~/.claude/skills/your-skill.md(personal) or.claude/skills/your-skill.md(project) - VS Code Copilot:
.agents/skills/your-skill.mdin your project - Cursor:
.cursor/skills/your-skill.mdin your project - Any AI chat: paste the content directly as context
See the installation guides for step-by-step setup.
- Pick the example closest to your role
- Copy it and replace every section with your own details
- Be specific — "5 years React, focused on complex SPAs" beats "JavaScript"
- Include preferences — how you like to work, what you avoid, your tooling
- Save it to the right folder for your AI tool
- Be specific about experience: years, scale, specific projects
- Name your tools: exact versions and libraries you use
- State your preferences: what you like, what you avoid, decision criteria
- Keep it scannable: AI tools read markdown well; use bullets and headers
- Don't exaggerate: the file is for the AI to help you, not a sales pitch
Writing a good SKILL.md from scratch takes an hour and most people understate their experience.
skillmdcreator.ai reads your CV (or a job description, or a short form) and produces a structured SKILL.md in 60 seconds — following the same patterns as the examples here but tailored to your actual background.
- Free preview before you pay
- $9 one-time for the full file
- $15 Pro for two persona variants
- GDPR compliant, data deleted after generation
Got a great SKILL.md for a role not covered here? Open a PR. Examples should be:
- Realistic (not aspirational fantasy)
- Specific (named tools, real years, actual preferences)
- Generic enough that others in the role will recognise themselves
MIT — use these examples however you like.