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

trust-appraise

Dry-run Trust Magnitude for proposed named skills or suites before curation. Use when deciding whether a proposed suite deserves A/S treatment, when checking Fusion Score structural inputs, when comparing repo stars vs suite component counts, or when asked to appraise a candidate before adding it to the registry.

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

gaia-research/gaia-skill-tree
설치 방법 보기

포함된 파일(1)

  • SKILL.md4.1 KB

SKILL.md(원문)

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

/trust-appraise

Runs a non-mutating Trust Magnitude dry run. Formulas, dedup, inheritance, grade floors and star gates are not restated here. The canonical source is docs/agents/curation-authority-map.md, which is checked against src/gaia_cli/trustMagnitude.py by tests/test_curation_authority_map.py.

Two modes:

  1. Registry mode (--skill) appraises an already-curated skill. A contributor/skill id reads registry/named/<contributor>/<skill>.md and resolves its genericSkillRef against registry/nodes/. A bare id reads the generic node. Use it during L4 human review to see the real TM and per-row artifact scores before signing off.
  2. Proposal mode (--repo) appraises a proposed suite from live GitHub signals before curation. It is the pre-curation companion to /trust-appraise-all.

Usage

# Appraise one or more curated skills (use during L4 human review)
PYTHONPATH=src python3 scripts/trust_appraise.py \
  --skill rico-favor/implement-with-discernment \
  --skill caioribeiroclw-pixel/evidence-attestation

# Appraise a proposed suite (pre-curation)
PYTHONPATH=src python3 scripts/trust_appraise.py \
  --repo gsd-build/get-shit-done \
  --components 5 \
  --evidence-path docs/INVENTORY.md

# Default suite appraisal set
PYTHONPATH=src python3 scripts/trust_appraise.py

# Machine-readable output
PYTHONPATH=src python3 scripts/trust_appraise.py --skill foo/bar --json

Scope labels: always report them

Every result carries scope, genericResolution and totalStatus (authority map §2):

ModescopegenericResolutiontotalStatus
--repo proposalnamed-own/proposalnot evaluatedpartial
--skill named, generic ref resolveseffective namedresolvedfinal
--skill named, generic ref missing from the registrynamed-ownnot evaluatedpartial
--skill named with no genericSkillRefeffective namednot applicablefinal
--skill generic nodegenericnot applicablefinal

A partial total is never the effective named TM. Say "generic: not evaluated", not "inheritance disallowed". Generic-layer evidence that a skill later inherits still counts, even when it does not prove implementation usage.

Proposal-mode metrics and their status

The proposal builds a temporary skill from its own rows only:

  • github-stars-own at the evidence blob URL
  • repo-own at the repository root
  • a structural fusion-recipe row, which scores 0 TM and feeds only the informational Fusion Score

skillCountInRepo is recorded and never divides a score. Each collected metric is reported in metricClaims with a verified / reported / inferred / unknown status and its repro command (authority map §5):

  • contributorContributionSum is the sum of GitHub per-contributor contributions. It is not a count of unique commits. The engine's repo-own input field is named commits, so the proposal fills that input from the sum and labels it inferred. Never report it as "N commits".
  • Repository metrics describe the whole repository. Skill-file installability (a verified links.github blob/ URL) is a separate check.

Important caveat

A high dry-run score is not promotion approval. Use this skill to surface evidence quality and TM bias before L4 human review, never to bypass review. arxiv rows with 0 citations score 0 TM whatever their trustNumber. social-signal rows need verifiable view counts, and fabricated numbers inflate scores directly. 4★ strictly requires grade A (TM ≥ 100), and grade S (5★) needs an independent witness. Both rules are in authority map §3.

리뷰

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

댓글

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

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

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. 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월 22일 업데이트

design-gate

무료

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월 22일 업데이트

design-iteration

무료

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월 22일 업데이트

dev-calibrate

무료

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월 22일 업데이트

epic-close

무료

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월 22일 업데이트

ev-adversarial-audit

무료

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월 22일 업데이트

gaia-research의 스킬 모두 보기

이 스킬의 문제 신고