菜单
Publish a new post (announcement, link, or LaTeX-style meta report) to the Gaia site. Use when you want to add any update to the registry's public feed and landing page.
用 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-post |
| description | Publish a new post (announcement, link, or LaTeX-style meta report) to the Gaia site. Use when you want to add any update to the registry's public feed and landing page. |
Publish a post to the Gaia registry site. Posts appear in the path-meta-queue on the landing page and, for reports, also update the hero notification badge. All post data is tracked in docs/meta/posts.json (newest-first) and docs/index.html is patched programmatically — no hand-editing HTML.
| Type | When to use | Requires |
|---|---|---|
announcement | Registry news, version releases, policy changes | title, summary |
link | External article, RFC, or resource worth surfacing | title, summary, --url |
report | Formal audit or meta-shift (LaTeX-style HTML rendered from Markdown) | title, summary, --source |
# Announcement
python scripts/add_post.py announcement "Title" "Short summary." [--label "Release"] [--date YYYY-MM-DD]
# External link
python scripts/add_post.py link "Title" "Short summary." --url https://... [--label "Link"] [--date YYYY-MM-DD]
# Meta report (renders HTML from a Markdown source file)
python scripts/add_post.py report "Title" "Short summary." \
--source docs/meta/MY_REPORT.md \
[--author "Name, Role"] \
[--label "Audit"] \
[--date YYYY-MM-DD] \
[--chart reports/YYYY-MM-DD-chart-data.json] \
[--hero | --no-hero]
--hero / --no-hero: controls whether the floating hero notification badge in the landing page is updated to point to this post. Defaults to yes for report type, no for others.
Create docs/meta/YYYY-MM-TITLE.md. Use YAML frontmatter for metadata the script needs:
---
title: "Registry Audit Report: Descriptive Title"
author: "Marcus Rafael Tiongson, Auditor"
summary: One sentence for the queue card.
abstract: |
Optional longer abstract paragraph. If omitted, `summary` is used.
label: Latest Audit
---
## Abstract
Extended abstract text (rendered in the paper body as an indented italic block).
## Executive Summary
Paragraph text here.
### Sub-section
More detail.
## Findings
Tables and lists work:
| Column A | Column B |
|----------|----------|
| value | value |
- Bullet one
- Bullet two
## References
[1] Author. (Year). *Title*. Publisher.
[2] Another reference.
Supported inline Markdown: **bold**, *italic*, `code`, [text](url), fenced code blocks.
python scripts/add_post.py report "Title" "Queue summary." \
--source docs/meta/YYYY-MM-TITLE.md
The script will:
docs/meta/reports/YYYY-MM-DD-slug.html using the embedded LaTeX-style academic template.docs/meta/posts.json.<!-- gaia-posts-start / end --> zone in docs/index.html (up to 3 most recent posts shown).<!-- gaia-hero-post-start / end --> zone (hero badge) to point to the new report.If you have a JSON data file for a timeline chart, pass it:
python scripts/add_post.py report "Title" "Summary." \
--source docs/meta/MY_REPORT.md \
--chart reports/my-chart-data.json
The JSON format mirrors may-2026-timeline.json:
{
"labels": ["2026-05-01", "2026-05-15", "2026-05-25"],
"datasets": [
{ "label": "1★", "color": "#94a3b8", "data": [40, 45, 50] },
{ "label": "6★", "color": "#f59e0b", "data": [1, 1, 1] }
]
}
git add docs/meta/posts.json docs/meta/reports/ docs/index.html
git commit -m "post: add <type> — <title> [skip-gen]"
Gaia Research as the default report author unless the user explicitly requests a different byline.CONTEXT.md (apex tier, Atomic Basics, card, etc.).## (rendered with auto-numbered LaTeX counter). Use ### for subsections.## Abstract section in the Markdown body is rendered as the indented italic abstract block in the paper; do not repeat it under a different heading.## References section receives special .ref-item treatment — each [N] ... line becomes a hanging-indent reference entry.docs/meta/reports/ alongside their HTML output.python scripts/add_post.py report \
"June 2026 Integrity Audit" \
"DAG validation and evidence liveness sweep across 220 skills." \
--source docs/meta/JUN_2026_AUDIT.md \
--label "Audit" \
--author "Marcus Rafael Tiongson, Auditor"