Skip to content
cccskills
FreePublished on GitHub

gaia-quick-curate

Inspect or exercise the paused gaia curate orchestration scaffold for one source URL. The command currently persists an INITIALIZED run ledger and reports status; its 25 named workflow states and transition methods are a design skeleton, not an implemented automated curation or merge pipeline. Use only for scaffold development, status inspection, or dry-run contract work. For live curation, use gaia-full-pipeline or gaia-consult. Trigger phrases: "/gaia-quick-curate", "inspect gaia curate", "curate scaffold", "quick curate status". For batch/multi-page runs use gaia-curate-dynamic; for crawler branches use gaia-bot-curate; for pending intake proposals use gaia-draft-curate.

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

See how to install

Files included (1)

  • SKILL.md4.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

gaia-quick-curate

gaia curate is currently a paused orchestration scaffold. It can create and persist a run ledger, reload one with --resume, and print status. A fresh run deliberately pauses at INITIALIZED; the transition methods beyond that point raise NotImplementedError and do not perform discovery, evidence verification, ingest, calibration, GitHub issue/PR work, or merging.

Do not describe this skill as an automated two-gate pipeline, claim that it will advance through all 25 states, or promise "one URL in, one merged PR out." The state names record the intended workflow shape only.

For an implemented, human-directed curation workflow, use /gaia-full-pipeline for phase routing or /gaia-consult for command guidance.

Current command surface

gaia curate <url> [--generic <id>] [--discover] [--dry-run]
gaia curate --resume <run-id> [--status]
InputCurrent behavior
<url>Creates a run ledger, pauses at INITIALIZED, and prints status.
--generic <id>Records a suggested generic ID; it does not apply a mapping.
--discoverRecords discovery intent; it does not run discovery yet.
--dry-runRecords dry-run intent; no curation transitions are implemented.
--resume <run-id>Loads an existing ledger by run ID.
--statusPrints the loaded or newly created run's status.

Run state is stored at:

.gaia/curation/runs/<run-id>/state.json

The ledger currently starts in INITIALIZED. Although src/gaia_cli/curation/state.py declares 25 intended state names, that list is not evidence that the workflow exists. SCAFFOLD_PAUSE_STATES in the orchestrator prevents a fresh run from entering the unimplemented transitions.

Safety and merge authority

The scaffold has no authority to mutate the registry or GitHub today. If its runtime is implemented later, all registry writes must still use the canonical Gaia CLI mutation path, approval gates must be explicit and resumable, and the final merge to main must remain founder-gated. This skill must never merge the final PR to main; a human founder makes that decision after reviewing the evidence, diff, and CI state.

Live source locations

ConcernPath
CLI command entrysrc/gaia_cli/commands/curate.py
Run ledger and 25-state design skeletonsrc/gaia_cli/curation/state.py
Pause guard and unimplemented transition stubssrc/gaia_cli/curation/orchestrator.py
URL-resolution helpersrc/gaia_cli/curation/url_resolver.py
Run state.gaia/curation/runs/<run-id>/state.json

There is no live src/gaia/curate/state_machine.py, gate UI, or control-panel comment renderer. Do not invent those paths or report future components as implemented.

When to use another skill

NeedUse
Implemented phase-by-phase curation/gaia-full-pipeline
Curation command/reference lookup/gaia-consult
Batch or multi-source discovery/gaia-curate-dynamic
Crawler bot/* branches/gaia-bot-curate
Pending intake proposals/gaia-draft-curate

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