Skip to content
cccskills
FreePublished on GitHub

ev-scout

Broad, pre-curation evidence reconnaissance for a declared Gaia skill, intake batch, upstream repository, or proposed generic capability. Run before choosing a discovery strategy or mapping topology, to give the curator independent research leads and counterevidence. Context only: never scores, grades, ratifies, ingests, or mutates the registry. Later ev-discovery and ev-pipeline phases validate/promote any selected leads.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md4.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

ev-scout — breadth-first pre-curation context

Run before Phase 1 of /gaia-full-pipeline, including an already-submitted gaia push batch (Strategy F). May also run standalone, before L4 mapping. This is a lightweight read/search pass, not the later /ev-discovery Phase 0 nor a substitute for /ev-pipeline. Scouting is deliberately permissive; downstream verification and /ev-adversarial-audit are deliberately skeptical.

Inputs

Use the declared skill URL(s), upstream SKILL.md or repository, intake issue, and proposed generic concepts (if available). Keep multiple skills in a batch distinct, especially for named-only evidence. Do not require an L4-approved generic mapping: report tentative alternatives when topology is unresolved.

Search widely, without grading

Explore several search angles and independent source families:

  1. Generic capability: peer-reviewed papers, preprints, evaluations, general benchmark methodologies, foundational approaches, rival systems, and criticism or failure modes.
  2. Named implementation: source repo, specific SKILL.md blobs, releases, tests, CI/reproduction claims, independently authored reviews, reported use, security findings, adoption or reproducible demonstrations.
  3. Comparison: alternative architectures and negative findings that could falsify claimed benefits. Prefer disconfirming evidence when the first results are uniformly promotional.
  4. Evaluation opportunities: candidate benchmark IDs, public methodology, datasets, harnesses and missing reproducibility details. A vendor claim is never a verified benchmark-result.

Try broad and narrow queries; sample independent sources rather than repeatedly searching the same host. Favor diversity of useful leads over an illusion of completeness. Do not discard a relevant lead just because it may later fail. Do not turn mere topic relevance into implementation-specific proof.

Use available search and repository-read tools. If Firecrawl is available, follow /ev-discovery's authentication/preflight and quoting conventions. If not, use other available read/search tools, or report search limitations. Absence of search is not a curation blocker: return a clearly incomplete packet.

Output: scout packet

Produce a Markdown packet in the handoff or at generated-output/ev-scout/<intake-or-slug>.md when a persistent file is needed. Include:

  • target skill(s), upstream URL(s), date, searched queries/source families, tools used or unavailable, and mapping status (tentative or ratified);
  • a table of leads, with URL, title/publisher, publication date if known, possible canonical Gaia evidence type, generic/named/benchmark-catalog scope, what it might substantiate, and what a verifier must still confirm;
  • a separate counterevidence and competing approaches section;
  • likely evaluation benchmarks as benchmark-source candidates only, including proposed generic applicability and missing reproducibility fields;
  • a short mapping-relevant synthesis that distinguishes architecture from demonstrated performance and marks uncertainty explicitly;
  • suggested verification priorities and handoff to /ev-discovery, /ev-pipeline, and /gaia-ingest-batch after their normal human gates.

Use "candidate", "possible", or "unverified" until evidence is checked. Never fabricate publication dates, citations, percentile values, peer-review status, scores, or external adoption. Mark unavailable facts unknown.

Non-authority and handoff

No registry mutations, evidence-lake edits, GitHub approval labels, L4 ratification, star grades, Trust Magnitude, or automatic evidence ingestion. This packet informs /gaia-draft-curate, /gaia-curate[-chain/-dynamic], and the human L4 review; it does not override their workflows.

Later /ev-discovery can investigate selected Stage-2 leads; /ev-collection normalizes typed candidate rows; /ev-benchmark-verification and /ev-adversarial-audit challenge them; /ev-link-validation checks links; human review and canonical Gaia CLI ingestion remain authoritative.

If a recent scout packet for this exact source exists, reuse and refresh it rather than rescouting blindly. Record any new material or limitations.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Measure CI churn cost for a pull request: how many commits and how many CI-compute seconds were burned on avoidable "fix the CI" push rounds. Use when you want to understand the efficiency cost of a PR's iteration cycle, get actionable pre-push check suggestions, or include a churn summary in a pipeline report. Triggers: "ci churn", "how much CI did we burn", "avoidable commits", "ci efficiency", "wasted CI time", "churn report", "/ci-churn". Called automatically by /fp-drift at pipeline close.

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 17, 2026

Produce the rendered evidence a human-gated frontend PR owes its reviewer: capture each changed surface (plus the before state for anything modified, plus mobile width), then generate one self-contained local HTML page the founder can open and review without checking anything out. Use when a PR is gated by the "Frontend changes are HUMAN-GATED" section of CLAUDE.md, or when the user says "/design-gate", "screenshot evidence for this PR", "prep this for founder review", "build the design evidence page", "what does this look like before and after". The page comes from a template script, not hand-written markup. Output is session-local and never committed. Do NOT use for non-gated changes: typo/grammar/factual fixes in an unchanged block, dead link targets, alt/ARIA fixes with no visual change, cache-bust bumps, or refactors with no rendered diff.

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 17, 2026

One-fix-at-a-time, approval-gated design fix recovery. Given a checklist of fixes (handover doc, CHECKLIST.md, or inline list), applies each individually, presents a diff, and waits for an explicit APPROVE / REJECT / NO CHANGES decision before committing. Trigger phrases: /design-iteration, "go through the checklist one by one", "fix these one at a time", "bucket recovery", "design fix pass".

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 17, 2026

Playbook for correcting a named skill's star level to match its computed Trust Magnitude grade, with an independent post-calibration verification pass and a CLI-logged timeline event (never hand-written). Use when: recalibrating a skill's level, fixing a stale or drifted star rating, running a batch of `gaia dev calibrate` corrections, or confirming a past calibration actually landed. Triggers: "calibrate <skill>", "recalibrate the trust magnitude backlog", "promote/demote <skill> to N stars", "why is <skill> still N stars", "verify a calibration actually landed", "Hall of Heroes ranking is wrong".

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 17, 2026

Close out a completed EPIC / sprint end-to-end: author a fact-verified meta-post announcing what shipped, archive the EPIC's handovers, snapshot orchestrator memory, gate the integration→main merge on CI-green + explicit human go, drive the version bump (merge-commit conventions that auto-sync classifies), and verify the release reached the registry/PyPI. Use when the user says "close out EPIC <n>", "wrap up the sprint", "ship the meta shift", "/epic-close", or asks to finalize an integration branch that is ready to merge to main. Generalizes the EPIC 1002 (Yggdrasil II) close-out. This skill orchestrates — it authors founder docs directly (superadmin) and delegates code/regen to workers; it NEVER merges to main without the human gate.

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 17, 2026

Run this skill for Phase 3 of the evidence verification pipeline — the adversarial audit step. Use when you need to check the evidence data lake for bad data before ingestion: dead links, wrong URL formats (tree/ vs blob/), subjective wording ("elite", "high-quality"), stale migration notes, benchmark catalog misuse/vendor-claim leakage, or skills whose star evidence conflicts with classified evidence level. Triggers on phrases like: "audit the data lake", "adversarial check", "ev-adversarial-audit", "check for noise in evidence", "flag bad evidence", "run the audit phase", "quality check the by-type files", or any reference to Phase 3 of the pipeline.

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 17, 2026

See all skills by gaia-research

Report a problem with this skill