npx skills add ...
npx skills add vercel/next.js --skill authoring-skills
npx skills add vercel/next.js --skill authoring-skills
How to create and maintain agent skills in .agents/skills/. Use when creating a new SKILL.md, writing skill descriptions, choosing frontmatter fields, or deciding what content belongs in a skill vs AGENTS.md. Covers the supported spec fields, description writing, naming conventions, and the relationship between always-loaded AGENTS.md and on-demand skills.
Use this skill when creating or modifying agent skills in .agents/skills/.
Create a skill when content is:
Keep in AGENTS.md instead when:
Only use fields from this list. Unknown fields are silently ignored.
The description is the primary matching surface for auto-activation. Include:
config-shared.ts)Skills should tell the agent what to do, not just what to know:
| AGENTS.md (always loaded) | Skills (on demand) |
|---|---|
| One-liner guardrails | Step-by-step workflows |
| "Keep require() behind if/else for DCE" | Full DCE pattern with code examples, verification commands, edge cases |
Points to skills via $name | Expands on AGENTS.md rules |
When adding a skill, also add a one-liner summary to the relevant AGENTS.md section with a $skill-name reference.
flags, dce-edge, react-vendoring.agents/skills/)For complex skills, use a hub + detail pattern:
# Too vague - won't auto-trigger reliably
description: Helps with flags.
# Good - specific files and concepts for matching
description: >
How to add or modify Next.js experimental feature flags end-to-end.
Use when editing config-shared.ts, config-schema.ts, define-env-plugin.ts.pr-status-triage/
├── SKILL.md # Overview, quick commands, links to details
├── workflow.md # Prioritization and patterns
└── local-repro.md # CI env matching