← ClaudeAtlas

harness-init-runnerlisted

Initialize a lightweight repo-local Node.js harness (harness/ + .harness/) WITHOUT AIOS dependency. Use ONLY when you need a standalone, portable harness. If AIOS is installed, use `aios-long-running-harness` instead — it has ContextDB integration, superpowers pairing, and checkpoint recovery.
rexleimo/harness-cli · ★ 42 · AI & Automation · score 74
Install: claude install-skill rexleimo/harness-cli
# Harness Init Runner (Node.js) Working directory: any Node.js repo with `package.json` Create a portable long-running-agent harness inside the **current repo** (Node.js), without pulling in the full AIOS workspace layout. ## When to use (even if AIOS is installed) - Use this when you want a **repo-local**, lightweight `harness/` runner that works across Codex / Claude Code / Gemini / opencode. - If you already use AIOS, you may not need this. However it can coexist: this skill creates `harness/` + `/.harness/` and does not depend on `scripts/aios.mjs`. ## What this skill generates (repo root) - `harness/` (runner code) - `harness.config.json` (provider command templates) - `/.harness/` (runtime artifacts root; gitignored) - `package.json` scripts: `harness:run`, `harness:doctor` - dependency: `zod` Runtime artifacts are written under `./.harness/runs/*` and MUST NOT be committed. ## Preconditions - Run from (or inside) a Node.js repo that has a `package.json`. - If `package.json` is missing, stop and ask the user whether to create a Node project first. ## Init Steps (deterministic) 1. Locate repo root by searching upward for `package.json`. 2. Copy the bundled templates from `assets/template/` into the target repo root: - copy `assets/template/harness/` → `<repoRoot>/harness/` - For `harness.config.json`: **if the file already exists, merge** (preserve user's existing keys, add only missing ones). **If it does not exist, copy the template.** Never silently o