mcpbeat

Claim Evidence Matrix

willoscar/claim-evidence-matrix

| Build a section-by-section claim–evidence matrix (`outline/claim_evidence_matrix.md`) from the outline and paper notes.

3k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
496
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill claim-evidence-matrix

What comes with it

10 610 bytes besides the instruction
scripts/run.py

The instruction itself

13 sections, as written by the author

Claim–Evidence Matrix

Make the survey’s claims explicit and auditable before writing prose.

This should stay bullets-only (NO PROSE). The goal is to make later writing *easy* and to prevent “template prose” from sneaking in.

Inputs

  • outline/outline.yml
  • papers/paper_notes.jsonl
  • Optional: outline/mapping.tsv

Output

  • outline/claim_evidence_matrix.md

Workflow (heuristic)

Uses: outline/outline.yml, outline/mapping.tsv.

  • For each subsection, write 1–3 claims that are:
  • specific (mechanism / assumption / empirical finding)
  • falsifiable (“X reduces tool errors under Y evaluation”, not “X is important”)
  • For each claim, list ≥2 evidence sources:
  • prefer different styles of evidence (method paper + eval/benchmark paper, or two competing approaches)
  • Keep it tight: claim → evidence → (optional) caveat/limitations.
  • If evidence is weak or only abstract-level, say so explicitly (don’t overclaim).
  • If bibkey exists in papers/paper_notes.jsonl, include [@BibKey] next to evidence items to make later prose/LaTeX conversion smoother.

Quality checklist

  • [ ] Every subsection has ≥1 claim.
  • [ ] Each claim lists ≥2 evidence sources (or an explicit exception).
  • [ ] Claims are not copy-pasted templates (avoid “围绕…总结…” boilerplate).

Helper script (optional)

Quick Start

  • uv run python .codex/skills/claim-evidence-matrix/scripts/run.py --help
  • uv run python .codex/skills/claim-evidence-matrix/scripts/run.py --workspace <workspace>

All Options

  • See --help (this helper is intentionally minimal)

Examples

  • Generate a first-pass matrix, then refine manually:
  • Run the helper once, then refine outline/claim_evidence_matrix.md by tightening claims and adding caveats when evidence is abstract-level.

Notes

  • The helper generates a baseline matrix (claims + evidence) and never overwrites non-placeholder work; in pipeline.py --strict it will be blocked only if placeholder markers remain.

Troubleshooting

Issue: claims are generic or read like outline boilerplate

Fix:

  • Tighten each claim to a falsifiable statement and add an explicit caveat if evidence is abstract-only.

Issue: you cannot add [@BibKey] because keys are missing

Fix:

  • Run citation-verifier to generate citations/ref.bib, then use the produced keys in the matrix.

How to use it

Copy the folder

Take willoscar/claim-evidence-matrix from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.