A portable instruction package can still fail when its second host has different tools or permissions. Test that boundary when moving a skill between assistants.
What moved to the foundation
Anthropic’s October 22 announcement transfers Agent Skills to the Agentic AI Foundation. The donation covers stewardship of the standard and its associated project assets.
The foundation’s announcement confirms Agent Skills as one of four incoming projects. OpenResponses, OpenEnv, and OpenSandbox are separate projects with different roles.
This is a governance change for an existing format. Proposed work on future versioning or security should remain distinct from requirements that implementations enforce today.
What a skill carries between hosts
The Agent Skills documentation describes a package of instructions and supporting resources that an agent can discover and use. That gives workflow authors a common way to organize expertise.
The host still supplies the execution environment. A path, shell command, or connected service that exists in one environment may be absent in another. The standard’s stewardship cannot establish permission to use a particular account.
A skill that only explains a procedure has fewer dependencies than one that runs scripts or changes external data. Review those dependencies before importing a package.
Try the same harmless workflow on two hosts
I would begin with a skill that reads a small public dataset and produces a local summary. Keep external writes outside the first portability test.
- Use the same package revision and input files.
- Record the tools, runtime versions, and connected services.
- Check how each host discovers and activates the instructions.
- Inspect file paths and missing dependency behavior.
- Compare the saved result with the original input.
Then examine the permission boundary separately. A request to publish or send a message should receive the authorization required by the destination workflow, even if the imported skill describes that action.
Keep maintenance visible after the transfer
For a production workflow, retain the package source, revision, and local changes. When upstream instructions change, review the diff before replacing a version used by a team.
Foundation governance can give contributors a shared place to develop the standard. Reliable use still depends on the package, host, and account configuration that execute the work.
The Notion skill-export article covers a practical cross-host workflow. Our SageMaker skills article examines package dependencies for model deployment.
Sources
- Anthropic donation announcement
- Foundation confirmation of the incoming projects
- Agent Skills format and documentation
Which dependency would stop your most useful skill from working on a second host?
Checked October 25, 2026. Prepared with AI-assisted research and drafting, with claims checked against the linked sources. MustHave.ai has not performed the proposed product tests.
