Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
How to install analyze-project?
lllllllama/rigorpilot-skills/analyze-project
$npx -y skills add lllllllama/rigorpilot-skills --skill analyze-projectInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/lllllllama/rigorpilot-skills" --skill "lllllllama/rigorpilot-skills/analyze-project"` 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/lllllllama/rigorpilot-skills" that are relevant to the current task. Run `npx skills add "https://github.com/lllllllama/rigorpilot-skills"` and select the relevant skills, then follow their instructions.
SKILL.md
| 1 | # analyze-project |
| 2 | |
| 3 | Use this as the Rigor Analyze / Rigor Audit read-only skill. The installed slug |
| 4 | remains `analyze-project` for compatibility. |
| 5 | |
| 6 | Use the shared operating principles in |
| 7 | `../../references/agent-operating-principles.md`; this skill should guide |
| 8 | read-only analysis without constraining the model's project-specific reasoning. |
| 9 | |
| 10 | ## When to apply |
| 11 | |
| 12 | - The user wants to understand a deep learning repository before changing it. |
| 13 | - The user needs a map of model structure, training entrypoints, inference entrypoints, and config relationships. |
| 14 | - The user wants conservative suggestions about likely insertion points or suspicious implementation patterns. |
| 15 | - The user explicitly wants read-only analysis and not heavy execution. |
| 16 | |
| 17 | ## When not to apply |
| 18 | |
| 19 | - When the main task is to execute a failing command or debug a traceback. |
| 20 | - When the user wants environment setup or asset download only. |
| 21 | - When the user wants speculative adaptation or broad exploratory patching. |
| 22 | - When the task is a general literature summary without repository analysis. |
| 23 | |
| 24 | ## Clear boundaries |
| 25 | |
| 26 | - This skill is read-mostly. |
| 27 | - It may run lightweight static inspection helpers. |
| 28 | - It does not patch repository code. |
| 29 | - It does not own final reproduction outputs. |
| 30 | - It should mark suspicious patterns as heuristics, not confirmed bugs. |
| 31 | |
| 32 | ## Output expectations |
| 33 | |
| 34 | - `analysis_outputs/SUMMARY.md` |
| 35 | - `analysis_outputs/RISKS.md` |
| 36 | - `analysis_outputs/status.json` |
| 37 | |
| 38 | ## Notes |
| 39 | |
| 40 | Use `references/analysis-policy.md` and the shared `../../references/research-pitfall-checklist.md`. |
Related
6 picksType
- researchInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo.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
- competitor-profilingWhen the user wants to research, profile, or analyze competitors from their URLs.Jul 2026
