Cloudflare lets agents load new skills from workspace files between turns

Cloudflare lets an agent discover added workspace skills between turns.

**Dek:** The October 29 SDK change treats agent skills as folders containing a manifest. Applications can load them from a workspace, object storage or code, with migration work for users of the previous APIs.

Cloudflare announced on October 29 that its Agents SDK can load agent skills from files in an agent’s workspace. An application can place a folder containing a skill manifest under the documented workspace path and make it available on the next turn. The changelog also describes R2 and code as sources. The change makes it possible to introduce or revise a skill without rebuilding the application each time. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/post/2026-10-29-agent-skills-from-files/)

Instructions become part of the runtime’s writable state

A skill can package instructions and resources an agent uses for a recurring task. Putting it in the workspace lets a team update the guidance close to the data and tools the agent already uses. Cloudflare says Think refreshes the list of sources before each turn and can communicate a changed catalogue without rebuilding the cached system prompt. Its notes also say agents can write skills and run workspace skill scripts through the workspace execution tool. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/post/2026-10-29-agent-skills-from-files/)

That arrangement gives operators a new permission to review. The ability to save a text file can become the ability to leave instructions for a later session. A team should decide which users or agents can write into skill locations and whether a generated skill is allowed to include scripts. The changelog says a manifest that breaks a specification rule can still load with a warning. Format validation and the application’s decision to trust a skill are therefore separate controls. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/post/2026-10-29-agent-skills-from-files/)

Migration affects more than the file location

Cloudflare lists removed imports and APIs for code using the earlier skills path. A project upgrading the SDK should check direct imports, any compile-time registration and the logic that determines which skills an agent can see. It can then test a known skill before and after changing its source, and confirm which revision is active on the next turn. An agent with tools or access to customer data also needs a test that an unapproved workspace file cannot give it authority the host application has withheld. [Cloudflare AI changelog](https://developers.cloudflare.com/changelog/post/2026-10-29-agent-skills-from-files/)

The strongest use case is a team that already has a clear owner for reusable instructions and wants to revise them independently of application releases. For other deployments, keeping a reviewed skill in code or in a controlled storage location may make version ownership easier to see.