Configures OrchestKit plugin settings, MCP servers, hook permissions, and keybindings. Use when customizing plugin behavior or managing settings.
Configures OrchestKit plugin settings, MCP servers, hook permissions, and keybindings for customizing behavior.
/plugin marketplace add yonatangross/orchestkit/plugin install orkl@orchestkitThis skill is limited to using the following tools:
references/mcp-config.mdreferences/presets.mdInteractive setup for customizing your OrchestKit installation.
/ork:configure
Use AskUserQuestion:
| Preset | Skills | Agents | Hooks | Description |
|---|---|---|---|---|
| Complete | 78 | 20 | 92 | Everything |
| Standard | 78 | 0 | 92 | Skills, no agents |
| Lite | 10 | 0 | 92 | Essential only |
| Hooks-only | 0 | 0 | 92 | Just safety |
| Monorepo | 78 | 20 | 92 | Complete + monorepo detection |
Categories available:
Product Agents (6):
Technical Agents (14):
Safety Hooks (Always On):
Toggleable Hooks:
CC 2.1.49 Managed Settings: OrchestKit ships plugin
settings.jsonwith default hook permissions. These are managed defaults — users can override them in project or user settings. Enterprise admins can lock managed settings via managed profiles.
All 5 MCPs ship enabled by default. Tavily requires an API key; agentation requires a local package install.
| MCP | Purpose | Default | Requires |
|---|---|---|---|
| context7 | Library documentation | enabled | Nothing |
| memory | Cross-session persistence | enabled | Nothing |
| sequential-thinking | Structured reasoning for subagents | enabled | Nothing |
| tavily | Web search + extraction | enabled | API key (free tier: app.tavily.com) |
| agentation | UI annotation tool | enabled | npm install agentation-mcp |
Why all enabled? OrchestKit ships 30+ Sonnet/Haiku subagents. While Opus 4.6 has native extended thinking, Sonnet and Haiku do not — they benefit from sequential-thinking. Tavily and agentation are used by specific agents (see
mcpServersin agent frontmatter). CC's MCPSearch auto-defers schemas when overhead exceeds 10% of context, so token cost is managed automatically.
Background agents: MCP tools are NOT available in background subagents (hard CC platform limitation). Agents that need MCP tools must run in the foreground.
Already have these MCPs installed globally? If Tavily or memory are already in your ~/.claude/mcp.json, skip enabling them here to avoid duplicate entries. OrchestKit agents will use whichever instance Claude Code resolves first.
Configure CC 2.1.7-specific features:
Enable turn duration in statusline? [y/N]: y
Adds to settings.json:
{
"statusline": {
"showTurnDuration": true
}
}
MCP deferral threshold (default 10%): 10
Adds to config.json:
{
"cc217": {
"mcp_defer_threshold": 0.10,
"use_effective_window": true
}
}
Use effective context window for calculations? [Y/n]: y
When enabled:
context_window.effective_percentageConfigure CC 2.1.20-specific features:
Enable task deletion (status: "deleted")? [Y/n]: y
Enables orphan detection and automatic cleanup of blocked tasks.
Enable PR status enrichment at session start? [Y/n]: y
Detects open PRs on current branch and sets ORCHESTKIT_PR_URL / ORCHESTKIT_PR_STATE env vars.
Enable permission profile suggestions for agents? [Y/n]: y
Shows recommended permission profiles when spawning agents.
Enable monorepo detection? [Y/n]: y
Detects monorepo indicators and suggests --add-dir usage.
CC 2.1.47: When
added_dirsare already active, the monorepo detector automatically skips the--add-dirsuggestion. Theadded_dirsfield is now available in hook inputs for multi-directory awareness.
Share OrchestKit across a team using a shared directory:
# Create shared plugin directory
mkdir -p /shared/team/plugins/orchestkit
# Copy plugin files
cp -r plugins/ork/* /shared/team/plugins/orchestkit/
# Team members use --add-dir to pick up the shared plugin
claude --add-dir /shared/team/plugins
CC 2.1.45+ supports plugin_hot_reload — team members get updates without restarting their sessions.
enabledPluginsvsadded_dirs:enabledPluginsis a CC-internal concept and is NOT exposed to hooks. The hook-accessible field for multi-directory awareness isadded_dirs(available inHookInputsince CC 2.1.47). Hooks can readinput.added_dirsto detect which additional directories are active — useful for adapting behavior in multi-repo workspaces.
When added_dirs are active, OrchestKit's monorepo detector surfaces package names from each directory as session context. This helps agents understand which packages are in scope:
Multi-directory context active (3 dirs)
Packages: @myapp/api, @myapp/web, @myapp/shared
Each directory may have its own CLAUDE.md with targeted instructions.
Use claude --add-dir ./packages/api --add-dir ./packages/web to include specific packages.
Configure CC 2.1.23-specific features:
Replace default Claude Code spinner verbs ("Thinking", "Working", etc.) with custom branding:
Customize spinner verbs? [Y/n]: y
Adds to .claude/settings.json:
{
"spinnerVerbs": {
"mode": "replace",
"verbs": [
"Orchestrating",
"Coordinating",
"Synthesizing",
"Analyzing",
"Reasoning",
"Crafting",
"Architecting",
"Validating",
"Dispatching",
"Assembling",
"Engineering",
"Composing"
]
}
}
Options:
mode: "replace" - Use only your custom verbsmode: "append" - Add your verbs to the defaultsOrchestKit-themed verbs focus on orchestration, architecture, and engineering actions.
Use AskUserQuestion to offer optional third-party integrations:
Enable Agentation UI annotation tool? [y/N]: y
Agentation lets you annotate your app's UI in the browser and have Claude pick up the feedback automatically.
When enabled, perform these steps (idempotent — skip any step already done):
Install dependencies (check package.json first):
npm install -D agentation agentation-mcp
Add MCP server to .mcp.json (skip if agentation key already exists):
{
"mcpServers": {
"agentation": {
"command": "npx",
"args": ["-y", "agentation-mcp", "server"],
"disabled": false
}
}
}
Enable MCP server in Claude Code settings — add "agentation" to the enabledMcpjsonServers array in .claude/settings.local.json (create file if missing, skip if already listed):
{
"enabledMcpjsonServers": ["agentation"]
}
Scaffold wrapper component — create a dev-only client component (skip if file already exists). Use the project's component directory (e.g. src/components/, components/, or app/components/):
// agentation-wrapper.tsx
"use client";
import { Agentation } from "agentation";
export function AgentationWrapper() {
if (process.env.NODE_ENV !== "development") return null;
return <Agentation endpoint="http://localhost:4747" webhookUrl="http://localhost:4747" />;
}
Then instruct the user to add <AgentationWrapper /> to their root layout.
CSP update (only if the project has a Content-Security-Policy): add http://localhost:4747 to the connect-src directive for development mode only.
Save to: ~/.claude/plugins/orchestkit/config.json
{
"version": "1.0.0",
"preset": "complete",
"skills": { "ai_ml": true, "backend": true, ... },
"agents": { "product": true, "technical": true },
"hooks": { "safety": true, "productivity": true, ... },
"mcps": { "context7": false, ... }
}
ork:doctor: Diagnose configuration issuesSearch, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.