eval-harness
Skill7 starsChanged 53 days agoMITView on GitHub
Select and run Roboclaws validation, product, eval-suite, and live-agent eval rows from a plan, diff, or explicit capability request.
79 other projects use a version of this.
Adopted by
Most recently taken up by
- hmohammed7/claude-skillstheir own version, first seen Nov 16, 2026
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- nano-step/eval-harnesstheir own version, first seen Nov 8, 2026
- Ashfaqbs/ai-coding-agent-toolkittheir own version, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- ufukyuksel-dev/SUPER_COMPUTER_AItheir own version, first seen Nov 1, 2026
Used with
Projects with it also use brand-discovery, agent-sort and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ysyecustSkillbrand-discovery
Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).
Also in 6 projects that use this
niloykumarbarmanSkillagent-sort
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
Also in 14 projects that use this
royaluniondesign-sysSkillconfigure-ecc
Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.
Also in 12 projects that use this
junimnjwSkillralphinho-rfc-pipeline
RFC-driven multi-agent DAG execution pattern with quality gates, merge queues, and work unit orchestration.
Also in 12 projects that use this
loulanyueSkillnuxt4-patterns
Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
Also in 10 projects that use this
royaluniondesign-sysSkillcontent-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
Also in 16 projects that use this
Other versions79 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 79
- affaan-m/ECC★ 246ksame name
- xu-xiang/everything-claude-code-zh★ 1.9ksame name
- allenhutchison/obsidian-gemini★ 534same name
- loulanyue/awesome-claude-notes★ 272same name
- cloudnative-co/claude-code-starter-kit★ 153same name
- tpavanipradeep/everything-claude-code★ 104same name
- mturac/everything-openai-codex★ 89same name
- mit-network/everything-claude-code★ 76same name
- Fmarzochi/EGC★ 61same name
- drvoss/everything-copilot-cli★ 49same name
69 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- eval-evolutionSkill
- household-worldSkill
- raw-fpv-visual-labelerSkill
- report-performance-analysisSkill
- scene-gaussian-map-alignmentSkill
- visual-result-showcaseSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.
0
Common
Most of the 73 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when a Roboclaws plan, diff, PR, or agent-facing change needs one maintainer proof surface.
- Very specific: line 20
Use Just only as the human-facing facade shown below.
- Distinctive: line 53
Run one versioned suite directly as a lower-level row/debugging path:
- Very specific: line 92
All named baseline profiles run selected rows or record explicit blocked evidence.
- Very specific: line 109
Never downgrade a selected live-agent eval into deterministic-only success.
- Very specific: line 158
Do not use or recreate a user-facing agent-validation-matrix route.
“Common” is measured: kept by at least 6 in 10 of the 73 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Eval Harness
Use this skill when a Roboclaws plan, diff, PR, or agent-facing change needs one maintainer proof surface. The skill answers:
- which deterministic gates, product runs, eval suites, and live-agent evals are relevant;
- why each row was selected, skipped, run, failed, or blocked;
- where the resulting reports and regression-promotion evidence live.
It is an orchestration skill, not a robot behavior skill. Keep household-world
task strategy in household-world; keep reusable robot capability semantics
in MCP tools and capability profiles.
Use Just only as the human-facing facade shown below. Frozen rows execute their
package owners directly: eval rows use python -m roboclaws.evals.cli, and
product rows use python -m roboclaws.cli.main run surface. Keep the subprocess
boundary for row timeout and isolation; do not route an executing row back
through Just or add a second command registry. The eval CLI grammar is an
optional documented kebab-case tool name followed by key=value arguments.
Commands
Recommend rows without running them:
just agent::eval recommend plan=docs/plans/example.md budget=focusedExecute relevant rows for a plan or diff:
just agent::eval execute plan=docs/plans/example.md budget=focused
just agent::eval execute since=origin/main budget=focused
just agent::eval execute profile=baseline-core budget=focused max_parallel=4Pass scene=<source>/<index>,... to expand rows whose catalog uses scene_scope=selected; the current scene-portable rows are the MapBuild product rows. Case identity, dependencies, commands, and result schema are resolved before local execution. Scheduling respects shared backend locks and writes one result per frozen benchmark case.
Refresh the current baseline at the appropriate cost tier:
just agent::eval execute profile=baseline-core budget=focused
just agent::eval execute profile=baseline-live-default budget=focused
just agent::eval execute profile=baseline-refresh budget=focusedRun one versioned suite directly as a lower-level row/debugging path:
just agent::eval suite=cleanup_capability budget=smokePromote failed, blocked, or inconclusive eval evidence:
just agent::eval promote-regression \
eval_results=output/evals/<suite>/<stamp>/eval_results.json \
source_sample_id=<sample-id> \
regression_sample_id=regression.<name>Profiles And Budgets
recommend: never executes rows; it lists commands and preflight needs.profile=adaptive: default mode; select rows from plan text, diff paths, and explicit axes.profile=baseline-core: select deterministic gates, current eval suites, direct local-simulator product rows, and DINO product rows. It excludes all live-provider rows and is the normal broad local refresh.profile=baseline-live-default: selectbaseline-coreplus the current MiniMax live-agent capability rows and the direct same-run map-build-to-consumer proof. Its open-task and cleanup consumers require the canonical prior; it excludes the alternate-provider fixed-prior matrix.profile=baseline-refresh: select the catalog baseline set directly: deterministic gates, all current eval suites including long-horizon tasks, direct product rows, DINO rows, all default live rows, and the explicit alternate-provider matrix. Prior-consuming rows resolve the canonical prior fromassets/eval-priors/runtime_map_prior_catalog.jsonby default; an explicitruntime_map_prior=<path>is allowed for a controlled refresh. A missing prior remains selected and records an explicit blocker instead of silently removing the row. This is the release/nightly full refresh.profile=baseline-ci: select only deterministic rows inherited frombaseline-core; provider-backed rows and internal/external provider egress are rejected at selection time. Ordinary dependency downloads remain valid workflow network access.- All named baseline profiles run selected rows or record explicit blocked
evidence; their rows are not converted to
skipped_by_budget.
Baseline prior policy is explicit per row. Prior consumers use
prior_policy=required and must consume a valid canonical or explicitly bound
prior. Map-build producers and unrelated contract rows use
prior_policy=not_applicable. No-prior controls are separate suites and are
never a baseline consumer result.
- Live trials do not retry by default. Set
live_retry_limit=<N>only when the evaluation contract explicitly calls for audited fresh-directory retries. execute budget=smoke: deterministic confidence only; selected expensive or live rows are recorded as skipped by user budget inprofile=adaptive.execute budget=focused: default maintainer mode; selected required live rows must run or record explicit blocked evidence.execute budget=full: run required and recommended selected rows unless environment, network, provider, hardware, or guard preflight blocks them.
Never downgrade a selected live-agent eval into deterministic-only success.
Missing provider keys, provider 5xx/429, and model-service failures are
model_or_provider_unavailable. Missing simulator/runtime, DINO sidecar,
Python env, or live-session capacity is environment_blocked.
Outputs
Each run writes:
output/eval-harness/<stamp>/
eval_harness.json
eval_harness.md
rows/<row-id>/
evals/<suite-id>/<stamp>/The manifest schema is roboclaws_eval_harness_manifest_v1. Rows use
roboclaws_eval_harness_row_v1 and may be deterministic_gate,
product_run, eval_suite, live_agent_eval, regression_promotion, or
manual_review. Provider rows also carry a fail-closed
provider_network_scope and allowed_execution_targets contract. All current
provider routes execute locally; external routes remain restricted to local
execution by the same contract.
Selection Rules
The selector is deterministic and rule-table based over the row catalog, plan
text, git diff paths, and explicit overrides. It does not use an LLM
classifier. Row policy lives in this skill and catalog/rows.json; Python
scripts only load rows, expand paths/profiles, select, execute, and write
manifests/reports.
Important signals:
- Eval harness, eval CLI, eval reports, or regression promotion select eval
unit tests and
smoke_regression. - Runtime Metric Map, map-build, actionability, or waypoint files select
map_build_quality; provider consumer rows usemap_consumer_fixed_prioronly when an explicit canonicalruntime_map_prioris available. - Cleanup skill, prompt, MCP policy, checker, or done-readiness files select
cleanup contract gates,
cleanup_capability, and focused/full live eval rows. - Agent SDK, provider profile, or live-runtime files select route/preflight checks and affected live-agent eval rows.
- Visual grounding, DINO, camera labeler, or RAW-FPV files select perception or camera product rows.
- Docs-only command taxonomy or skill guidance changes should select docs and route checks, with eval rows only when the docs claim behavior changed.
Do not use or recreate a user-facing agent-validation-matrix route. Historical
plans may mention it, but maintained guidance should point at @eval-harness
and just agent::eval recommend|execute|suite|promote-regression.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

