Minimal Run And Audit
Writing & docs491.9K installs
What it does
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes…
Install
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill minimal-run-and-auditWebsite
www.skills.sh/lllllllama/rigorpilot-skills/minimal-run-and-auditDetails
From the skill’s SKILL.md or README, by its authors. View the original
minimal-run-and-audit
Use this as the Rigor Run skill. The installed slug remains minimal-run-and-audit for compatibility.
Use the shared operating principles in ../ai-research-reproduction/references/agent-operating-principles.md; this skill should make run evidence auditable without turning every command into a rigid protocol.
When to apply
- After a reproduction target and setup plan exist.
- When the main skill needs execution evidence and normalized outputs.
- When a smoke test, documented inference run, documented evaluation run, or other short non-training verification is appropriate.
- When the user already knows what command should be attempted and wants execution plus reporting only.
When not to apply
- During initial repo scanning.
- When environment or assets are still undefined enough to make execution meaningless.
- When the task is a literature lookup rather than repository execution.
- When the user is still deciding which reproduction target should count as the main run.
Clear boundaries
- This skill owns normalized reporting for an attempted command.
- It may receive execution evidence from the main skill or a thin helper.
- It does not choose the overall target on its own.
- It does not perform broad paper analysis.
- It does not own training startup, resume, or long-running training state.
- It should not normalize risky code edits into acceptable practice.
- It must not hide changes that alter evaluation, preprocessing, checkpoints,
metrics, or other scientific meaning.
Input expectations
- selected reproduction goal
- runnable commands or smoke commands
- environment and asset assumptions
- optional patch metadata
Output expectations
- execution result summary
- standardized
repro_outputs/files SCIENTIFIC_CHANGELOG.mdfor changed scientific meaning and evidence statusCOMPARABILITY_REPORT.mdfor README/paper/baseline comparability- clear distinction between verified, partial, and blocked states
PATCHES.mdwhen repo files changed
Notes
Use references/reporting-policy.md, ../ai-research-reproduction/references/research-rigor-principles.md, scripts/run_command.py, and scripts/write_outputs.py.
More Writing & docs skills
See allWriting & docs
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
1.3M installsnpx skills add https://github.com/mattpocock/skills --skill grill-with-docsWriting & docs
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
1.1M installsnpx skills add https://github.com/mattpocock/skills --skill triageWriting & docs
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
952.2K installsnpx skills add https://github.com/mattpocock/skills --skill domain-modelingWriting & docs
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
528.6K installsnpx skills add https://github.com/mattpocock/skills --skill writing-beats
Skills are shared by members and not reviewed by us. Read a skill’s code before you install it.