.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

home/glossary/skill.md
home/glossary/skill.md

What is a SKILL.md file?

SKILL.md is the plain-markdown file that defines an agent skill: a short description of when the skill applies plus the instructions the agent should follow, in the format Claude Code and other skills-compatible agents read.

Every agent skill is, at its core, a SKILL.md file. The top of the file describes what the skill is for and when to trigger it; the body holds the actual instructions — the steps, rules, examples and constraints the agent should follow when the task comes up. Some skills ship supporting files alongside it (scripts, templates, reference docs), but SKILL.md is the entry point the agent loads.

The format matters because it's what makes skills portable. Any skills-aware client — Claude Code, Cursor and others — knows how to read a SKILL.md, so the same file improves every compatible agent without rewriting it. That's why the ecosystem converged on one simple markdown convention rather than a per-tool config.

Writing one is straightforward: describe the trigger clearly so the agent knows when to reach for it, then give focused, opinionated instructions. Narrow skills that do one job well beat sprawling ones. Every skill in this directory is built on a SKILL.md you can inspect from its source repo.

Popular skills

All Skills →
Type
  1. vercel-labs avatarfind-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express…SkillsJul 20262.7M27k
  2. mattpocock avatargrill-meA relentless interview to sharpen a plan or design.SkillsJul 2026690k189k
  3. vercel-labs avataragent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…SkillsJul 2026591k39k
  4. vercel-labs avatarreact-best-practicesReact and Next.js performance optimization guidelines from Vercel Engineering.SkillsJul 2026587k29k
  5. mattpocock avatargrill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026585k189k
  6. mattpocock avatarimprove-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026566k189k

FAQ

Where does the SKILL.md file go?

It lives in the skill's folder in your project or global skills directory; the install command places it for you.

Can I write my own SKILL.md?

Yes. Create a SKILL.md with a clear trigger description and your instructions, and any skills-compatible agent can load it.

More terms

MCP serveragent skillAI agentAI workflowprompt templateModel Context ProtocolClaude skills