prime-radiant-inc

Everyharness — Development skill for Claude Code

Development community

Generate a coding-agent plugin for every harness from one config file.

How to install Everyharness

This entry records only its repository, not the path inside it, so there is no exact command to give. Open prime-radiant-inc/everyharness and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Everyharness does

Generate a coding-agent plugin for every harness from one config file.

Alternatives in Development

Claude Config — Built-in /config command to manage settings interactively 81.1k ★
Check 1: Cache Exists? — CLAUDE_DIR="${CLAUDE_CONFIG_DIR:-$HOME/.claude}" CACHE_EXISTS=$(ls -d "$CLAUDE_DIR/plugins/cache/claude-hud" 2 10.9k ★
Octo Doctor — Environment diagnostics — check providers, auth, config, hooks, scheduler, and more 2.8k ★

README

everyharness

[!NOTE] **v1.0.0.** The v1 feature set is complete: eleven harness adapters, init/import, generated install docs, and container-backed install checks. The `everyharness.yaml` schema and the generation-manifest format are stable as of 1.0. Not yet published to npm; install is clone-and-build (see [docs/BROCHURE.md](docs/BROCHURE.md), Getting started).

Generate a coding-agent plugin for every harness from one config file.

What it is and who it's for: [docs/BROCHURE.md](docs/BROCHURE.md).

The goal: one `everyharness.yaml` as the source of truth, with `everyharness generate` emitting native plugin manifests, bootstrap wiring, docs, and tests for every supported coding-agent harness (Claude Code, Codex, Gemini CLI, Cursor, Copilot CLI, OpenCode, Pi, Kimi Code, Hermes, Devin CLI, Factory Droid, Grok Build CLI, Antigravity). Generated files are committed; `everyharness validate` catches drift in CI.

Usage

npx everyharness init       # scaffold a new plugin
npx everyharness import     # convert an existing Claude-format plugin
npx everyharness generate   # emit per-harness files from everyharness.yaml
npx everyharness validate   # drift + schema checks (exit 1 = config error, 3 = drift, 2 = schema)
npx everyharness matrix     # component-support matrix
npx everyharness test       # container-backed offline install checks (needs docker; exit 2 = failed checks)
npx everyharness bump 1.2.3 # set the version everywhere + regenerate (also --check / --audit; reads release:)

`everyharness test` runs two offline tiers inside the container: first it parses every generated harness manifest and confirms referenced paths exist, then it performs a **real install** of the plugin into each harness CLI (claude, codex, gemini, opencode, grok, droid, hermes, copilot, pi) and asserts the CLI actually enumerates the plugin's skills — the check that catches a manifest that parses but is wired to the wrong place. Harnesses with no offline enumeration path