Skills lllllllama rigorpilot-skills RigorPilot
analyze-project
- Use it when:
- You want to understand a deep-learning research repo before changing it, without running anything heavy.
- It does:
- Maps the model structure, the training, inference and evaluation entry points and how configs connect, and points out where changes could plug in.
- You get:
- An analysis_outputs/ folder with a summary, a risks file and a machine-readable status.
- Doesn't:
- Patch code, launch heavy jobs, or call a suspicious pattern a confirmed bug.
- Unlike repo-intake-and-plan:
- That one picks a README command to reproduce; this one explains the code itself.
Skill 5 of 11 in the RigorPilot bundle, after env-and-assets-bootstrap and before minimal-run-and-audit.
TL;DR
A read-only skill from RigorPilot, a set of skills that reproduces deep-learning research code from its README. It looks for the likely training, inference and evaluation entry points, summarizes how configs and scripts are laid out, and suggests insertion points, the places where a new module or change would plug in, conservatively. Patterns that look wrong, checked against a research-pitfall checklist that ships with the repo's main skill, ai-research-reproduction, are reported as heuristics to review, not as bugs. It may run lightweight static inspection helpers and writes only its own report files: it never patches the repository's code or starts heavy training or evaluation. The main skill calls it only when a repo's structure needs clarifying, and ai-research-explore usually uses it to understand a repo before trying ideas; on its own, it fits the moment before you plan changes to someone else's research code.
Summarizes the skill at fb3ccdf.
npx skills add https://github.com/lllllllama/rigorpilot-skills --skill analyze-project skills.sh pageSource on GitHubAll skills from lllllllama/rigorpilot-skills
More weekly downloads than 93% of skills
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 25 |
| Sep 28 | 61 |
| Oct 5 | 83 |
| Oct 12 | 3,530 |
| Oct 19 | 10,941 |
| Oct 26 | 11,055 |
| Nov 2 | 8,789 |
| Nov 9 | 7,292 |
More downloads than 95% of skills
Fewer stars than 88% of repos
Newer than 97% of skills
| Category |
Research reproduction, financial data, charts and diagrams. |
|---|---|
| Type |
A multi-step process the agent follows: interview, debug, run a TDD loop, review. |
| Effect |
Its own steps create or change files, git state or local tools. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics | |
| Stack |
SKILL.md
From lllllllama/rigorpilot-skills at fb3ccdf. Checked daily, last changed Nov 6, 2026.
Frontmatter
name: analyze-project
description: 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.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.mdanalysis_outputs/RISKS.mdanalysis_outputs/status.json
Notes
Use references/analysis-policy.md and the shared ../ai-research-reproduction/references/research-pitfall-checklist.md.