/harness-genome
7-section repo readiness report from `metaharness genome {path}`. Returns repo_type / agent_topology / risk_score / mcp_surface / test_confidence / publish_readiness. Pure-read; degrades gracefully (ADR-150).
Claude Code
$ npx -y skills add ruvnet/ruflo --skill harness-genome --agent claude-code
Codex
$ npx skills add ruvnet/ruflo --skill harness-genome -a codex -y
Cursor
$ npx skills add ruvnet/ruflo --skill harness-genome -a cursor -y
Gemini CLI
$ npx skills add ruvnet/ruflo --skill harness-genome -a gemini-cli -y
GitHub Copilot
$ npx skills add ruvnet/ruflo --skill harness-genome -a github-copilot -y
OpenCode
$ npx skills add ruvnet/ruflo --skill harness-genome -a opencode -y
Windsurf
$ npx skills add ruvnet/ruflo --skill harness-genome -a windsurf -y
SKILL.md
harness-genome.SKILL.mdname: harness-genome
description: 7-section repo readiness report from `metaharness genome {path}`. Returns repo_type / agent_topology / risk_score / mcp_surface / test_confidence / publish_readiness. Pure-read; degrades gracefully (ADR-150).
argument-hint: "[--path .] [--alert-on-risk-above 0.5] [--format table|json]"
allowed-tools: BashCompanion to `harness-score`. Where score is a 5-dimension numeric scorecard, genome is a 7-section categorical/numeric report covering repo type, agent topology recommendations, risk score (0-1), MCP surface area, test confidence (0-1), and publish readiness (0-1).
Algorithm
Implementation: [`scripts/genome.mjs`](../../scripts/genome.mjs).
1. Shell out to `npx metaharness genome <path> --json` (60s hard timeout). 2. Parse the shape: `{ repo_type, agent_topology[], risk_score, mcp_surface, test_confidence, publish_readiness }`. 3. Preserve upstream's readiness verdict as `verdict` and `verdictExitCode`. Upstream exits 1 for `needs-work` and 2 for `blocked`; these are valid reports, so the wrapper returns them successfully. 4. If `--alert-on-risk-above N`: exit 1 when `risk_score > N`. 5. Output JSON (default) or markdown.
Phase-0 baseline (ruflo, measured 2026-06-16)
{
"repo_type": "node_mcp_ci",
"agent_topology": ["maintainer", "tester", "security", "release"],
"risk_score": 0.27,
"mcp_surface": "remote",
"test_confidence": 0.8,
"publish_readiness": 0.9
}Ruflo's `risk_score: 0.27` is low (good). `publish_readiness: 0.9` is high. The `mcp_surface: "remote"` reflects that ruflo's MCP servers are hosted, not bundled.
When to use
- Pre-mint review: "before scaffolding a custom harness from this repo,
should we?" — genome answers it categorically.
- Drift detection: capture genome snapshots over time, diff via
cost-diff-style tooling to spot when `agent_topology` recommendations drift away from a deliberate architecture choice.
- CI gate: `--alert-on-risk-above 0.5` fails the build when the repo's
risk profile crosses a threshold.
Pairs with
- `harness-score` — numeric readiness
- `harness-mcp-scan` — static MCP security findings
- `harness-threat-model` — enterprise-review-grade threat model
Read more
name: harness-genome
description: 7-section repo readiness report from `metaharness genome {path}`. Returns repo_type / agent_topology / risk_score / mcp_surface / test_confidence / publish_readiness. Pure-read; degrades gracefully (ADR-150).
argument-hint: "[--path .] [--alert-on-risk-above 0.5] [--format table|json]"
allowed-tools: BashCompanion to `harness-score`. Where score is a 5-dimension numeric scorecard, genome is a 7-section categorical/numeric report covering repo type, agent topology recommendations, risk score (0-1), MCP surface area, test confidence (0-1), and publish readiness (0-1).
Algorithm
Implementation: [`scripts/genome.mjs`](../../scripts/genome.mjs).
1. Shell out to `npx metaharness genome <path> --json` (60s hard timeout). 2. Parse the shape: `{ repo_type, agent_topology[], risk_score, mcp_surface, test_confidence, publish_readiness }`. 3. Preserve upstream's readiness verdict as `verdict` and `verdictExitCode`. Upstream exits 1 for `needs-work` and 2 for `blocked`; these are valid reports, so the wrapper returns them successfully. 4. If `--alert-on-risk-above N`: exit 1 when `risk_score > N`. 5. Output JSON (default) or markdown.
Phase-0 baseline (ruflo, measured 2026-06-16)
{
"repo_type": "node_mcp_ci",
"agent_topology": ["maintainer", "tester", "security", "release"],
"risk_score": 0.27,
"mcp_surface": "remote",
"test_confidence": 0.8,
"publish_readiness": 0.9
}Ruflo's `risk_score: 0.27` is low (good). `publish_readiness: 0.9` is high. The `mcp_surface: "remote"` reflects that ruflo's MCP servers are hosted, not bundled.
When to use
- Pre-mint review: "before scaffolding a custom harness from this repo,
should we?" — genome answers it categorically.
- Drift detection: capture genome snapshots over time, diff via
cost-diff-style tooling to spot when `agent_topology` recommendations drift away from a deliberate architecture choice.
- CI gate: `--alert-on-risk-above 0.5` fails the build when the repo's
risk profile crosses a threshold.
Pairs with
- `harness-score` — numeric readiness
- `harness-mcp-scan` — static MCP security findings
- `harness-threat-model` — enterprise-review-grade threat model
📖 RuFlo Explained — Build an AI Team That Plans, Remembers, Tests, and Improves A 14-chapter guide: from the basic idea to a first useful task, then memory, agent teams, plugins, cost and verification. Agent = Model + Harness.
Other skills on ruflo.
More skills from other plugins.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by…
bmad
Answers BMad questions and recommends the next skill from what is installed. Use when the user asks bmad for help, what to do…
Questions about harness-genome.
- Which coding agents can use harness-genome?
- harness-genome installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

