Windsurf: Devin Playbooks Are Becoming Skills
WindsurfWindsurf is moving Devin Playbooks to Skills, one account at a time. When an account moves, each playbook becomes a skill with the same instructions, the Playbooks pages turn read-only with a link to the matching skill, and the Playbooks API reads and writes the skill. New accounts created from October 24, 2026 start with Skills and have no Playbooks.
Key Takeaways
- Playbooks are being replaced by Skills, with accounts migrated one at a time.
- Each playbook becomes a skill with identical instructions, so no content has to be rewritten.
- Playbooks pages go read-only and link to the skill each playbook became.
- The Playbooks API reads and writes the skill, which keeps existing integrations working.
@playbookmentions and!playbookmacros keep working, as do automations that reference playbooks.- Accounts created from October 24, 2026 start with Skills only, with no Playbooks.
What is changing
Windsurf announced that Devin Playbooks are becoming Skills. The migration happens account by account rather than all at once, so users will see the change on their own account at different times.
What happens when an account moves
When an account is migrated, every playbook is converted into a skill that carries the same instructions. The Playbooks pages in the web app become read-only and each playbook links to the skill it became, so it is easy to find where the content now lives.
Existing workflows are designed to keep working. The Playbooks API continues to function, but it now reads and writes the underlying skill. Automations, @playbook mentions and !playbook macros keep working too, so teams do not have to rewrite their triggers or chat habits on the day of the move.
New accounts
Accounts created from October 24, 2026 start with Skills and have no Playbooks at all. Anyone onboarding after that date will only ever see the Skills model.
Why it matters
Skills are the reusable-instruction format Devin already uses across its CLI and desktop products. Folding playbooks into them removes a parallel concept, so a single set of reusable instructions can be shared across surfaces. For teams that rely heavily on playbooks, the compatibility layer in the API, mentions and macros means the transition should not break existing automation.