Discovery-only Gaia curation for one manually selected source page. Fetches and normalizes up to five real SKILL.md candidates, deduplicates and maps them for human L4 review, then stops without evidence scoring or registry mutation.
Scanned 9/12/2026
Install to Claude Code
npx -y skills add gaia-research/gaia-skill-tree --skill gaia-curate --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Gaia Curate?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gaia-research-gaia-curate-gaia-skill-tree)More formats (shields.io, HTML) on the badges page.
---
name: gaia-curate
description: >-
Discovery-only Gaia curation for one manually selected source page. Fetches and
normalizes up to five real SKILL.md candidates, deduplicates and maps them for
human L4 review, then stops without evidence scoring or registry mutation.
version: 2.0.0
argument-hint: "<source-page-url>"
---
# Gaia Curate
Read [CURATION-CORE.md](CURATION-CORE.md). This skill is discovery-only and processes one manually selected source page with at most five candidates.
1. Fetch the page and record its canonical URL, retrieval time, source lane, and source-native trend signals. Do not treat popularity as trust.
2. For each candidate, fetch a real upstream `SKILL.md`. Reject/defer a listing that cannot resolve to one. Parse non-empty `name` and `description` frontmatter; preserve host repository, cited origin/attribution, commit SHA when available, and SHA-256 content hash.
3. Normalize one candidate, exact-dedupe by canonical URL/content hash, then persist the complete JSON output of `gaia dev list --generic --json` before worker dispatch. Preserve it in the generic snapshot receipt; every mapping option must appear in the same separately supplied snapshot. Offer at most three mapping options plus the bounded `NEW_GENERIC` and `UNSURE` paths; `UNSURE` is recorded as `DEFER`.
4. Emit one `discovery-packet-v2` decision using `MAP`, `NEW_GENERIC`, `DUPLICATE`, `NOT_A_SKILL`, or `DEFER`, and validate it with [scripts/validate_discovery_packet.py](scripts/validate_discovery_packet.py) plus `--generic-snapshot <saved-cli-output.json>`. A `DUPLICATE` must repeat the candidate's canonical URL or content hash exactly. Use Yggdrasil II `basic|fusion` only for an L4-reviewable proposal; do not ask workers for legacy branches or stars. The validator retains v1 read compatibility, but v1 is not normative for new output.
5. Write the validated V2 packet to `registry-for-review/discovery-packets/`, present the L4 human shortlist, and stop. A shortlist is not registry acceptance. Only after L4 may the human append the schema-defined `l4Resolution` (vendor-neutral generic identity, named identity, and exact upstream `blob/.../SKILL.md` URL) and hand the resolved packet to `gaia push --from-file <packet.json>`. Never infer those fields from a candidate slug or listing URL.
Never gather or score evidence, assign manual grades/classes, calculate TM, calibrate stars, mutate registry files, regenerate docs, commit, push, or open a PR.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!