example-harness
FeaturedScaffold a ready-made AI agent harness in one command from the 19 published @metaharness/* example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming, repo-maintainer).
Install
Quality Score: 90/100
Skill Content
Details
- Author
- ruvnet
- Repository
- ruvnet/metaharness
- Created
- 2 months ago
- Last Updated
- 2 days ago
- Language
- TypeScript
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
create-harness
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".
init-harness
One-shot initialization of a parallel-terminal Claude Code build harness in a project - a git worktree and branch per terminal, phase checkboxes as the task queue, pinned model/effort per agent, mechanical git-tag gates, hardened read/gate/log hooks, and a SQLite agent-memory shard per terminal. Use when the user says "/init-harness", "init-harness", "initialize the harness", "set up the build harness", "scaffold this project's harness", "bootstrap the agent harness", or drops in a project-context.yml and asks to initialize. Also use when a project needs multi-terminal agent orchestration with gates, or when an existing harness must be verified or repaired (hooks not firing, guards not blocking, .agents drift). Do NOT use for adding a single agent or skill to an existing project.
harness-cli
Use when working with other agents or the harness from inside a runner-spawned task — messaging peers on the agentboard, spawning / driving / killing worker agent sessions, delegating one-shot tasks, moving files in or out of a task's worktree, notifying the human operator, or discovering live agents and topics. Also defines the agentboard conventions (handshake, reply topics, trust model). Reply delivery is asynchronous via the inbox hook — never block on wait/dispatch from an agent turn.