メニュー
Triage and classify pending Gaia skill intake batches in registry-for-review/. Use for gaia push intake proposals, draft skill batches, and deciding whether proposals should proceed to canonical curation. This skill is read-only and never promotes skills itself.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Helper for release operations, compilation of changelogs between tags, version lockstep syncing, and promotion of GitHub releases from canary/pre-release to latest/production. Use when the user asks to "compile the changelog", "promote release to latest", "tag a release", or do version release operations.
Push committed changes and create a draft PR on GitHub. Use when you have staged changes ready to push and want to open a draft PR for early feedback or documentation.
Consult this skill BEFORE proposing a fix to any CLI gap or schema gap that touches evidence, trust magnitude, evidence types, evidence grades, the TM formula, or star-level promotion gates. Also read it whenever an issue mentions citations, stars, commits, contributors, views, reviewers, percentile, arxiv, github-stars-own, repo-own, social-signal, benchmark-result, peer-review, self-attestation, fusion-recipe, verifier-attestation, or proxy-containment — those are the 10 canonical evidence types and the raw inputs that feed their formulas. Also read it when asked whether a skill qualifies for a given star level (0★–6★): the Star Bar and promotion gates live in `META.md`, not in the TM methodology page. Reading both prevents proposing a calibration that satisfies the TM grade threshold but violates a Star Bar installability or link requirement.
Phase 4 of the Gaia evidence verification pipeline. Checks every URL in the evidence data lake for HTTP liveness — catches dead links (404, 403, timeout, connection errors) before evidence is ingested into the registry. Use this skill when: running the full /ev-pipeline, asked to "validate links", "check evidence URLs", "run link validation", "find dead links in the data lake", "check HTTP status of evidence sources", or "verify evidence links still work". Also useful standalone when you suspect evidence sources have gone stale after a long gap between pipeline runs. Wraps validate_sources.py, which uses Firecrawl CLI to scrape each unique URL and records pass/fail status in a markdown report. Requires Firecrawl CLI to be installed and authenticated.
Top-level orchestrator for the Gaia Registry evidence verification pipeline. Run this when you want to do a full evidence pass — collecting raw sources, verifying live GitHub star counts, adversarially auditing for quality/formatting issues, and checking that every URL is reachable — all in one coordinated sequence. Trigger phrases: "run the evidence pipeline", "full evidence pass", "verify evidence", "evidence verification pipeline", "run ev-pipeline", "check all evidence", "audit the data lake", "evidence quality sweep", "refresh evidence", "validate evidence sources". Also aliased as /evidence-verification-pipeline. Use the individual sub-skills (ev-collection, ev-star-verification, ev-adversarial-audit, ev-link-validation) only when you need to re-run one phase in isolation; for end-to-end work, always start here.
Canonical entry point for the full Gaia evidence verification pipeline. Invoke as /evidence-verification-pipeline or /ev-pipeline — both names trigger this skill. Use whenever you need to run all four evidence phases end-to-end: collecting raw evidence from the data lake, verifying live GitHub star counts, running adversarial auditing for noise and URL errors, and checking link health via Firecrawl. Also use when someone says "run the evidence pipeline", "verify the evidence lake", "audit evidence", "run ev-pipeline", "full evidence check", "pipeline run", "prepare evidence for ingestion", or "refresh the data lake". This is the pre-ingestion step — run it before importing any evidence into the registry.
| name | gaia-draft-curate |
| description | Triage and classify pending Gaia skill intake batches in registry-for-review/. Use for gaia push intake proposals, draft skill batches, and deciding whether proposals should proceed to canonical curation. This skill is read-only and never promotes skills itself. |
| version | 2.0.0 |
Review and classify pending skill proposals staged by gaia push. This is the intake decision gate between registry-for-review/ and canonical curation.
This skill owns only intake batches and their linked intake issues/PRs. It does not:
registry/, registry/gaia.json, or batch JSON files;/gaia-triage);/gaia-curation-review);/gaia-curate-chain or /gaia-curate).git status --short --branch
python3 scripts/validate_intake.py
If the working tree contains unrelated changes, report them and do not alter them. If intake validation fails, stop and report the malformed batch.
Inspect registry-for-review/skill-batches/*.json, excluding .gitkeep. Record for each batch:
batchId, generation time, source, and proposed items;knownSkills as informational context only.Never edit or rewrite an intake batch. These are immutable submission records.
Use GitHub CLI when authenticated:
gh issue list --state open --search 'label:draft-skills'
gh pr list --state open --label draft-skills --json number,title,headRefName,url
Match batchId in titles, bodies, or comments. Report:
If GitHub authentication is unavailable, state that limitation rather than guessing.
Use only facts present in the batch and verified canonical lookups. Do not invent evidence grades or impose repository-star/recency thresholds here; deep evidence research belongs to the downstream curation workflow.
| # | Proposed ID | Name | Type | Existing match | Supplied evidence | Open questions | Decision |
|---|---|---|---|---|---|---|---|
| 1 | skill-id | Skill name | basic/fusion | generic or none | URLs/artifacts | missing facts | pending |
Check for obvious canonical duplicates with read-only commands such as:
gaia dev list --generic --named
For each proposal, collect a rationale and, when applicable, the target canonical ID for a rename or duplicate decision.
Work one batch at a time. Valid decisions are:
accept — proceed to canonical curation;rename <new-id> — accept under a corrected ID;duplicate <existing-id> — already represented;needs-evidence — hold and state exactly what is missing;reject — decline with a reason.Every decision must include a short rationale. Do not silently discard proposals.
Summarize:
batchId and linked issue/PR;review/gaia-push/* for intake, review/meta/* for canonical changes).The packet may be saved as /tmp/gaia-draft-curate-<batchId>.md. Write a repository Markdown artifact only when explicitly requested. Never modify the source batch.
Ask whether to continue. By default, hand accepted items to /gaia-curate-chain for discovery-packet validation and L4 review only. After L4, preserve the batch and issue/PR links, route unresolved evidence to /ev-pipeline, and hand verified rows to a maintainer for the CLI-only meta shift. The chain does not mutate the registry or sync docs. Use /gaia-curate only when the user explicitly chooses the lower-overhead path for a low-risk batch.
The handoff must preserve the originating batch and issue/PR links. This skill itself does not run gaia dev add, gaia dev evidence, or any other mutating command.
Batches reviewed: N
Tracking links: N found, N missing
Decisions: N accepted, N renamed, N held, N duplicated, N rejected
Promotion triggered: no (or explicit downstream handoff and branch)
Validation: commands run and results