Skip to content
cccskills
FreePublished on GitHub

gaia-ingest

Atomically ingest one already-verified evidence row into one named Gaia skill using the CLI, then appraise Trust Magnitude and propose—never silently apply—a calibration. Use after /ev-pipeline has verified an approved intake source, or whenever a curator says "ingest evidence", "add verified evidence", "gaia-ingest", or "turn this source into registry evidence".

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

gaia-research/gaia-skill-tree
Works withGitHub

Run score Not tested

See how to install

Files included (1)

  • SKILL.md4.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Gaia Ingest

Safely turn one verified evidence source into one CLI-authored evidence row. This is the mutation bridge after evidence verification; it is not discovery, source research, or a bulk importer.

Required inputs

  • Named skill ID: contributor/skill-id
  • Source URL verified by /ev-pipeline link validation
  • Evidence Type and only the numeric payload that type supports
  • Attribution scope: named, generic, or suite
  • Factual notes describing exactly what the source proves

Refuse the write when any input is absent, the source is dead, the evidence belongs to a different capability, or the requested payload would be guessed.

Preflight

  1. Confirm the named skill exists and inspect its current rows:

    gaia dev list --named --json
sed -n '1,120p' registry/named/<contributor>/<skill-id>.md

  2. Confirm the source was verified by the current evidence run. For GitHub, also fetch live facts with gh api; for social sources, scrape the source and preserve its public view count; for benchmarks, require the complete reproducibility payload.

  3. Reject duplicate (Evidence Type, canonical source URL) rows. Do not use a suite-wide source as full-strength component evidence. A component must have implementation-specific proof; suite-wide proof belongs on the suite capstone or is recorded as scoped supplemental context.

  4. Choose only a schema-supported Evidence Type. Never use the obsolete --class flag. Use gaia dev evidence --help if the payload is unclear.

CLI-only mutation

Run exactly one command for the one evidence row. Always use --no-build; callers such as /gaia-ingest-batch perform the single final build.

GAIA_OPERATOR_OVERRIDE=1 gaia dev evidence <contributor/skill-id> "<source-url>" \
  --type <evidence-type> <supported-numeric-flags> \
  --notes "<factual scope and verification note>" \
  --source-started-at YYYY-MM-DD \
  --no-build

Payload examples:

# Public third-party video; views must be visible on the scraped source.
gaia dev evidence firecrawl/web-scrape-integration "https://www.youtube.com/watch?v=..." \
  --type social-signal --views 8510 \
  --notes "Third-party tutorial explicitly demonstrates Firecrawl page scraping." \
  --source-started-at 2025-07-20 --no-build

# Concrete upstream skill file; use a blob URL, live star count, and real
# number of skills sharing the repository.
gaia dev evidence firecrawl/web-scrape-integration "https://github.com/firecrawl/skills/blob/main/skills/firecrawl-build-scrape/SKILL.md" \
  --type github-stars-own --stars 42 --skill-count-in-repo 5 \
  --notes "Official upstream implementation source; star count verified via GitHub API." \
  --source-started-at 2026-04-08 --no-build

For benchmark-result, provide every reproducibility flag required by gaia dev evidence --help; never convert a vendor benchmark claim into a percentile without an independently verifiable benchmark source.

Appraise, then stop

After the write:

PYTHONPATH=src python3 scripts/trust_appraise.py --skill <contributor/skill-id>

Report the new TM, Overall Trust Grade, per-row score, and whether the source is implementation-specific. Propose a calibration only when Trust Magnitude clears the gate and the Star Bar is met (the per-star Evidence Floor is retired under Yggdrasil II — TM is the sole promotion gate). Do not run gaia dev calibrate without explicit operator approval.

Finalization

For a one-row standalone run, validate without regenerating unrelated artifacts:

GAIA_OPERATOR_OVERRIDE=1 gaia dev validate

For multiple rows, hand back to /gaia-ingest-batch, which performs exactly one gaia dev build and final validation.

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

ci-churn

Free

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 24, 2026

design-gate

Free

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 24, 2026

design-iteration

Free

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 24, 2026

dev-calibrate

Free

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 24, 2026

epic-close

Free

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 24, 2026

ev-adversarial-audit

Free

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 24, 2026

See all skills by gaia-research

Report a problem with this skill