ev-benchmark-verification
Skill22 starsChanged 3 days agoLicence not identifiedView on GitHub
Phase 2B of the Gaia evidence verification pipeline. Verifies benchmark-result rows and benchmark-source candidates against registry/benchmark-sources.json before adversarial audit, link validation, catalog promotion, or ingestion. Use when running /ev-pipeline, checking benchmark-result evidence, reviewing benchmark-source candidates, or preparing benchmark rows for /gaia-ingest-batch.
In this repository171 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- founder/CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- ci-churnSkill
- design-gateSkill
- design-iterationSkill
- dev-calibrateSkill
- dev-ingest-namedSkill
- epic-closeSkill
- ev-adversarial-auditSkill
- ev-collectionSkill
- ev-discoverySkill
- evidence-verification-pipelineSkill
- ev-link-validationSkill
- ev-pipelineSkill
- ev-scoutSkill
- ev-star-verificationSkill
- feature-pipelineSkill
- firecrawlSkill
- fp-driftSkill
- fp-exploreSkill
- fp-implementSkill
- fp-iterateSkill
- fp-planSkill
- fp-reviewSkill
- fuseSkill
- gaia-auditSkill
- gaia-badge-provisionSkill
- gaia-bot-curateSkill
- gaia-consultSkill
- gaia-curate-chainSkill
- gaia-curate-dynamicSkill
- gaia-curateSkill
- gaia-curate-trendingSkill
- gaia-curation-reviewSkill
- gaia-docs-syncSkill
- gaia-draft-curateSkill
- gaia-frontierSkill
- gaia-full-pipelineSkill
- gaia-fuse-full-suiteSkill
- gaia-image-productionSkill
- gaia-ingest-batchSkill
- gaia-ingestSkill
- gaia-intake-closeSkill
- gaia-issue-resolverSkill
- gaia-meta-auditSkill
- gaia-meta-sweepSkill
- gaia-orchestratorSkill
- gaia-previewSkill
- gaia-quick-curateSkill
- gaia-releaseSkill
- gaia-review-meta-closeSkill
- gaia-steward-deskSkill
- gaia-steward-fullSkill
- gaia-steward-issue-hygieneSkill
- gaia-steward-landSkill
- gaia-steward-laneSkill
- gaia-steward-observeSkill
- gaia-steward-pr-maintenanceSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.

