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.
Install
With your agent
Install OMGSkills skill "vercel/next.js:.agents/skills/authoring-skills" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/vercel/next.js /tmp/next.js && ln -s /tmp/next.js/.agents/skills/authoring-skills ~/.claude/skills/authoring-skillsFrom README
Authoring Skills Use this skill when creating or modifying agent skills in .agents/skills/. When to Create a Skill Create a skill when content is: Too detailed for AGENTS.md (code templates, multi-step workflows, diagnostic procedures) Only relevant for specific tasks (not needed every session) Self-contained enough to load independently Keep in AGENTS.md instead when: It's a one-liner rule or guardrail every session needs It's a general-purpose gotcha any agent could hit File Structure Supported Frontmatter Fields Only use fields from this list. Unknown fields are silently ignored. Writing Descriptions The description is the primary matching surface for auto-activation. Include: What the skill covers (topic) When to use it (trigger scenario) Key file names the skill references (e.g. config-shared.ts) Keywords a user or agent might mention (e.g.