manuscript-provenance
bymathews-tom· 56 skills
Computational provenance audit verifying every number, table, and figure in a manuscript derives from code, not manual entry. Triggers on: "check provenance", "verify reproducibility", "audit my pipeline", "are my numbers from code", "provenance audit". Companion to manuscript-review (prose audit).
How to install manuscript-provenance?
mathews-tom/armory/manuscript-provenance
$npx -y skills add mathews-tom/armory --skill manuscript-provenanceInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/mathews-tom/armory" --skill "mathews-tom/armory/manuscript-provenance"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/mathews-tom/armory" that are relevant to the current task. Run `npx skills add "https://github.com/mathews-tom/armory"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- researchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo.Jul 2026
- analyze-projectRigor Analyze / Rigor Audit read-only skill for deep learning research repositories.Jul 2026
- paper-context-resolverRigor Paper Context helper for README-first deep learning repo reproduction.Jul 2026
- repo-intake-and-planRigor Intake helper for README-first deep learning repo reproduction.Jul 2026
- firecrawl-searchWeb search with full page content extraction. Use this skill whenever the user asks to search the web, find articles, research a topic, look something up, find…Jul 2026
- customer-researchWhen the user wants to conduct, analyze, or synthesize customer research.Jul 2026
