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

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.

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

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.4 KB

SKILL.md(원문)

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

Adversarial Evidence Audit (ev-adversarial-audit)

Phase 3 audits the evidence lake from a Devil's Advocate perspective before URL health validation and ingestion.

Type-First Evidence Lake Contract (#1148)

The evidence lake is type-first. Audit evidence/by-type/<canonical-evidence-type>.md files. Legacy evidence/tier_*.md files may still exist as coexistence artifacts, but they are not the semantic routing key.

Audit Target

Split reviewer work across evidence/by-type/<type>.md files, not tier files. Suggested sharding:

  • Repo/adoption signals: repo-own, github-stars-own, social-signal
  • Technical proof: benchmark-result, arxiv, peer-review
  • Governance/proxy proof: proxy-containment, verifier-attestation
  • Composition/self proof: fusion-recipe, self-attestation

Findings to Flag

  • Dead or malformed URLs, including GitHub tree/ links where a blob/ source is required.
  • Subjective/evaluative wording not supported by the source.
  • Evidence type mismatches or legacy alias leakage.
  • Star evidence that conflicts with live verification notes from Phase 2.
  • Benchmark catalog misuse after Phase 2B: benchmark-result rows citing unknown, candidate, registered, rejected, or retired sources as if they score; vendor claims presented as reproducible benchmarks; scoring provenance on non-verified catalog entries; missing reproducibility fields or missing/dubious percentile values.
  • Stale migration notes that still treat tier_*.md as the semantic working set.
  • Multi-target peer-review packet misuse: wrong evidenceType, empty targets, invalid skillId, duplicate (source.url, skillId, evidenceType) rows, or forbidden strength/scoring fields (trustNumber, grade, class, tier, level, stars, rank).
  • Imposter over-purging & audit taxonomy conflation (RFC #1809): ensure legitimate early-stage, self-hosted, or installable: false skills (Tier 2 Packaging Gap, Tier 3 Under-Evidenced Stub) are not mislabeled as Tier 1 Malicious Imposters or flagged for deletion.

Append concise findings to the source report. Do not mutate registry files.

Optional Semantic Evidence Review Sidecar

An operator may optionally run the read-only Jev advisory runner to flag semantic anomalies in evidence rows (docs/agents/jev.md):

# Offline dry-run by default ($0 spend); add --live to query TypeSafe API
python scripts/jev_advisory.py --mode evidence --input <evidence-rows.json>

This output serves as review triage hints only. It never marks evidence rows verified, does not replace deterministic HTTP health or Phase 2B benchmark verification, does not touch Trust Magnitude scoring, and emits an actionable handoff to worker-luna on uncertainty.

리뷰

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

댓글

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

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

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

Phase 2B of the Gaia evidence verification pipeline. Verifies benchmark-result rows and benchmark-source candidates against registry/benchmark-sources.json before adversarial audit, link validation, catalog promotion, or ingestion. Use when running /ev-pipeline, checking benchmark-result evidence, reviewing benchmark-source candidates, or preparing benchmark rows for /gaia-ingest-batch.

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

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

gaia-research의 스킬 모두 보기

이 스킬의 문제 신고