home / skills / yonatangross / orchestkit / configure

configure skill

/plugins/ork/skills/configure

This skill guides you through configuring OrchestKit settings to tailor MCPs, hooks, and agents for your development workflow.

npx playbooks add skill yonatangross/orchestkit --skill configure

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
4.9 KB
---
name: configure
license: MIT
compatibility: "Claude Code 2.1.34+."
description: "Configures OrchestKit settings. Use when customizing MCP servers, plugin options, or preferences."
argument-hint: "[preset-name]"
context: inherit
version: 1.0.0
author: OrchestKit
tags: [configuration, setup, wizard, customization]
user-invocable: true
allowed-tools: [Bash, Read, Grep, Glob]
complexity: low
metadata:
  category: workflow-automation
---

# OrchestKit Configuration

Interactive setup for customizing your OrchestKit installation.

## Quick Start

```bash
/configure
```

## Step 1: Choose Preset

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 |

## Step 2: Customize Skill Categories

Categories available:
- AI/ML (26 skills)
- Backend (15 skills)
- Frontend (8 skills)
- Testing (13 skills)
- Security (7 skills)
- DevOps (4 skills)
- Planning (6 skills)

## Step 3: Customize Agents

**Product Agents (6):**
- market-intelligence
- product-strategist
- requirements-translator
- ux-researcher
- prioritization-analyst
- business-case-builder

**Technical Agents (14):**
- backend-system-architect
- frontend-ui-developer
- database-engineer
- llm-integrator
- workflow-architect
- data-pipeline-engineer
- test-generator
- code-quality-reviewer
- security-auditor
- security-layer-auditor
- debug-investigator
- metrics-architect
- rapid-ui-designer
- system-design-reviewer

## Step 4: Configure Hooks

**Safety Hooks (Always On):**
- git-branch-protection
- file-guard
- redact-secrets

**Toggleable Hooks:**
- Productivity (auto-approve, logging)
- Quality Gates (coverage, patterns)
- Team Coordination (locks, conflicts)
- Notifications (desktop, sound)

## Step 5: Configure MCPs (Optional)

All MCPs disabled by default. Enable selectively:

| MCP | Purpose |
|-----|---------|
| context7 | Library documentation |
| sequential-thinking | Complex reasoning |
| memory | Cross-session persistence |
| playwright | Browser automation |

## Step 6: CC 2.1.7 Settings (New)

Configure CC 2.1.7-specific features:

### Turn Duration Display

```
Enable turn duration in statusline? [y/N]: y
```

Adds to settings.json:
```json
{
  "statusline": {
    "showTurnDuration": true
  }
}
```

### MCP Auto-Deferral Threshold

```
MCP deferral threshold (default 10%): 10
```

Adds to config.json:
```json
{
  "cc217": {
    "mcp_defer_threshold": 0.10,
    "use_effective_window": true
  }
}
```

### Effective Context Window Mode

```
Use effective context window for calculations? [Y/n]: y
```

When enabled:
- Statusline shows `context_window.effective_percentage`
- Compression triggers use effective window
- MCP deferral more accurate

## Step 7: CC 2.1.20 Settings

Configure CC 2.1.20-specific features:

### Task Deletion Support

```
Enable task deletion (status: "deleted")? [Y/n]: y
```

Enables orphan detection and automatic cleanup of blocked tasks.

### PR Status Enrichment

```
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.

### Background Agent Permission Pre-Mapping

```
Enable permission profile suggestions for agents? [Y/n]: y
```

Shows recommended permission profiles when spawning agents.

### Monorepo Multi-Directory Detection

```
Enable monorepo detection? [Y/n]: y
```

Detects monorepo indicators and suggests `--add-dir` usage.

## Step 8: CC 2.1.23 Settings

Configure CC 2.1.23-specific features:

### Spinner Verbs Customization

Replace default Claude Code spinner verbs ("Thinking", "Working", etc.) with custom branding:

```
Customize spinner verbs? [Y/n]: y
```

Adds to `.claude/settings.json`:
```json
{
  "spinnerVerbs": {
    "mode": "replace",
    "verbs": [
      "Orchestrating",
      "Coordinating",
      "Synthesizing",
      "Analyzing",
      "Reasoning",
      "Crafting",
      "Architecting",
      "Validating",
      "Dispatching",
      "Assembling",
      "Engineering",
      "Composing"
    ]
  }
}
```

**Options:**
- `mode: "replace"` - Use only your custom verbs
- `mode: "append"` - Add your verbs to the defaults

**OrchestKit-themed verbs** focus on orchestration, architecture, and engineering actions.

## Step 9: Preview & Save

Save to: `~/.claude/plugins/orchestkit/config.json`

```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, ... }
}
```

## Related Skills
- doctor: Diagnose configuration issues
## References

- [Presets](references/presets.md)
- [MCP Configuration](references/mcp-config.md)

Overview

This skill configures OrchestKit settings through an interactive CLI flow. It guides selection of presets, skill categories, agents, hooks, MCPs, and versioned Claude Code (CC) feature toggles. Use it to produce a tailored config.json for your development environment.

How this skill works

The skill walks you step-by-step: choose a preset, enable skill categories, pick product and technical agents, and toggle safety and productivity hooks. It offers optional MCP activation and exposes CC-specific toggles (2.1.7, 2.1.20, 2.1.23) such as turn-duration display, MCP deferral thresholds, PR enrichment, permission suggestions, and custom spinner verbs. At the end it previews the resulting settings and saves a ready-to-use config file.

When to use it

  • On first installation to create a baseline OrchestKit profile
  • When onboarding a team with specific agent and hook needs
  • Before enabling MCPs or experimental CC features in production
  • When customizing safety, notifications, or monorepo behavior
  • To create environment-aware presets for CI or developer machines

Best practices

  • Start from a preset (Complete, Standard, Lite) then selectively disable features you don’t need
  • Keep safety hooks enabled (git-branch-protection, file-guard, redact-secrets) as default
  • Enable MCPs only for features you require (memory, sequential-thinking, playwright, context7) to limit surface area
  • Use effective context window and MCP deferral tuning for large-context models to avoid unnecessary processing
  • Preview the generated configuration and test in a staging session before rolling to production

Example use cases

  • Create a developer workstation config with UI/frontend skills enabled and monorepo detection on
  • Provision a CI agent profile with testing and quality gates hooks but no interactive agents
  • Enable memory MCP and sequential-thinking for long-running RAG workflows
  • Turn on PR status enrichment and background agent permission suggestions for a team using automated agents
  • Customize spinner verbs and turn-duration display for clearer session telemetry during demos

FAQ

Where is the final configuration saved?

The flow previews and writes a JSON configuration file to your user Claude plugin path so your OrchestKit plugin reads the new settings.

Are safety hooks mandatory?

Safety hooks are recommended and enabled by default; you can toggle non-safety hooks like productivity or notifications as needed.