Skip to content
cccskills
FreePublished on GitHub

gaia-consult

Reference guide for the full manual Gaia curation pipeline. Invoke at any phase when unsure what command to type next: gaia-curate, L4 review, gaia push, ev-pipeline (Phases 0–4), gaia-ingest, or close. Trigger phrases: "/gaia-consult", "what's the command for", "remind me how to", "I'm lost in the pipeline", "what do I do next", "consult the pipeline doc", "pipeline reference".

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

Run score Not tested

See how to install

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

gaia-consult

This is a lookup skill — it points you at the canonical pipeline reference document and tells you which section covers the phase you're in. Read the section. Type the command. Do not guess.

Reference document

docs/en/manual-curation-pipeline.html

Open it in any browser. It is self-contained, offline-capable, and covers every phase with exact typed commands.

Phase → section map

You are in…Jump to section in the doc
You want to automate everything from a URL/gaia-quick-curate — not this doc
Discovering a skill, running prefill, writing the packetPhase 1 — gaia-curate
Reviewing the packet, ratifying with gaia dev ratifyPhase 2 — L4 Review
Running gaia push, branching, opening the draft PRPhase 3 — gaia push → PR
Running the evidence lake phases (0–4)Phase 4 — ev-pipeline
Writing evidence rows, appraising TM, calibrating starsPhase 5 — gaia-ingest
Merging the PR, posting comments, closing the issuePhase 6 — Close
Any command failing unexpectedlyCommon errors section at the bottom
Need every command in one placeQuick-reference cheat sheet at the bottom

When to invoke this skill

  • You are at any phase of the pipeline and are unsure of the next command.
  • A command failed and you want to check the expected invocation.
  • You want to confirm a flag, a file path, or a decision-rule before proceeding.
  • You are about to mutate the registry (gaia dev evidence, gaia dev calibrate, gaia dev fuse) and want to double-check the exact invocation.

Suite curation detour

If the intake is for a suite capstone (a contributor with 3+ named skills being fused), the pipeline has an additional step between Phase 5 (ingest) and Phase 6 (close). Before closing:

  1. Confirm all component named skills are already in the registry at their correct rank.
  2. Run /gaia-fuse-full-suite — this adds the fusion node, suite manifest, derivatives back-links, and fuse timeline event.
  3. Validate: GAIA_OPERATOR_OVERRIDE=1 gaia dev validate
  4. Then proceed to Phase 6 (close) as normal.

Do not attempt to hand-write a fusion node — the CLI writes it with the correct type: fusion and timeline entry.

This skill does not…

  • Execute any commands itself.
  • Duplicate the pipeline documentation inline.
  • Replace reading the actual reference file.

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

See all skills by gaia-research

Report a problem with this skill