メニュー
Interactive wizard for OrchestKit settings: MCP servers, hook permissions, keybindings, and install presets. Use when customizing plugin behavior or managing settings.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/yonatangross/orchestkit --skill configureコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Chain patterns for multi-phase pipelines: MCP detection, handoff files, checkpoint-resume, worktree agents, CronCreate monitoring. Use when building or debugging a pipeline skill.
OrchestKit doctor for health diagnostics across manifest integrity, hook configuration, skill validation, agent frontmatter, MCP server connectivity, CC version compatibility, and permission rules. Reports issues with severity levels and auto-remediation suggestions. Validates component counts, detects orphaned entries, and checks CC version matrix compliance. Use when diagnosing plugin health, troubleshooting configuration issues, or running pre-release checks.
Inspects the OrchestKit telemetry pipeline for the current project — lists all known telemetry files with write counts, sizes, schema status, growth trend, and orphan detection. Use when verifying the observability pipeline is healthy, debugging a missing writer, or auditing which files have schema locks vs. which are drift-vulnerable. Read-only — never modifies telemetry files.
SKILL.md を表示中
| name | configure |
| license | MIT |
| compatibility | Claude Code 2.1.220+. |
| description | Interactive wizard for OrchestKit settings: MCP servers, hook permissions, keybindings, and install presets. Use when customizing plugin behavior or managing settings. |
| argument-hint | [preset-name] |
| context | inherit |
| version | 1.0.1 |
| author | OrchestKit |
| tags | ["configuration","setup","wizard","customization"] |
| user-invocable | false |
| allowed-tools | ["Bash","Read","Grep","Glob","AskUserQuestion"] |
| complexity | low |
| persuasion-type | collaborative |
| effort | low |
| model | haiku |
| metadata | {"category":"workflow-automation"} |
| paths | [".claude/**","**/.claude/**"] |
Interactive setup for customizing your OrchestKit installation.
/ork:configure
/ork:configure mcp memory
PRESET = "$ARGUMENTS[0]" # Optional preset name or subcommand, e.g., "mcp"
TARGET = "$ARGUMENTS[1]" # Optional target, e.g., "memory"
# If no arguments, run interactive wizard.
# $ARGUMENTS is the full string (CC 2.1.59 indexed access)
Use AskUserQuestion:
| Preset | Skills | Agents | Hooks | Description |
|---|---|---|---|---|
| Complete | 91 | 31 | 96 | Everything |
| Standard | 91 | 0 | 96 | Skills, no agents |
| Lite | 10 | 0 | 96 | Essential only |
| Hooks-only | 0 | 0 | 96 | Just safety |
| Monorepo | 91 | 31 | 96 | Complete + monorepo detection |
Categories available:
Product Agents (2):
Technical Agents (17):
Operations Agents (6):
Research Agents (4):
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.
CC 2.1.111 — prune overbroad Bash permissions: Since 2.1.111, read-only Bash commands with glob patterns (
ls:*,head:*,grep:*,wc:*,find:*, etc.) no longer trigger permission prompts by default. If your.claude/settings.local.jsonhas explicitBash(ls:*)/Bash(grep:*)style allows added to silence old prompts, they are now redundant. The built-in/less-permission-promptsskill scans your transcripts and proposes a prune diff — run it once per project and once per user profile, then commit the accepted subset. The committed OrchestKitsrc/settings/ork.settings.jsonis already minimal (allow =Read,Glob,Grep, a small set of MCP entries) and doesn't need changes.
CC 2.1.129 —
Bash(mkdir *)/Bash(touch *)allow rules now work for in-project paths: previously silently rejected for project-relative paths; now honored as documented. Workaround entries enumerating explicit subpaths (Bash(mkdir:./src/*), etc.) can be collapsed back to the canonical glob form. Seereferences/cc-version-settings.md§ CC 2.1.129.
CC 2.1.157 — plugin auto-load + workflow-trigger control: Plugins in
.claude/skillsauto-load (no marketplace required);claude plugin init <name>scaffolds one there. The "Workflow keyword trigger" toggle in/config— and pressing backspace right after the keyword — stops a bare "workflow"/"ultracode" from launching a dynamic workflow.claude agentshonors theagentfield insettings.json, with--agent <name>to override.
CC 2.1.160 — write prompts for startup files & build configs: Expect approval prompts before Claude writes shell startup files (
.zshenv/.zlogin/.bash_login,~/.config/git/) or — inacceptEditsmode — build-tool configs that grant code execution (.npmrc,bunfig.toml,.bazelrc,.pre-commit-config.yaml,.devcontainer/). These are security defaults; approve them deliberately, don't pre-allow.
CC 2.1.141 —
ANTHROPIC_WORKSPACE_IDfor workload identity federation: When authenticating headless/CI agents (e.g./ork:ci-sentinel,/ork:bare-eval) through Anthropic's WIF flow, setANTHROPIC_WORKSPACE_IDto scope the minted token to one workspace when the federation rule covers more than one. Without it, a multi-workspace rule mints an unscoped token.
CC 2.1.142 —
MCP_TOOL_TIMEOUTfor remote MCP: the per-request timeout now actually applies to remote HTTP/SSE MCP servers (previously capped at 60s regardless of the configured value). Raise it (e.g.MCP_TOOL_TIMEOUT=180000) for long-poll tools — NotebookLMstudio_status, knowledge-base ingest, index rebuilds — that legitimately run past 60s, so they don't silently time out and self-skip.
CC 2.1.169 — safe-mode + policy-enforcement fixes:
--safe-mode(orCLAUDE_CODE_SAFE_MODE=1) starts CC with ALL customizations disabled — CLAUDE.md, plugins, skills, hooks, MCP servers — the fastest way to bisect "is ork (or any plugin) causing this?" before filing a bug. Enterprise managed MCP policies (allowedMcpServers/deniedMcpServers) are now enforced on reconnect, IDE-typed configs,--mcp-configservers in the first post-install session, and before remote settings load — if your org sets them, previously-working unlisted servers may now be (correctly) blocked. Untrusted project settings can no longer set OTEL client-certificate paths without trust confirmation. Self-hosted runners get apost-sessionlifecycle hook (after session end, before workspace deletion) for snapshotting uncommitted work or exporting logs, plus a configurable SIGTERM→SIGKILL window (default 5s).
CC 2.1.166 —
fallbackModelsetting (up to 3 models): thefallbackModelsetting now accepts up to three models, tried in order when the primary is overloaded or unavailable, and--fallback-modelnow also applies to interactive sessions (not just headless). Set it for longork:implement/ork:brainstormruns so an overloaded primary degrades to the next model instead of stalling the run. Extends the 2.1.152 fallback note inreferences/cc-version-settings.md.
CC 2.1.181 —
/config key=valuefor one-off settings: set any single setting straight from the prompt —/config thinking=false,/config model=opus— without opening the/configmenu or hand-editing a settings file. Works in interactive,-p, and Remote Control. This is the fast path for a one-off, ad-hoc setting change. It does not replace durable automation: a "whenever X, do Y" behavior still requires a hook insettings.json(the harness executes hooks;/configonly writes a setting value). Use/config key=valueto flip a setting now; use this skill's hook flow when the change must fire automatically every session. Seereferences/cc-version-settings.md§ CC 2.1.181.
All 4 MCPs ship enabled by default. Tavily requires an API key.
| 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) |
Why enabled? OrchestKit ships 30+ Sonnet/Haiku subagents. While Opus 5 has native extended thinking, Sonnet and Haiku do not — they benefit from sequential-thinking. Tavily is 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.
Opt out of claude.ai MCP servers (CC 2.1.63+): Claude Code may load MCP servers from claude.ai by default. To disable this and only use locally-configured MCPs:
export ENABLE_CLAUDEAI_MCP_SERVERS=false
Add to your shell profile (~/.zshrc or ~/.bashrc) to persist across sessions. This only affects MCP servers sourced from claude.ai — locally-configured MCPs in .mcp.json and ~/.claude/mcp.json are unaffected.
Load details: Read("${CLAUDE_PLUGIN_ROOT}/skills/configure/references/cc-version-settings.md") for full configuration options.
Covers CC 2.1.7 (MCP deferral threshold, effective context window), CC 2.1.20 (task deletion, PR enrichment, agent permissions, monorepo detection, team distribution), CC 2.1.23 (spinner verbs customization), and CC 2.1.79 (turn duration display).
prUrlTemplate (M122)For enterprise GitLab / GitHub Enterprise / Bitbucket installations with non-standard URL shapes, set prUrlTemplate in ~/.claude/settings.json (or project-level) to override URL construction in review-pr / create-pr / fix-issue:
{
"prUrlTemplate": "https://gitlab.acme.com/{owner}/{repo}/-/merge_requests/{n}"
}
Tokens: {host}, {owner}, {repo}, {n}. See src/skills/chain-patterns/references/pr-from-platform.md for the full host-family table and skill-side branching pattern.
Configure dual-channel telemetry for streaming session data to HQ or your own API.
AskUserQuestion(questions=[{
"question": "Set up session telemetry?",
"header": "Telemetry",
"options": [
{"label": "Full streaming (Recommended)", "description": "All 18 events stream via native HTTP + enriched summaries"},
{"label": "Summary only", "description": "SessionEnd and worktree events only (command hooks)"},
{"label": "Skip", "description": "No telemetry — hooks run locally only"}
],
"multiSelect": false
}])
Ask for the webhook URL in plain text — AskUserQuestion needs ≥2 options (CC schema minItems: 2) and can't capture a free-form URL, so prompt directly:
What is your webhook endpoint URL? Reply with the full URL (e.g.,
https://api.example.com/hooks).
Run the HTTP hook generator:
npm run generate:http-hooks -- <webhook-url> --write
# File: .claude/orchestration/config.json
saveConfig({ webhookUrl: "<webhook-url>" })
Set ORCHESTKIT_HOOK_TOKEN in your environment (never in config files):
export ORCHESTKIT_HOOK_TOKEN=your-secret
Two channels now active:
Channel 1 (HTTP): All 18 events → /cc-event (Bearer auth, zero overhead)
Channel 2 (Command): SessionEnd → /ingest (HMAC auth, enriched data)
Save webhookUrl to config and remind about env var (same as above, skip generator step).
Load Read("${CLAUDE_PLUGIN_ROOT}/skills/configure/references/http-hooks.md") for architecture details.
Tip (CC 2.1.69+): After saving configuration changes, run
/reload-pluginsto activate them without restarting your session.Tip (CC 2.1.152+): If you edited or added skills in a skill directory (personal
~/.claude/skills/or project.claude/skills/— not plugin-packaged ones), run/reload-skillsto re-scan and pick them up in the same session. ASessionStarthook can do the same by returningreloadSkills: true.
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, ... }
}
VSCode users can run /remote-control to bridge their terminal session to claude.ai/code. This lets you continue the same session from a browser or phone — useful for monitoring long-running configurations or agent tasks away from your desk.
ork:doctor: Diagnose configuration issuesLoad on demand with Read("${CLAUDE_PLUGIN_ROOT}/skills/configure/references/<file>"):
| File | Content |
|---|---|
references/presets.md | Preset definitions |
references/mcp-config.md | MCP configuration |
references/http-hooks.md | CC 2.1.63+ observability hooks (Langfuse, Datadog, custom endpoints) |
references/cc-version-settings.md | CC 2.1.7, 2.1.20, 2.1.23, 2.1.79 version-specific settings |