Agent Skills
VS Code
How VS Code finds, installs and reads a skill, from its own docs, checked 26 Oct 2026.
Where it looks for skills
| Scope | Folders it reads |
|---|---|
| This project | .github/skills/, .claude/skills/ and .agents/skills/ |
| All your projects | ~/.copilot/skills/, ~/.claude/skills/ and ~/.agents/skills/ |
From VS Code’s own docs, checked 26 Oct 2026.
Install a skill
- Copy the skill’s folder, with its SKILL.md at the top, into .github/skills/ in your project, or into ~/.copilot/skills/ for all your projects.
- Keep the folder named exactly as the name field in its SKILL.md, as The skill folder explains.
- On qai.io/skills, every skill’s page has the steps for VS Code, starting from Install skills in VS Code.
Fields it reads
Beyond the six fields every SKILL.md can hold, VS Code reads argument-hint, user-invocable, disable-model-invocation and context.
SKILL.md sets out the six fields and their limits.
How the format check reads it
The format check on qai.io/skills reads a skill for VS Code as VS Code & Copilot: VS Code reads skills one folder below .github/skills, .claude/skills or .agents/skills and falls back to the folder name when the name is missing or differs; GitHub's Copilot docs require the exact name SKILL.md.
Where that differs from the Agent Skills spec row, rule by rule:
| Rule | Agent Skills spec | VS Code & Copilot |
|---|---|---|
| One SKILL.md per skill | Warns | Notes it |
| Frontmatter starts on line 1 and is closed | Fails | Warns |
| Frontmatter is valid YAML and reads as written | Fails | Warns |
| No symbolic links in the skill | Warns | Notes it |
| Has a name | Fails | Warns |
| The name is at most 64 characters | Fails | Warns |
| The name matches its folder | Fails | Warns |
| The name avoids the reserved words anthropic and claude | Warns | Not checked |
| The name has no angle brackets | Fails | Warns |
| The name has no namespace prefix | Fails | Warns |
| The name has no hidden characters or odd spacing | Fails | Warns |
| The name says what the skill does | Notes it | Not checked |
| Has a description | Fails | Warns |
| The description is at most 1,024 characters | Fails | Warns |
| The description says when to use the skill | Notes it | Not checked |
| The description leads with the main job | Notes it | Not checked |
| Only the six spec fields | Warns | Notes it |
| Has a license field | Notes it | Not checked |
| compatibility is text of 1 to 500 characters | Fails | Notes it |
| metadata maps text keys to text values | Fails | Notes it |
| allowed-tools is one space-separated string | Warns | Notes it |
| No install records in metadata | Warns | Not checked |
| The body is at most 500 lines | Warns | Not checked |
| The body is under about 5,000 tokens | Warns | Not checked |
| Reference files are linked from SKILL.md | Notes it | Not checked |
| Long reference files start with contents | Notes it | Not checked |
| No dated instructions | Notes it | Not checked |
Validate a SKILL.md shows what VS Code will reject in your file, with the fix.
Watch out for
- The name must match the folder name, and a name with characters other than lowercase letters, digits and hyphens makes the skill silently fail to load.
- VS Code also reads ~/.claude/skills, so skills installed for Claude Code show up here too.
- Two skills with the same name in different folders both appear in the list.
- context: fork is experimental.