Skills Left the Vendor: When the Folder Became Infrastructure

On 22 October 2026 Anthropic donated Agent Skills to the Agentic AI Foundation under the Linux Foundation, the same home they already used for MCP. More than seventy agent platforms have loaded the folder format since the standard went public; they name ChatGPT, Cursor, GitHub Copilot, VS Code, and the obvious cousins. A million skills published. Hundreds of millions of installs. A format born so Claude Code would stop lacking procedural knowledge is now infrastructure nobody owns.^[1]

Read that next to June. A frontier SKU vanished because a letter said so. Four months later theprocedure cannot vanish the same way. That is the summer, in one juxtaposition. Kill switches apply to horses. Folders, once they are a standard, are how you keep the harness.

This is the opposite of Fable

The Fable directive was the state reaching into a live model. The AAIF donation is a lab letting go of the procedural layer so it cannot be recalled with a letter. MCP already went this way: connectors as a shared language. Skills are the procedural twin. Engineers from Anthropic, Google, OpenAI and others maintaining a spec as individuals is the tell. The interesting competition moves to models, harness UX, and your folders, not to who invented YAML frontmatter.

Boards will under-hear this. It does not look like a product launch. Operators should over-hear it. If your skills only live in one vendor's workspace, you slept through the event. The standard is the exit door.

Pioneer move: one tree, many agents

Canonical directory, .agents/skills or whatever you will actually review in Git. Claude, Cursor, Codex paths as aliases, not three libraries. Progressive disclosure so seventy runtimes do not mean seventy copies of a 2,000-line bible. The OS essay is the how. This essay is the why-now: the political economy caught up with the folder.

Do not wait for procurement to pick a winner. Dual-home the runtime the way you dual-home the model after a kill switch. The skill should not care which horse showed up on Monday. That was the point of the spec when it was still "a Claude thing." It is now the point of a foundation.

A CoE cannot own this, and will try

Predictable failure: a center of excellence announces the official skill pack, mapped to the official Copilot, with a review board for descriptions. Anthropic's own team did the opposite internally, sandbox, pull, promote what people already used. When a million skills exist in the wild, your board is not a filter. It is a queue. Role bundles, evals, security vetting of scripts and network: those are platform. Which skill gets written next: that is the operator who just failed a loop.

Hunt authors. The donation does not replace the lab or FDE. It tells you what those functions should leave behind: folders that any of the seventy can load, including the runtime behind the fence.

Hardware reads this as permission

Physical AI needed a portable procedure layer more than the office did. Schematics, DfM, twin-diffs, PLC tests, those cannot live as chat folklore and cannot depend on one lab's SKU. A vendor-neutral skill is how a cell in an air gap and a brand team in a holding company share an operating system without sharing a cloud. The last mile was always atoms. The standard is how the last mile stays yours.

This week

Pick the canonical tree. Move anything that only exists in a vendor UI into it. Run one loop on two runtimes without editing the skill. If you cannot, you do not have a skill. You have a setting. Then go design the teams: FDE at the edge, lab as foundry, platform as the thing that makes those two boring and safe. The standard will not do that for you. It just removed the excuse that you were waiting for the ecosystem to settle.

Skills left the vendor. A letter can still kill a model. It cannot as easily kill a folder the industry agreed to load. Own the tree. Dual-home the runtime. Hunt the authors. Build FDE and the lab on that floor. That is the frontier, and it is already under your feet.

Related: Skills Became Infrastructure, The FDE Frontier, and Establish the Lab.