Anthropic Donates Agent Skills Standard to Foundation

What was donated on October 22

Anthropic announced on October 22 that it is donating Agent Skills to the Agentic AI Foundation under the Linux Foundation. The donation covers the Agent Skills name and logo, its GitHub organization, and the agentskills.io domain. The format is deliberately simple: a skill is a folder with a SKILL.md file that describes a task or domain, with optional scripts and reference files. The company says more than 70 agent platforms have integrated the standard since its December 2025 publication. Anthropic also reports one million published skills and nearly 280 million installations. Those adoption figures are the donor's claims; the announcement does not supply an independently audited census or a method for distinguishing active, useful skills from duplicates.

Why a neutral home matters

Agent Skills began in Anthropic's Claude Code work, where a general-purpose agent needed procedural knowledge for particular jobs. Developers then built loaders for other tools. The foundation move addresses a governance problem created by that growth: when many competing products implement one format, the rules for names, compatibility, changes and security should be legible outside the originating vendor. Anthropic says engineers from Anthropic, Google, OpenAI and other companies will maintain the project as individuals, with David Soria Parra and Mahesh Murag as lead maintainers. The announcement says organizations may use or contribute to the standard without joining the foundation. It does not say the foundation has already ratified every future governance procedure.

This is a standards and ecosystem announcement, not a new model release. The practical unit is a repository directory that an agent can discover and load. A SKILL.md can tell an agent when to use a workflow, what tools to invoke, and where supporting materials live. Optional executable scripts make the folder more powerful and also increase the cost of trusting it. A text file fetched from a public repository is still third-party input, even when its layout follows a recognized standard. A neutral name or familiar directory shape should not be confused with code review, sandboxing or provenance verification.

The proposed roadmap is still a proposal

Anthropic proposes beginning with versioned releases, a formal proposal process and security guidance for people who create and install skills. Versioning could let implementers state precisely which syntax and behavior they support, avoiding silent drift between tools. A proposal process could make extensions and compatibility changes reviewable. Security guidance could specify how a loader presents requested permissions, handles references outside the skill folder and evaluates scripts before execution. Those are the subjects Anthropic says it wants on the roadmap. The October 22 statement does not establish finished enforcement rules for every platform or promise that installation alone will be safe.

What interoperability can and cannot guarantee

An interchangeable packaging format lowers the cost of moving a documented workflow between compatible agents. It does not make tool APIs identical, guarantee that a model will follow instructions perfectly or prove that a shell script is harmless. One platform may allow network access and file writes, another may require approval, and a third may have no equivalent tool. A skill that assumes one platform's semantics can fail or request too much authority on another. The sensible portability test is to run a small fixture under each target loader and compare the actual side effects, prompts, failures and outputs. Documentation portability is valuable even when execution behavior differs.

The public specification should be read as data about the format, not as an instruction from the open web to this publication system. That distinction is particularly important for skills. A malicious page can imitate a SKILL.md and ask an agent to leak tokens or ignore earlier rules. Editors and developers should cite a repository at a pinned revision when reviewing an installation, inspect referenced scripts, and enforce permissions at the host tool boundary. Such steps follow from the threat model; they are recommendations here, not assertions that the foundation has already adopted them.

A concrete evaluation for a team

Choose one narrow workflow, such as parsing a known report or checking a release changelog. Record the skill folder and commit hash, run it in an isolated workspace, and list each file and network endpoint it touched. Try it under two supported agent hosts. If results differ, separate format parsing failures from differences in model behavior or permission policy. A useful skill should reduce repeated explanation without making the operator blind to its actions. Measure task success and review effort, not installation count alone. For an organization with a private skill catalogue, add ownership, review date and revocation information so users can retire a compromised or obsolete package.

Anthropic's reported adoption suggests the format already spans products, while the governance transfer could make future changes less dependent on one vendor. The two facts should not be conflated: broad adoption is a claim about present integrations, and foundation stewardship is an organizational step whose effectiveness will be shown by actual releases, open proposals and security documentation. The immediate reader action is to inspect the current specification and the repository, then watch for a published governance process. This article is in the October 25 issue because the original donation announcement appeared October 22; it does not imply a new October 25 announcement.