Agent Skills Now Belong to a Foundation: What It Means

On 22 October 2026, Anthropic announced that it is giving Agent Skills, the open format for teaching AI agents how to do specific tasks, to the Agentic AI Foundation. If your team uses AI coding agents, the short answer is this: nothing breaks and nothing is required of you, but the format your team's know-how is written in now has a neutral home instead of a single company.

This article explains what a skill is, what exactly changed on 22 October, what it means for a team building software, and where Atlas stands on it today.

What is an Agent Skill?

A skill is a package of written instructions that teaches an AI agent how to do one kind of task the way your organisation does it. Think of the page in an employee handbook that says "this is how we prepare a release" or "this is how we write a customer report". The agent uses it when the task comes up and follows it.

Anthropic says skills began with Claude Code, its AI coding tool. In its words, Claude Code "handled general knowledge work well, but often lacked the procedural knowledge that real business tasks need". Skills are meant to supply that missing know-how. Anthropic launched skills in October 2025 and published the format as an open standard in December 2025. "Open standard" here means the format is published for anyone to use, not locked to one product.

What changed on 22 October 2026?

According to Anthropic's announcement, it is donating four things to the Agentic AI Foundation (AAIF):

• the standard itself;
• the Agent Skills name and logo;
• the GitHub organization where it lives (GitHub is the website where software projects are shared and worked on);
• the agentskills.io website domain.

The AAIF is hosted by the Linux Foundation, a long-standing non-profit home for shared software projects. Anthropic co-founded the AAIF last year with Block and OpenAI. Anthropic had already given it the Model Context Protocol (MCP), the standard for connecting agents to outside tools and data.

In plain terms: until now, one company held the rulebook for skills. Now a neutral organisation does.

Who will run it?

The announcement says the standard will be maintained by engineers from Anthropic, Google, OpenAI and other companies, who take part as individuals. The two Lead Maintainers are David Soria Parra and Mahesh Murag. Joining the AAIF is not required to use the standard or to contribute to it.

How widely is it used?

Anthropic reports these figures in its announcement:

• more than 70 agent platforms have integrated Agent Skills since the standard was published, including ChatGPT, Cursor, GitHub Copilot and VS Code;
• 1 million skills have been published;
• nearly 280 million skills have been installed.

These are Anthropic's own numbers, so read them as the maker's claim. Anthropic also notes that within weeks of the October 2025 launch, developers had published thousands of skills and built loaders (small add-ons that let other tools read skills) for Codex, Cursor and OpenCode.

Why does a neutral owner matter?

Anthropic's stated aim is "to keep Agent Skills open, community-driven, and vendor-neutral". For a business, that translates into a few practical points.

Less lock-in. Suppose your team writes a skill for how your company reviews contracts, or how your product's release notes should read. If one vendor controls the format, that work is a bet on that vendor. If many tools read the same format and a neutral body steers it, the bet is safer. You could change tools and keep the skill.

Clearer rules for change. Anthropic has proposed a roadmap with three items: versioned releases, a formal proposal process for changes, and security guidance for people who write and install skills. The announcement gives no dates for any of them, so treat them as intentions, not commitments. Anthropic says the project will follow the same community-input and open decision-making approach used for MCP.

A clearer place to raise problems. The specification is at agentskills.io, discussion happens on GitHub (github.com/agentskills/agentskills), and feedback on proposed changes to the specification goes through the project's Discord, a chat service.

What does this mean for a team building software?

For most teams, very little changes this week. Anthropic asks nothing of users beyond optional participation, and your existing skills keep working. The value is in the decisions you make from here.

Treat skills as company assets

A skill captures how your team likes work done. That is worth writing down properly, keeping a history of changes to, and reviewing, just as you would with code. Good first candidates are the things you keep explaining to new people:

• how a bug report should be written and sorted by urgency;
• your definition of "done" for a feature;
• the checks every release must pass;
• naming and style rules for documents or code.

Take the security question seriously

A skill is an instruction that an agent will follow. That means installing someone else's skill is a trust decision, a bit like running a stranger's checklist with your accounts open. Anthropic has put security guidance for writers and installers on its proposed roadmap, which suggests the topic is recognised. Until that guidance exists, the sensible habit is simple: read a skill before your team installs it, and prefer skills written in-house or by sources you trust. This is our advice, not something the announcement states.

Do not expect it to fix quality by itself

A skill can make an agent more consistent about the steps you describe. It does not prove that the work is correct. You still need tests, review and a person who checks the result.

How does Atlas handle skills today?

Honestly: Atlas does not yet let you add your own skills for its engineers to load. Atlas is a software team made of AI engineers, built on Claude Code. What it does today is teach its engineers through other routes. Domain plugins teach the team a product's rules, with Salesforce as one example, and those rules are checked against every change before work can be called done. Lessons from finished work are also passed on to future engineers. One lesson is held back as a control, and any lesson that tracks worse results or higher cost is retired automatically.

Skills your team writes yourselves are not part of that yet. Support for them is coming to Atlas, built in, so it needs no setup on your side. Until then, put your standards into the brief you give PA, your project assistant, and let the checks on finished work show whether they are followed.

What should you do this week?

1. Pick one repeated task and write down the steps in plain language. That draft is your first skill.
2. Ask your engineers which skills they already use, and where each came from.
3. Agree a simple rule for installing outside skills: someone reads it first.
4. Watch the Agent Skills discussion on GitHub for the versioning and security work Anthropic has proposed.

Conclusion

Moving Agent Skills to the Agentic AI Foundation is a governance change, not a feature change. It does not alter how skills work today, but it gives teams more reason to invest in them: Anthropic reports the format is integrated on more than 70 platforms, and it now has a neutral host. The sensible response is modest. Write down your team's best practices, treat outside skills with care, and keep your tests and reviews in place.