Agent Skills is no longer an extension tied to a single vendor. The group that published the standard for giving AI agents specialized knowledge and workflows has announced the move to the Agentic AI Foundation. Published in December 2025 and already integrated by more than 70 platforms — including ChatGPT, Cursor, GitHub Copilot and VS Code — the standard changes governance: from a controlled specification to a neutral resource, at least in intention.

The move has value beyond philanthropy. When a technical specification reaches critical mass in adoption, keeping unilateral control becomes counterproductive. Companies that integrate a standard worry that the owner might change the rules, favor its own services, or make competing implementations obsolete. Donating the standard to an independent foundation reduces that risk and pushes other platforms to adopt it without feeling dependent on a rival. It is the classic shift from competitive advantage to shared infrastructure.

The local execution angle

For teams managing self-hosted stacks or isolated environments, Agent Skills touches a deeper nerve than it seems. A skill is not just a more elaborate prompt: it can include operating procedures, access to tools, software dependencies and input/output conventions. If these capabilities remain tied to cloud endpoints or commercial runtimes, an agent running on corporate infrastructure starts with a handicap: it may have the model, but not the same operational capacity. An open standard governed by a foundation makes it plausible that the same skill package can be interpreted by local engines without going through the services of the original publisher.

That does not mean the standard alone is enough. The integrations claimed by 70 platforms matter only if interoperability is verified, not just announced. The concrete risk is silent fragmentation: everyone declares compatibility, but each runtime implements a different subset or extends the specification with proprietary behavior. The foundation therefore inherits a technical governance problem: defining execution profiles, conformance tests and extension methods. For organizations planning multi-year on-prem deployments, that stabilization matters more than the speed at which new skills are added.

Who loses? Above all, those who built their advantage on exclusive distribution of workflows and integrations. In the enterprise, the value rarely lies in the LLM alone, but in the ability to connect it to internal systems, proprietary data and operating procedures. If these capabilities become portable, the exit barrier drops and vendors must compete on execution, security and cost, not on closing the ecosystem. For organizations evaluating on-premise alternatives, there are concrete trade-offs between control and integration complexity: AI-RADAR collects analytical frameworks at /llm-onpremise to navigate these constraints.

One open question remains: whether the foundation will be able to enforce a minimum execution profile or whether the market will keep tolerating incompatible variants. The donation is a structural signal, but the proof will be in the actual conformance of runtimes, especially local ones.