Assess a repository's readiness for an AI agent execution framework across five dimensions. Produce JSON or a table with readiness scores, estimated cost per run, and scaffold status, without changing repository files.
5-dimension harness readiness scorecard from `metaharness score {path}`. Returns harnessFit / compileConfidence / taskCoverage / toolSafety / memoryUsefulness + estCostPerRunUsd + scaffoldReady. Pure-read; subprocess invocation; degrades gracefully when MetaHarness is absent (ADR-150 architectural constraint).
Review the instructions the agent will receive before you install.
Surfaces the upstream metaharness score CLI as a ruflo skill. Use when
Claude Code needs to assess whether a repo is ready for harness adoption
before recommending the user run npx ruflo init or harness-mint.
Implementation: scripts/score.mjs.
npx metaharness score <path> --json (single subprocess,
60s hard timeout).{ harnessFit, compileConfidence, taskCoverage, toolSafety, memoryUsefulness, estCostPerRunUsd, recommendedMode, archetype, template, scaffoldReady, hardConstraints }.--alert-on-fit-below N: exit 1 when harnessFit < N.| Dimension | Value |
|---|---|
| harnessFit | 82/100 |
| compileConfidence | 100 |
| taskCoverage | 79 |
| toolSafety | 100 |
| memoryUsefulness | 40 |
| estCostPerRunUsd | $0.048 |
| recommendedMode | CLI + MCP |
| archetype | typescript-sdk-harness |
| template | vertical:coding |
| scaffoldReady | true |
Ruflo passes its own readiness check. memoryUsefulness: 40 is the
weakest dimension — track this as a leading indicator for future memory
work in the AgentDB layer.
node plugins/ruflo-metaharness/scripts/score.mjs --alert-on-fit-below 70 --format json
Exit 1 fails the build. Pair with harness-genome for the full
7-section view.
When metaharness is not installed and npx can't fetch it (offline,
no network, registry unreachable), the script emits:
{
"degraded": true,
"reason": "metaharness-not-available",
"hint": "Install with `npm i -D metaharness@~0.4.1` (pinned range — this plugin never fetches @latest) or verify network access for the one-time cache install."
}
and exits 0. Ruflo continues to function — this is the architectural constraint in action.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.