Plugin Architecture
OrchestKit ships as one unified plugin — everything loads on-demand with zero overhead.
One Plugin, Everything Included
OrchestKit ships as a single plugin: ork.
claude install orchestkit/orkNo choices, no configuration required. All 111 skills, 37 agents, and 212 hooks install together.
What Loads When
Not everything runs at once. OrchestKit uses on-demand loading to stay fast:
| Component | When It Loads | Overhead |
|---|---|---|
| Hooks | Session start — only event-matched hooks fire | ~800 tokens/turn max |
| Agents | When spawned by name or keyword match | Zero until invoked |
| Skills | Injected into agent context when relevant | Zero until matched |
| Commands | Available immediately via /ork:skillname | Listing only (~80 tokens/skill) |
Why One Plugin
Early versions split functionality into multiple plugins (orkl, ork-creative). This caused:
- Version conflicts between plugins
- Duplicate hook registrations
- Confusing install instructions
Since v7.0, everything is consolidated into ork. Skills you don't use have zero token cost.
Next Steps
- Installation — Full install guide with verification
- First 10 Minutes — Guided first session
MCP Servers
External tool integrations that give agents web search, component registries, design extraction, and more.
Cookbook
Step-by-step workflow walkthroughs for common development tasks with OrchestKit.
Edit on GitHub
Last updated on