跳到正文
cccskills
免费在 GitHub 公开

evidence-verification-pipeline

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 the evidence phases end-to-end: collecting raw evidence from the data lake, verifying live GitHub star counts, running Phase 2B benchmark-source verification, 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.

中文简介正在准备中。当前显示原文说明。

集成工具GitHub

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md3.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Evidence Verification Pipeline

Alias entry point for /ev-pipeline. It operates on the evidence/ data lake only and does not mutate registry files.

Type-First Evidence Lake Contract (#1148)

The evidence lake is type-first. The primary working set for every phase is evidence/by-type/<canonical-evidence-type>.md. Legacy evidence/tier_*.md files may still exist as coexistence artifacts for older tooling, but they are not the semantic routing key.

Phase Responsibilities

  • Phase 0 — ev-discovery (skippable): searches for new Stage-2 evidence on declared need and appends discovered rows into source inputs for Phase 1.
  • Phase 1 — ev-collection: materializes/compiles by type. evidence/by-type/<type>.md is primary; tier_*.md is coexistence-only.
  • Phase 2 — ev-star-verification: verifies live GitHub stars without repartitioning by rank.
  • Phase 2B — ev-benchmark-verification: verifies benchmark-result rows and candidate manifests against registry/benchmark-sources.json; unknown/candidate/registered/mirrored/incomplete sources do not score. Registered sources may declare appliesToGenericSkillRefs for generic capability applicability, but that metadata is non-scoring until a named benchmark-result row satisfies reproducibility and approved provenance.
  • Phase 3 — ev-adversarial-audit: audits the by-type files, including benchmark catalog misuse and vendor-claim leakage.
  • Phase 4 — ev-link-validation: validates URLs. validate_sources.py remains a temporary coexistence URL-health shim.

Generated evidence outputs are review artifacts. Do not commit generated by-type files, tier files, source reports, validation reports, unified lake files, seeds, collector rows, or benchmark candidate manifests without a human gate. After Phase 2B + Phase 3 + Phase 4, humans must approve any benchmark catalog promotion or /gaia-ingest-batch; machines classify, humans promote. A registered benchmark source is generic-applicable catalog metadata only: no named-skill score, Trust Magnitude contribution, or scoring evidence row exists until a named benchmark-result row satisfies reproducibility and approved provenance.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 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月24日 更新

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月24日 更新

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月24日 更新

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月24日 更新

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月24日 更新

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月24日 更新

查看 gaia-research 的全部技能

报告此技能的问题