Repo Genome

What it does

When your agent uses it

• Tasks that involve Bioinformatics
• Tasks that involve Architecture decision records
• Tasks that involve Feature launches and release readiness

Example prompts

• “/repo-genome”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Repo profile — type, languages, build/test commands, ci presence
2. 2Agent topology — recommended roles (maintainer / tester / security / release)
3. 3MCP risk model — surface + numeric risk + policy posture
4. 4Test confidence — how strong are the test signals
5. 5Release readiness — buildable / testable / ci-wired
6. 6Recommended harness plan — template, archetype, hosts, agents, skills
7. 7Scorecard — risk_score, publish_readiness, test_confidence

What it can do on your machine

Read from SKILL.md and the folder at commit e0dfd44. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are bash and json).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Repo Genome loads about 772 tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 241 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~75

When it runs · the whole SKILL.md, loaded when a task matches

~772

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ruvnet/metaharness at commit e0dfd44, republished under its MIT licence (© ruvnet). 241 words, ~772 tokens.

name

repo-genome

description

7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.

/repo-genome path=./my-repo
/repo-genome path=./my-repo bundle=true
/repo-genome path=./my-repo out=./harness-genome.json

harness genome ./my-repo                          # text report
harness genome ./my-repo --json                   # 6-field scorecard JSON
harness genome ./my-repo --bundle                 # ADR-031 schema-1 envelope
harness genome ./my-repo --out harness-genome.json # write scorecard to file

{
  "repo_type": "rust_node_polyglot_mcp_ci",
  "agent_topology": ["maintainer", "tester", "security", "release"],
  "risk_score": 0.31,
  "mcp_surface": "local_default_deny",
  "test_confidence": 0.86,
  "publish_readiness": 0.78
}

© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude-plugin/skills/repo-genome of ruvnet/metaharness.

Open the folder on GitHubat commit e0dfd44