SIP — Skills Interoperability Protocol
The composability contract that makes multi-skill execution possible.
Core Principle
A skill owns its domain. It does not own the conversation.
When multiple skills are active, each one handles its domain and stays out of the others'. No skill overrides another. No skill assumes it's the only one running.
Why SIP Exists
Without a protocol, combining AI capabilities means conflict. One skill wants verbose output, another wants terse. One wants formal tone, another wants casual. SIP resolves this by giving each skill a clear domain and explicit composition rules.
Key Concepts
| Concept | Description |
|---|---|
| Domains | Non-overlapping areas of ownership (voice, density, craft, process, content) |
| Composition Modes | How skills combine: pipeline, layered, handoff, advisory |
| Precedence Rules | Conflict resolution hierarchy |
| Composition Contract | Rules every skill must follow |
How It Works
- Each skill declares its domain in frontmatter
- Skills declare what they yield to (
yields_to) - When composing, each skill handles its domain
- Conflicts are resolved by precedence rules
- Structure from upstream skills is preserved
Quick Example
/blog technical + /caveman lite- Blogger (domain: voice) handles tone, personality, content structure
- Caveman (domain: density) handles token count, verbosity
- No conflict — each owns its domain
Learn More
- Domains — The five domain types
- Composition Modes — How skills combine
- Precedence Rules — Conflict resolution
- Contract — Rules every skill must follow