Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories.
SkillScore32Maintained
Automatic
◆AI Engineer pack
Last verified 9/7/2026
What it changes
Passed 3 of 10 test cases with the skill, and 2 of 10 without it.
Without skill18%
With skill32%
Checks it passed that the model alone missed
Declines environment setup requests
Names the file path analysis_outputs/RISKS.md
Names the file path analysis_outputs/SUMMARY.md
and 2 more in the full report
5 fixed2 passed either way13 still failing2 broke
Pass-rate lift
+14 pp
Tokens
-19%
Agent turns
0%
Response time
-31%
Model gemini-3.6-flashMeasured 9/7/2026v37 of 22 cases passed with skill · 10 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
Which exact output path is assigned for storing the high-level codebase summary, model architecture overview, and entrypoint inventory?
What was checked, without and with the skill
Checked
Without skill
With skill
Names the file path analysis_outputs/SUMMARY.md
Missed
Passed
case-17 · gemini-3.6-flash · 9/7/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md40 lines5 filesincludes scripts
analyze-project
Use this as the Rigor Analyze / Rigor Audit read-only skill. The installed slug
remains analyze-project for compatibility.
Use the shared operating principles in
../ai-research-reproduction/references/agent-operating-principles.md; this skill should guide
read-only analysis without constraining the model's project-specific reasoning.
When to apply
The user wants to understand a deep learning repository before changing it.
The user needs a map of model structure, training entrypoints, inference entrypoints, and config relationships.
The user wants conservative suggestions about likely insertion points or suspicious implementation patterns.
The user explicitly wants read-only analysis and not heavy execution.
When not to apply
When the main task is to execute a failing command or debug a traceback.
When the user wants environment setup or asset download only.
When the user wants speculative adaptation or broad exploratory patching.
When the task is a general literature summary without repository analysis.
Clear boundaries
This skill is read-mostly.
It may run lightweight static inspection helpers.
It does not patch repository code.
It does not own final reproduction outputs.
It should mark suspicious patterns as heuristics, not confirmed bugs.
Output expectations
analysis_outputs/SUMMARY.md
analysis_outputs/RISKS.md
analysis_outputs/status.json
Notes
Use references/analysis-policy.md and the shared ../ai-research-reproduction/references/research-pitfall-checklist.md.