cpt13-g/build-research-evidence / .agents/skills/venue-evidence-audit
venue-evidence-audit
VerifiedAudit recent high-relevance papers from a target venue to identify claim-relevant experimental evidence gaps after core P0 results exist. Use for venue completeness and reviewer-risk analysis; not for redefining the research question or running experiments.
Venue Evidence Audit
Run only when the Orchestrator authorizes the audit and P0 is substantially complete. Start with python tools/context_view.py show --role venue, then read referenced Claim-Evidence and gap artifacts. Read docs/PROTOCOLS.md, docs/ROLE_HANDOFFS.md, docs/CONTEXT_POLICY.md and docs/EVIDENCE_COMPLETION_PROTOCOL.md on a fresh context or changed hash. Reuse an existing dated source set only when its task, venue, freshness and coverage still fit; search further for changed expectations or unresolved gaps. Context savings never justify skipping relevant papers or negative evidence.
Analyze 5-10 recent, highly relevant papers, prioritizing same task, research question, method class, venue and recency. Record search date, sources, relevance, inclusion/exclusion reasons and uncertainty. Stop once core expectations, material gaps and high-ROI actions are stable; do not expand into a systematic review. Compare datasets, baselines, metrics, seed/statistical practice, ablations, sensitivity, robustness, generalization, efficiency, complexity, qualitative analysis and figure/table conventions.
Produce an Evidence Gap Matrix with current status, venue frequency, Claim relevance, reviewer risk, estimated cost, information gain and recommended priority. Recommendations do not enter the queue automatically. A common but Claim-irrelevant experiment is P3/SKIP. Do not alter the Research Spine, Primary Claims or Method, and report any positioning concern only as risk.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |