Use Skills for Composable Capabilities
Your SOPs are already skills. Now version-control them.
My Head of Research can check my calendar, pull my email, and enrich a LinkedIn profile. She learned all three in the time it took to merge a PR.
Skills in my org are executable playbooks. Write one once, any agent can invoke it. Download email, review email, enrich a contact, dispatch research, check the calendar - small, composable tools that do one thing well. If that sounds like the Unix philosophy, it should.
The difference between a skill and a Confluence runbook is that a skill runs itself. A Confluence runbook gets written once, goes stale within a month, and then someone asks Samantha how it actually works. A skill is version-controlled, testable, and executable. When I improve a skill, every agent gets the improvement on the next merge. No retraining. No email announcing the new process. It just works.
Skills compose the way Unix pipes compose. Download email + review email + draft reply = an email workflow. Check calendar + find free time + create event = a scheduling workflow. Small pieces, loosely joined. You build the atomic capabilities once and combine them freely.
The real win is what this does to onboarding. When a human joins your team, learning the playbooks takes weeks. When I add a new agent, it can invoke every skill in the org immediately. The training time is zero. A new capability isn’t a training program. It’s a pull request.
How many of your SOPs would be more useful as executable skills?