본문으로 건너뛰기
cccskills
무료GitHub에 공개

gaia-post

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md4.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Gaia Post

Publish a post to the Gaia Skill Tree 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.

Post Types

TypeWhen to useRequires
announcementRegistry news, version releases, policy changestitle, summary
linkExternal article, RFC, or resource worth surfacingtitle, summary, --url
reportFormal audit or meta-shift (LaTeX-style HTML rendered from Markdown)title, summary, --source

Usage

# 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.

Step-by-Step: Adding a Meta Report

Step 1 — Write the Markdown source

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.

Step 2 — Run the script

python scripts/add_post.py report "Title" "Queue summary." \
  --source docs/meta/YYYY-MM-TITLE.md

The script will:

  1. Parse the frontmatter and Markdown body.
  2. Render docs/meta/reports/YYYY-MM-DD-slug.html using the embedded LaTeX-style academic template.
  3. Prepend the new post to docs/meta/posts.json.
  4. Patch the <!-- gaia-posts-start / end --> zone in docs/index.html (up to 3 most recent posts shown).
  5. Patch the <!-- gaia-hero-post-start / end --> zone (hero badge) to point to the new report.

Step 3 — (Optional) Add Chart.js timeline data

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] }
  ]
}

Step 4 — Commit

git add docs/meta/posts.json docs/meta/reports/ docs/index.html
git commit -m "post: add <type> — <title> [skip-gen]"

Constraints

  • Use Gaia Research as the default report author unless the user explicitly requests a different byline.
  • Avoid banned vocabulary from CONTEXT.md (apex tier, Atomic Basics, card, etc.).
  • All section headings in report Markdown should use ## (rendered with auto-numbered LaTeX counter). Use ### for subsections.
  • The ## 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.
  • The ## References section receives special .ref-item treatment — each [N] ... line becomes a hanging-indent reference entry.
  • Chart data files live in docs/meta/reports/ alongside their HTML output.

Example

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"

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

ci-churn

무료

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

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".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gaia-research/gaia-skill-tree232026년 10월 17일 업데이트

gaia-research의 스킬 모두 보기

이 스킬의 문제 신고