Agent Skills Hit 40 Clients and 200 New Skills a Week. Should Your Product Ship One?

Agent Skills went from an Anthropic feature to a cross-platform standard in under a year. Since the spec opened at agentskills.io on December 18, 2025, roughly 40 products have adopted it, including GitHub Copilot, Cursor, OpenAI Codex, Gemini CLI, and VS Code. The ecosystem adds about 200 new skills a week, and the SkillsMP directory now indexes around 1.9 million public skills.

For website and product owners, the question is concrete: should your site publish skills that teach agents to use your product? Here is how the standard works and who benefits.

What is an Agent Skill?

A skill is a folder with a SKILL.md file: packaged instructions, scripts, and resources an agent loads when it needs a specific capability. Think of it as documentation written for an agent to execute rather than a person to read.

Anthropic launched skills in October 2025 for Claude, then published the format as an open standard that any agent product can implement. That opening is what changed the math: a skill you write once now works in Claude, Copilot, Cursor, Codex, and the rest of the compatible clients.

What do skills have to do with your website?

Discovery. The emerging convention is a skills index at /.well-known/skills/index.json, listing the skills your site or product offers. An agent working with your product checks the index, loads the relevant skill, and suddenly knows your API conventions, your rate limits, your gotchas, and the right order of operations.

That matters because agents fail at products the same way new hires do: not from missing intelligence, but from missing context. A skill is that context, versioned and testable. Anthropic's own partner directory already carries skills from Atlassian, Canva, Cloudflare, Figma, Notion, Ramp, Sentry, Stripe, and Zapier, which is a decent picture of who benefits first: products that developers drive through agents.

What does a good skill look like?

The skills that get used share three traits.

They are narrow. "Set up a webhook subscription" beats "use our API." An agent picks skills by description, and precise descriptions win.

They are executable. Good skills include the exact commands, working code snippets, and checks for success, not marketing prose. If a step can fail, the skill says how to tell and what to do next.

They are maintained. A skill that references a renamed endpoint is worse than no skill, because the agent trusts it. Ship skills from the same pipeline as your docs, and version them.

Writing one is not a big project. A first skill is usually a distillation of your best how-to guide, tested by pointing an agent at it and watching where it stumbles.

Should your site publish skills?

Worth adding if agents already touch your product. Developer tools, APIs, SaaS with integrations: this is the same audience that made the partner directory. The effort is hours, the standard is open, and the reach spans 40 clients.

Worth adding, with a narrower scope, if your site has complex workflows agents get wrong: a booking flow with strict validation, a configurator with dependencies. A skill can encode the path that works.

Skip it if you run a content site. Skills teach agents to do things, and reading articles is something they already do. Your effort goes further in the content layer: schema.org and markdown negotiation.

Skills sit in the interaction layer of the agent readiness stack, next to WebMCP and NLWeb. Of the three, skills are the cheapest to try and the only one with 40 shipping consumers today.

How do you publish one?

Three steps. Write the SKILL.md following the agentskills.io format, with a name, a precise description, and step-by-step instructions. Test it by giving it to an agent and running the task cold. Then list it in your index at /.well-known/skills/index.json so agents can discover it from your domain.

GenReady's analyzer checks for that index on every scan. Like the rest of our agent readiness checks, it is bonus-only: a valid skills index adds a point, a missing one never subtracts.

Want to see which discovery files your site already serves? Run a free GenReady scan — it checks the skills index and seven other signals in under 60 seconds.