Orchestkit

114 skills · 36 agents · 219 hooks

Contents

• Quick Start
• Why OrchestKit?
• What You Get
• Key Commands
• Configuration
• Install
• FAQ
• Development
• What's New
• Community

Quick Start

/plugin marketplace add yonatangross/orchestkit
/plugin install ork

Then start your personalized onboarding:

/ork:setup

The setup wizard scans your codebase, detects your tech stack, recommends skills for your needs, configures MCP servers, and creates a readiness score — all in one command.

Why OrchestKit?

Every Claude Code session starts from zero. You explain your stack, patterns, preferences—again and again.

OrchestKit gives Claude persistent knowledge of production patterns that work automatically:

What You Get

One unified plugin, everything included.

All available in a single /plugin install ork. Skills load on-demand. Hooks work automatically.

Browse everything in the Docs →

Key Commands

/ork:auto         # Front door: describe a goal, it routes to the right skill
/ork:setup        # Personalized onboarding wizard
/ork:implement    # Full-stack implementation with parallel agents
/ork:expect       # Diff-aware AI browser testing
/ork:review-pr    # PR review with parallel agents
/ork:verify       # Multi-agent validation
/ork:commit       # Conventional commit with pre-checks
/ork:explore      # Analyze unfamiliar codebase
/ork:remember     # Save to persistent memory
/ork:doctor       # Health check

Configuration

/ork:setup detects your stack, recommends MCP servers, and writes the configuration for you.

Recommended MCP Servers

Set "alwaysLoad": true on the first three in your .mcp.json. It skips the per-skill tool probe and shaves ~150ms off cold starts.

Customizing skills

Skills install as files on your disk, but don't hand-edit the installed copy — it gets overwritten on update and silently diverges from the canonical playbook. The supported ways to extend (user-level skills, project skills, upstream PRs, or disabling a bundled skill) are in docs/extending-skills.md.

Install

/plugin install ork

No tiering. No version confusion. Just one powerful plugin.

Not on Claude Code? Pull the skills into any agent (Cursor, Codex, OpenCode, …) via skills.sh:

npx skills add yonatangross/orchestkit

FAQ

/plugin list
/plugin uninstall ork && /plugin install ork

Run /ork:doctor to diagnose.

Requires ≥2.1.220 (supported floor; Opus 5 as the default Opus, xhigh effort, dynamic workflows, sandbox.network.strictAllowlist, native binary, hardened Bash(rm:*)/Bash(find:*) rules). Check with claude --version.

Raising this floor is a breaking change and ships as a major release. See STABILITY.md for the full contract, and shared/cc-support.json for the authoritative window.

Development

npm run build      # Build plugins from src/
npm test           # Run all tests

Edit src/ and manifests/, never plugins/ (generated).

See CONTRIBUTING.md for details.

What's New

v9.1.1 · 2026-07-26

• sync README and changelog data to v9.1.0 (#3167)

v9.1.0 · 2026-07-26

• retro-hardening mechanisms 5+6 (invocability check, byte-budget guard) (#3161)
• viz: re-anchor visual-style rule + quickviz on-ramp (#3164)
• viz: stop throttling explicit visual asks (#3166)

v9.0.2 · 2026-07-26

• ci: remove the Claude PR Review workflow and its labeler (#3159)

v9.0.1 · 2026-07-26

• bound rotated analytics archives, unstale the CC floor (#3156)
• build: default-deny frontmatter gate, pass all 10 fields (#3158)
• readme: refresh What's New for 9.0.0 and isolate the RTL table cell (#3153)
• cc-watch: snapshot upstream CHANGELOG (2.1.220) (#3155)

v9.0.0 · 2026-07-25

• cc: the Claude Code support floor is now 2.1.220. Claude Code 2.1.206 through 2.1.219 are no longer supported; hooks and skills may no-op or error on them, and that is not treated as a bug. Upgrade Claude Code before updating OrchestKit.
• cc: adopt Opus 5, strict-renew the support floor to 2.1.220 (#3141)
• verify: add the Reachability Proof axis (REACHED vs UNREACHED) (#3149)
• docs: pin playground links to the commit SHA, not the branch (#3148)
• hooks: bound hook-timing.jsonl, the one analytics file with no cap (#3151)
• …and 1 more (see CHANGELOG.md)

v8.85.0 · 2026-07-25

• agent activation routing (M170) (#3133)
• 3 defects found by /ork:assess on the M170 diff (#3136)
• build: stop dropping argument-hint from generated commands (#3146)
• hooks: make network-egress-guard DENY tier quote-aware (#3124)
• hooks: redirect pipe-to-interpreter deny instead of dead-ending (#3121)
• …and 8 more (see CHANGELOG.md)

v8.84.10 · 2026-07-23

• ci: drop the What's New freshness gate blocking the PR queue (#3118)
• deps: bump the npm-minor-patch group across 1 directory with 4 updates (#3111)
• deps: bump the remotion group across 1 directory with 21 updates (#3110)
• bump the github-actions group across 1 directory with 6 updates (#3112)

v8.84.9 · 2026-07-23

• ci: scope What's New --check to PRs, refresh for 8.84.8 (#3113)
• review: allow the release bot to trigger a review (#3114)
• review: skip auto-label on Dependabot PRs (no secret access) (#3116)

See CHANGELOG.md for the full release history.

Community

Join the Building with AI community for AI dev tips, OrchestKit support, and connecting with other builders:

Names and audiences match what yonyon.ai renders, so the two surfaces cannot drift. Every link resolves through yonyon.ai/go/*, so a rotated invite never needs a README change and no raw invite is published here.

Docs · Issues · Discussions · Community

MIT License · @yonatangross