Minimal run and audit
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 when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
Save adds this to your Playground favorites. Hearts show appreciation.
How you can use it
- Run a repository's documented smoke test or inference command and record the results in standard output files.
- Record whether each result is verified, partial, or blocked, with a comparability report against the README or paper.
- Log any code changes to a patches file and flag changes that affect scientific meaning.
Who it's for
- Researchers checking whether a published deep learning repo reproduces its claimed results
- Reviewers who need auditable evidence from a reproduction run
Written by AI from this item's description. Check the source before relying on it.
See what it would do for your project in Playground →Set it up
Pick the app you use.
minimal-run-and-audit
- 1
Open Plugins → Skills
Left sidebar → Plugins, then the Skills tab.
- 2
Add → Upload from your computer
Pick the SKILL.md (or Create with editor and paste the text), then Create.
- 3
Use it with /
In a chat, type / and pick the skill, then write your request.
Show the skill file
# 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.md` for changed scientific meaning and evidence status - `COMPARABILITY_REPORT.md` for README/paper/baseline comparability - clear distinction between verified, partial, and blocked states - `PATCHES.md` when 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`.
Read a skill before you install it: it tells the AI what to do. Promptu never installs or runs anything.
Install from the command line
npx skills add https://github.com/lllllllama/rigorpilot-skills
Review commands before running them. Promptu never runs code on your machine or pushes changes to your repo.

