Skills · The Agent Skills standard
Agent Skills has a neutral home — and still no security story
Written October 31, 2026
Anthropic handed the Agent Skills standard to the Agentic AI Foundation on 22 October 2026. Your existing skills keep working, the format is unchanged, and the security guidance is still only proposed — so a skill written by a stranger is no safer than it was on 21 October.
What changed
On 22 October 2026, at AGNTCon + MCPCon North America in San Jose, Anthropic donated the Agent Skills standard to the Agentic AI Foundation (AAIF), a Linux Foundation project it co-founded with Block and OpenAI. The donation covers the Agent Skills name and logo, the GitHub organisation, and the agentskills.io domain. Engineers from Anthropic, Google, OpenAI, and other companies will maintain the standard as individuals, with David Soria Parra and Mahesh Murag as Lead Maintainers. The same day, the Linux Foundation announced four new AAIF projects — Agent Skills from Anthropic, Open Responses from OpenAI, OpenEnv from Hugging Face, and OpenSandbox from Alibaba — bringing the foundation from three launch projects to ten hosted projects in its first year. What changed is who governs the standard and who decides its next version. Anthropic's announcement puts it plainly: the AAIF will provide a neutral home, and the community has a say in where the standard goes next.
The adoption figures in Anthropic's announcement are Anthropic's own, with no counting method stated: more than 70 agent platforms have integrated Agent Skills since the standard was published in December 2025, and 1 million skills have been published with nearly 280 million installed. Those figures describe reach, not review. Nothing in either announcement says any of those skills were checked.
What did not change
The specification did not change. A skill is still a directory holding a SKILL.md file, with YAML frontmatter followed by Markdown instructions. The specification lists six frontmatter fields and requires two of them: name (at most 64 characters) and description (at most 1024 characters, describing what the skill does and when to use it). The optional fields are license, compatibility, metadata, and allowed-tools, the last marked experimental. The specification page carries no version number, and its last update predates the handover, dated 4 August 2026. Existing SKILL.md files stay valid, and the products that load them keep loading them from the same places, because the handover moved governance, not the file format.
None of the six fields records who published a skill, whether anyone reviewed it, or whether it was signed. A skill directory may also hold a scripts/ folder with executable code the agent can run, alongside reference material and assets. The format therefore still lets a skill carry code that runs with the agent's permissions, with nothing in the file itself to say whether that code is safe. That is the gap the handover does not close.
What is only proposed
Anthropic proposed starting with a roadmap covering versioned releases, a formal proposal process, and security guidance for people who write and install skills. Proposed is the operative word: none of the three has shipped. There is no versioned release of the specification to pin a skill to, no published proposal process to watch for changes, and no published security guidance from the foundation to follow. Until one of those appears, the neutral home is a governance fact, not a safety signal. A skill that claims foundation approval, a version number, or a security review is claiming something that does not exist yet.
What to do about it
- Keep writing skills to the specification as it stands. Use the two required fields well: a name that matches the folder, and a description that says what the skill does and when to use it, since that description is what agents load at startup to decide whether a skill matches a task. Do not invent a version field or a signing field — the specification has neither, and extra fields are not a substitute for either.
- Treat every skill from a stranger as unreviewed code. Vet a skill before you install it, reading its instructions and scripts as an attacker would, and write the decision down before the skill runs anything. The handover changes who governs the format; it does not vet the million skills already published under it.
- Test a skill in each agent you use it in. The specification defines the file, not how each product loads it, and support for the experimental
allowed-toolsfield varies between agents. A skill that activates correctly in one agent has not been shown to activate correctly, or safely, in another. - Watch for the roadmap items, and judge them when they ship. A versioned release, a published proposal process, and published security guidance would each change what a builder can rely on. Until they exist, the honest description of the standard is the one in this page: a stable file format with a new, neutral owner and no security story yet.
Limits
- This page evaluates the handover as announced on 22 October 2026. Later foundation decisions — including any versioned release or security guidance — would change the picture, and this page does not predict them.
- The adoption figures are Anthropic's own counts, with no counting method stated. They are reported here as Anthropic's claims, not as an independent count.
Related playbooks
- Addy Osmani's 25 agent skills for coding agents
- Agent Skills joins the Agentic AI Foundation
- Chrome's modern-web-guidance: skills for your agent
- FastMCP 4.2 serves skills from the server
Sources
- https://www.anthropic.com/news/donating-agent-skills-to-the-agentic-ai-foundation
- https://www.linuxfoundation.org/press/agentic-ai-foundation-announces-four-new-projects-agent-skills-open-responses-openenv-and-opensandbox?hs_amp=true
- https://agentskills.io/specification
Back to: Skills index · Also: Vet a skill before you install it · Make sure your Claude Code skill actually loads when it should: test it in each agent before you rely on it · NVIDIA SkillSpector — scan a skill before you install it · Coding playbooks hub