analyze-project — Claude Code skill: read a deep learning repo
Reads a deep learning repository and maps its structure, entrypoints and suspicious spots. Changes nothing, runs no heavy jobs.
npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a claude-codeWhat analyze-project does
The skill is read-mostly. It inspects code and never patches it. You get three files: analysis_outputs/SUMMARY.md, analysis_outputs/RISKS.md and analysis_outputs/status.json. Together they show how the model is built, where training and inference entrypoints live, and how the configs relate to each other.
It leans on shared agent operating principles from ../ai-research-reproduction/references/agent-operating-principles.md, an analysis policy in references/analysis-policy.md, and a research pitfall checklist. Lightweight static inspection helpers are allowed. Command execution and environment setup are not part of the job.
Suspicious patterns come back labelled as heuristics, not confirmed bugs. Keep that in mind before you treat a flag as a real defect. Debugging a failing command or a traceback is a different task, and so is broad refactoring or speculative patching. Final reproduction outputs stay outside this skill's scope.
What it helps with
- understand an unfamiliar repository before touching it
- map training and inference entrypoints
- trace how configs connect and where insertion points sit
- flag suspicious implementation patterns without editing code
- get a summary and a risk list as separate files
Example prompts for the agent
- Walk through this repo and show me the model structure and training entrypoints
- Where do the configs live, and where would my module fit best?
- Review the code and flag anything suspicious — no edits
How to install analyze-project
1Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a claude-code2Manually: put the files in place
~/.claude/skills/analyze-project/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/analyze-project/
1Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a codex2Manually: put the files in place
.agents/skills/analyze-project/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a cursor2Manually: put the files in place
.cursor/skills/analyze-project/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install lllllllama/RigorPilot-Skills analyze-project2Manually: put the files in place
.github/skills/analyze-project/SKILL.md1Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a gemini-cli2Platform CLI
gemini skills install https://github.com/lllllllama/RigorPilot-Skills --path skills/analyze-projectManually: put the files in place
.devin/skills/analyze-project/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set9
The whole set →Similar
Questions about analyze-project
How do I install analyze-project in Claude?
Run npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a claude-code. The skill then sits at ~/.claude/skills/analyze-project/SKILL.md.
What does analyze-project do?
It reads a deep learning repository and describes its structure, entrypoints, config relationships and suspicious patterns. It does not modify code.
Can it debug a failing command?
No. Running commands and reading tracebacks is outside its scope — it is built for reading and flagging, not execution.
Source text
SKILL.md · MIT
--- 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.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`.
© lllllllama · MIT · lllllllama/RigorPilot-Skills