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 tran

SKILL.md

GitHub

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]
Input Current 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.
--discover Records discovery intent; it does not run discovery yet.
--dry-run Records dry-run intent; no curation transitions are implemented.
--resume <run-id> Loads an existing ledger by run ID.
--status Prints 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

Concern Path
CLI command entry src/gaia_cli/commands/curate.py
Run ledger and 25-state design skeleton src/gaia_cli/curation/state.py
Pause guard and unimplemented transition stubs src/gaia_cli/curation/orchestrator.py
URL-resolution helper src/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

Need Use
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