| Rewrite `outline/claim_evidence_matrix.md` as a projection/index of evidence packs (NO PROSE), so claims/axes are driven by `outline/evidence_drafts.jsonl` rather than outline placeholders.
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill claim-matrix-rewriter
Purpose: make outline/claim_evidence_matrix.md a navigation/index layer that is driven by evidence packs (not by outline bullets).
Key property: keep the legacy, gate-checked format so downstream QA can rely on stable markers:
- Claim: (one per subsection) - Evidence: (>=2 per subsection)outline/subsection_briefs.jsonloutline/evidence_drafts.jsonlcitations/ref.biboutline/claim_evidence_matrix.md..., unicode ellipsis (…), TODO, (placeholder), or <!-- SCAFFOLD -->.uv run python .codex/skills/claim-matrix-rewriter/scripts/run.py --helpuv run python .codex/skills/claim-matrix-rewriter/scripts/run.py --workspace <workspace>uv run python .codex/skills/claim-matrix-rewriter/scripts/run.py --helpuv run python .codex/skills/claim-matrix-rewriter/scripts/run.py --workspace <workspace>--help.outline/subsection_briefs.jsonl, outline/evidence_drafts.jsonl, citations/ref.bib.outline/subsection_briefs.jsonl and outline/evidence_drafts.jsonl exist and blocking_missing is empty.citations/ref.bib exists and contains the cited keys.uv run python .codex/skills/claim-matrix-rewriter/scripts/run.py --workspace <workspace>citations/ref.bibFix:
citation-verifier (or fix the upstream notes) so every referenced key exists before rewriting.blocking_missingFix:
paper-notes / evidence-draft) first; the matrix should not “paper over” missing evidence.Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take willoscar/claim-matrix-rewriter from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.