orchestkit

Official CLI for OrchestKit, the free, MIT-licensed Claude Code plugin published by the Yonyon software studio.

Status: not yet published to npm. The source lives here and the binary builds and passes its suite, but npm publish has not been run. Do not document npx orchestkit on the website until the first release is live: a published-looking install command that 404s is worse than none.

What it does

OrchestKit itself installs into Claude Code, not into your shell. This CLI is the scripting surface around it: it prints the install command, emits MCP client config, and queries the public read-only docs API from a terminal or a CI job without writing a fetch wrapper first.

orchestkit install            # print the Claude Code install command
orchestkit search <query>     # search the documentation
orchestkit ask <question>     # natural-language query (NLWeb /ask)
orchestkit read <page>        # print a docs page as Markdown
orchestkit mcp [http|stdio]   # emit MCP client config
orchestkit doctor             # check Node, API reachability, rate-limit budget

Options: --limit <n>, --json, --base-url <url> (or ORCHESTKIT_BASE_URL).

Examples

orchestkit search "parallel agents" --limit 3
orchestkit read foundations/overview > overview.md
orchestkit mcp stdio > mcp.json
orchestkit search "hooks" --json | jq -r '.[].url'

Library use

The same surface is importable, so a script can skip the shell:

import { createClient, search } from "orchestkit";

const { results, rateLimit } = await search(createClient(), "memory", 5);
console.log(results[0]?.url, `${rateLimit.remaining}/${rateLimit.limit} left`);

API contract

The docs API is public, read-only and unauthenticated.

• Rate limits, 120 requests per minute per IP per endpoint. Every response carries the IETF RateLimit-* headers; the CLI surfaces the remaining budget after each call so scripts can pace themselves instead of probing.
• Errors, RFC 9457 Problem Details. ApiError.problem exposes the parsed object, including the links recovery hops a 404 carries.
• Versioning and deprecation, https://orchestkit.yonyon.ai/api-policy.

Requirements

Node >= 20 (uses global fetch). Zero runtime dependencies.

Development

npm run build        # tsc + shebang/exec-bit fixup
npm test             # unit suite + spawn tests against the built binary
npm run publish:dry-run

npm test spawns dist/cli.js for real, so run npm run build first or those cases skip. Networked commands are spawned with a preloaded fetch stub (tests/fixtures/fetch-stub.mjs), hermetic, no socket, no live site.

Releasing

1. npm run build && npm test && npm run publish:dry-run
2. npm publish --access public (name orchestkit was unregistered as of 2026-08-21; re-check before releasing)
3. Only then: add the CLI to DEVELOPER_RESOURCES in docs/site/lib/developer-resources.ts and to the package list in docs/site/app/llms.txt/route.ts, so the site starts claiming it the day it becomes true.

MIT © Yonatan Gross