Menu
Use when integrating results into a paper or drafting any paper section — enforces that every claim maps to specific evidence before it can be written
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when designing the evaluation protocol for a method development project — locks primary metrics, datasets, seeds, statistical tests, and baseline list into an immutable contract
Use when G2 (plan freeze) and G3 (execution readiness) gates have passed — handles all implementation, baseline reproduction, experimentation, and iteration for both Type M and Type D projects; this is Phase 4
Use when research direction is validated (G1 passed) and the project needs method design, analysis framework, evaluation protocol, or story line — this is Phase 3 and must complete before any code or experiments
Reusable protocol for multi-agent discussions that iterate until convergence. Used by results-integration (Phase 5) and paper-writing (Phase 6) to ensure discussions actually resolve issues rather than just noting them.
Use when and ONLY when the user explicitly requests paper writing and G4 (write-ready) gate has passed — handles LaTeX structure, senior-level writing, reference verification, and iterative refinement
Use when Phase 1 (research-direction-exploration) is complete and G1 gate has passed — subjects the research problem to adversarial defense-style questioning, classifies project intent, re-evaluates venue target, and produces a final feasibility ruling before any method design begins
| name | claim-evidence-alignment |
| description | Use when integrating results into a paper or drafting any paper section — enforces that every claim maps to specific evidence before it can be written |
A claim without evidence is an opinion, not a result. This skill activates at Phase 5 (results integration) and remains in effect through Phase 6 (paper writing).
Core principle: Evidence first, claim second. Never the reverse.
Violating the letter of this rule is violating the spirit of this rule.
EVERY CLAIM MUST MAP TO SPECIFIC EVIDENCE. UNMAPPED CLAIMS ARE DELETED.
Before writing any paper section, build and maintain this table:
| Claim | Evidence Source | Figure/Table | Statistical Support |
|---|---|---|---|
| (exact claim text) | (experiment, dataset, condition) | (Fig X / Table Y) | (test, p-value, CI) |
Every row must be complete. Empty cells mean the claim is not ready to write.
| Excuse | Reality |
|---|---|
| "The trend is clear visually" | Visual trends need statistical backing. Show the numbers. |
| "Everyone knows this is true" | Common knowledge still needs citation. Your claim needs evidence. |
| "The result is obvious from the method" | Theoretical arguments need empirical validation in a paper. |
| "I'll add the evidence later" | No claim without evidence. Write evidence first, claim second. |
No evidence → no claim
Weak evidence → weak language
Strong evidence → then and only then, strong claim
Map every claim. Delete the rest. No exceptions.