create-harness
This skill scaffolds an AI agent harness — your own focused, branded harness with its own npx <name> CLI, MCP server registration, memory namespace, learning loop, and marketplace identity.
When to use this skill
Use this skill when the user wants any of:
- A custom MCP-server-backed AI assistant (legal, trading, support, ops, …)
- A Claude Code plugin that bundles their own agents/skills/prompts
- A Codex skill that wraps a kernel + tools
- A pi.dev extension or Hermes agent runtime config
- A standalone npm package they can
npm publish under their own scope
How to invoke
/create-harness
The skill asks for:
- Harness name (kebab-case, e.g.
legal-redline)
- Description (one line)
- Host(s) — Claude Code, Codex, pi.dev, Hermes (multi-select)
- Template —
minimal (default), vertical:trading, vertical:support, vertical:devops, vertical:legal, vertical:research, or eject-from-ruflo
- Memory backend — AgentDB (default), SQLite-only, in-memory
- Routing strategy — 3-tier (default) or single-tier
- Marketplace — independent (no ruflo branding) or powered-by
Under the hood
Calls npx create-agent-harness <name> with the user's choices, copies the chosen template into the current directory, runs the post-generation smoke test, and emits a .harness/manifest.json so future updates can harness upgrade cleanly (copier-style regenerate-diff-merge).
Outputs
| File |
Purpose |
package.json |
The harness's npm package, ready to npm publish |
bin/<name>.js |
The CLI binary your users invoke |
.claude/settings.json (if Claude Code host) |
MCP + hooks wiring |
.codex/config.toml (if Codex host) |
MCP table in TOML |
AGENTS.md + SYSTEM.md (if pi.dev host) |
Pi extension instructions |
cli-config.yaml (if Hermes host) |
Hermes runtime config |
.harness/manifest.json |
Generator state — drives drift detection (ADR-008) |
witness.json |
Ed25519-signed provenance manifest (ADR-011) |
After scaffolding
The user can:
cd <name>
npm install
npm test
npm publish # ship their harness to npm
# their users: npx <name> init
Notes for the model
- This is a deterministic operation — defer to
create-agent-harness for the actual file creation, do NOT generate harness file contents yourself
- The witness manifest is required — do not skip it
- If the user asks for "ruflo for X" or "my own ruflo", recommend
vertical:<X> templates first and offer minimal as the fallback
- Multi-host is supported but increases the harness's surface area — recommend single-host for first-time users unless they explicitly need multi-host
1---2name: create-harness3description: Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a vertical AI assistant for X".4---56# create-harness78This skill scaffolds an AI agent harness — your own focused, branded harness with its own `npx <name>` CLI, MCP server registration, memory namespace, learning loop, and marketplace identity.910## When to use this skill1112Use this skill when the user wants any of:1314- A custom MCP-server-backed AI assistant (legal, trading, support, ops, …)15- A Claude Code plugin that bundles their own agents/skills/prompts16- A Codex skill that wraps a kernel + tools17- A pi.dev extension or Hermes agent runtime config18- A standalone npm package they can `npm publish` under their own scope1920## How to invoke2122```23/create-harness24```2526The skill asks for:27281. **Harness name** (kebab-case, e.g. `legal-redline`)292. **Description** (one line)303. **Host(s)** — Claude Code, Codex, pi.dev, Hermes (multi-select)314. **Template** — `minimal` (default), `vertical:trading`, `vertical:support`, `vertical:devops`, `vertical:legal`, `vertical:research`, or `eject-from-ruflo`325. **Memory backend** — AgentDB (default), SQLite-only, in-memory336. **Routing strategy** — 3-tier (default) or single-tier347. **Marketplace** — independent (no ruflo branding) or powered-by3536## Under the hood3738Calls `npx create-agent-harness <name>` with the user's choices, copies the chosen template into the current directory, runs the post-generation smoke test, and emits a `.harness/manifest.json` so future updates can `harness upgrade` cleanly (copier-style regenerate-diff-merge).3940## Outputs4142| File | Purpose |43|---|---|44| `package.json` | The harness's npm package, ready to `npm publish` |45| `bin/<name>.js` | The CLI binary your users invoke |46| `.claude/settings.json` (if Claude Code host) | MCP + hooks wiring |47| `.codex/config.toml` (if Codex host) | MCP table in TOML |48| `AGENTS.md` + `SYSTEM.md` (if pi.dev host) | Pi extension instructions |49| `cli-config.yaml` (if Hermes host) | Hermes runtime config |50| `.harness/manifest.json` | Generator state — drives drift detection (ADR-008) |51| `witness.json` | Ed25519-signed provenance manifest (ADR-011) |5253## After scaffolding5455The user can:5657```bash58cd <name>59npm install60npm test61npm publish # ship their harness to npm62# their users: npx <name> init63```6465## Notes for the model6667- This is a deterministic operation — defer to `create-agent-harness` for the actual file creation, do NOT generate harness file contents yourself68- The witness manifest is required — do not skip it69- If the user asks for "ruflo for X" or "my own ruflo", recommend `vertical:<X>` templates first and offer `minimal` as the fallback70- Multi-host is supported but increases the harness's surface area — recommend single-host for first-time users unless they explicitly need multi-host
ruvnet