mcpbeat Sign in

Claim Evidence Matrix Skill for Codex

| 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.

Other skills for the same job

different authors, same section of the catalogue
Content Research Writer
by frostant
×10

Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.

4k tokens
Lead Research Assistant
by frostant
×8

Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.

2k tokens
Notebooklm
by ZhanlinCui
×6

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

26k tokens scripts
Biorxiv Database
by christophacham
×4

Efficient database search tool for bioRxiv preprint server. Use this skill when searching for life sciences preprints by keywords, authors, date ranges, or categories, retrieving paper metadata, downloading PDFs, or conducting literature reviews.

9k tokens scripts
Openalex Database
by christophacham
×4

Query and analyze scholarly literature using the OpenAlex database. This skill should be used when searching for academic papers, analyzing research trends, finding works by authors or institutions, tracking citations, discovering open access publications, or conducting bibliometric analysis across 240M+ scholarly works. Use for literature searches, research output analysis, citation analysis, and academic database queries.

13k tokens scripts
Uspto Database
by christophacham
×4

Access USPTO APIs for patent/trademark searches, examination history (PEDS), assignments, citations, office actions, TSDR, for IP analysis and prior art searches.

21k tokens scripts
Denario
by christophacham
×3

Multiagent AI system for scientific research assistance that automates research workflows from data analysis to publication. This skill should be used when generating research ideas from datasets, developing research methodologies, executing computational experiments, performing literature searches, or generating publication-ready papers in LaTeX format. Supports end-to-end research pipelines with customizable agent orchestration.

11k tokens
Hypogenic
by christophacham
×3

Automated LLM-driven hypothesis generation and testing on tabular datasets. Use when you want to systematically explore hypotheses about patterns in empirical data (e.g., deception detection, content analysis). Combines literature insights with data-driven hypothesis testing. For manual hypothesis formulation use hypothesis-generation; for creative ideation use scientific-brainstorming.

7k tokens

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.