gaia-research/gaia-skill-tree / .agents/skills/gaia-ingest-batch
gaia-ingest-batch
VerifiedBatch wrapper for /gaia-ingest. Ingests a bounded set of already-verified evidence rows through CLI-only writes, uses --no-build on every row, appraises Trust Magnitude for every affected named skill, then runs exactly one build and validation pass. Use for an L4-approved intake after /ev-pipeline; benchmark-result rows also require a Phase 2B report and explicit human gate approval.
Gaia Ingest Batch
This is a coordinator, not a second evidence-ingestion implementation. Every
row follows the contract in /gaia-ingest; this skill only sequences verified
rows efficiently and finalizes the resulting registry artifacts.
Input manifest
Prepare a reviewed manifest with one row per source:
rows:
- skill: firecrawl/web-scrape-integration
source: https://www.youtube.com/watch?v=...
evidenceType: social-signal
payload:
views: 8510
sourceStartedAt: 2025-07-20
notes: "Third-party tutorial explicitly demonstrates page scraping."
The manifest must state a source URL, Evidence Type, source-start date,
verifiable numeric payload, factual notes, and attribution scope for every row
(see docs/agents/curation-authority-map.md).
Exclude any deferred candidate. Never infer an Evidence Type or a metric from a
summary. Under #2473, both first-party and third-party social-signal rows
demonstrating the target skill are eligible immediately (sameAsAuthor = 1.0,
publishCooldownDays = 0 — no 30-day hold), subject to target-skill relevance,
provenance (creatorRelation, relevanceNote), views >= 1000, (type, url)
dedup, and the 3-row plateau; proxy-containment strictly requires an external,
non-first-party repository (externalStars >= 10000); and synthetic
self-attestation rows must never be added to clear the 49.9 TM suite-component
shared-repository cap. For benchmark-result, attach the Phase 2B benchmark-source report and
human approval for the lane: verified rows need CI/verifier attestation plus
runAt, datasetHash, and benchmarkInputHash; reported rows may be public
claims or mirrored benchmark evidence approved by the human gate and do not need
those reproducibility fields. rejected, pending, candidate, retired, or
unknown benchmark sources/rows must not enter ingestion as scoring rows. A
catalog status: rejected is the blacklist. appliesToGenericSkillRefs is
catalog metadata only; it does not create a named score without a named
benchmark-result row.
Procedure
-
Verify
/ev-pipelinecompleted for the manifest’s sources and link health is recorded. Reject dead, unverified, duplicate, or scope-mismatched rows. Forbenchmark-result, require Phase 2B + Phase 3 + Phase 4 completion and explicit human gate approval before any row is ingested. -
For each row, invoke the
/gaia-ingestcontract and execute its exactgaia dev evidence ... --no-buildcommand. Process one row at a time and stop on the first CLI preflight or source-verification failure. -
Appraise each affected skill after its final row:
PYTHONPATH=src python3 scripts/trust_appraise.py --skill <contributor/skill-id> -
Present proposed calibrations. Do not calibrate without explicit operator approval. If approval is already recorded, run each approved calibration with
--no-build. -
Hand off the branch-close to
/gaia-review-meta-close. Do not run the build/validate/stage/PR steps here — that skill owns the single build, the calibration+Origin gate, suite wiring viagaia dev fuse(sosuiteComponentssurvives the build), upstream-naming correction, the LF-renormalized artifact allowlist (dropping CRLF churn and blocking leaks), the UTF-8-safe validate, and the PR. Pass it the branch, the affectedcontributorhandles (for badge/og staging), the per-skill appraised TM/grade from step 3, and the intake issues toResolves. This skill stops at "evidence ingested + appraised."
Output
Report, for every row: CLI command, source verdict, Evidence Type, row grade,
TM contribution, and duplicate/scope decision. Report, for every skill: final
TM, Overall Trust Grade, current level, and any calibration proposal. Then hand
these facts to /gaia-review-meta-close for the gated close-out.
Route suite creation only after components are ingested and appraised — the
capstone/suiteComponents wiring happens inside /gaia-review-meta-close
(gaia dev fuse), or via /gaia-fuse-full-suite for a standalone suite build.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |