Anthropic announced on October 22, 2026 that it is donating Agent Skills, an open standard it published in December 2025, to the Agentic AI Foundation (AAIF) under the Linux Foundation. According to Anthropic, AAIF was co-founded last year with Block and OpenAI and previously received Anthropic's donation of the Model Context Protocol (MCP). A skill is described as a folder containing a SKILL.md file that teaches an agent a specific task or domain, along with any scripts or reference material it needs. Anthropic said it developed skills while working on Claude Code, which handled general knowledge work but often lacked procedural knowledge for business tasks. The company states that more than 70 agent platforms—including ChatGPT, Cursor, GitHub Copilot, and VS Code—have integrated Agent Skills, and that 1 million skills have been published and nearly 280 million installed. Anthropic is donating the Agent Skills name and logo, the GitHub organization, and the agentskills.io domain, and says the standard can still be used without joining AAIF. Engineers from Anthropic, Google, OpenAI, and other companies will maintain the standard as individuals, with David Soria Parra and Mahesh Murag as Lead Maintainers. A proposed roadmap covers versioned releases, a formal proposal process, and security guidance. Writer Simon Willison noted he had predicted this move last December.
- Anthropic published Agent Skills as an open standard in December 2025 and is now donating it to the Agentic AI Foundation under the Linux Foundation
- Anthropic reports more than 70 platforms have integrated it, with 1 million skills published and nearly 280 million installed
- A proposed roadmap includes versioned releases, a formal proposal process, and security guidance for writing and installing skills
What it means for you
Agent Skills is a plain way to hand an AI agent a specific procedure—a folder with a file that spells out how a task gets done, plus any scripts it needs. Anthropic moving it to a neutral foundation means the format is more likely to keep working across different tools (ChatGPT, Copilot, Cursor and others) rather than being tied to one vendor. For most operations teams this is plumbing, not a decision you need to make today, but it signals that writing down a process once could increasingly let different tools follow it.
Try this
If you've been tempted to automate a task, first write the procedure out in plain steps—as if you were teaching a new hire. That document is useful whether or not you ever hand it to an agent, and it surfaces the confusion before any tool gets near it.
Who should care
Technical leads and anyone already building on Claude Code, Copilot, Cursor, or similar agent tools who maintains reusable task instructions across teams.
Skip this if
You're not building agent workflows and your automation is handled by a vendor's product—this is standards-body news with no action for you.
Sources: Anthropic, Simon Willison — read the original