Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories.
Install Analyze Project
$ npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lllllllama/RigorPilot-Skills analyze-project --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/lllllllama/RigorPilot-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analyze-project .claude/skills/analyze-project && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "analyze-project" agent skill from https://github.com/lllllllama/RigorPilot-Skills/tree/main/skills/analyze-project into .claude/skills/analyze-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-project", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/lllllllama/RigorPilot-Skills/tree/main/skills/analyze-projectType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lllllllama/RigorPilot-Skills analyze-project --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lllllllama/RigorPilot-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analyze-project .agents/skills/analyze-project && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyze-project" agent skill from https://github.com/lllllllama/RigorPilot-Skills/tree/main/skills/analyze-project into .agents/skills/analyze-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-project", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lllllllama/RigorPilot-Skills analyze-project --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lllllllama/RigorPilot-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analyze-project .cursor/skills/analyze-project && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analyze-project" agent skill from https://github.com/lllllllama/RigorPilot-Skills/tree/main/skills/analyze-project into .cursor/skills/analyze-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-project", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/lllllllama/RigorPilot-Skills.git --path skills/analyze-project--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lllllllama/RigorPilot-Skills analyze-project --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lllllllama/RigorPilot-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analyze-project .gemini/skills/analyze-project && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "analyze-project" agent skill from https://github.com/lllllllama/RigorPilot-Skills/tree/main/skills/analyze-project into .gemini/skills/analyze-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-project", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install lllllllama/RigorPilot-Skills analyze-projectInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lllllllama/RigorPilot-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analyze-project .github/skills/analyze-project && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "analyze-project" agent skill from https://github.com/lllllllama/RigorPilot-Skills/tree/main/skills/analyze-project into .github/skills/analyze-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-project", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lllllllama/RigorPilot-Skills analyze-project --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lllllllama/RigorPilot-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analyze-project .opencode/skills/analyze-project && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analyze-project" agent skill from https://github.com/lllllllama/RigorPilot-Skills/tree/main/skills/analyze-project into .opencode/skills/analyze-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-project", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
analyze-project- GitHub stars
- 497
- Used in
- 1 other repo
- Token cost
- ~519 tokens
- SKILL.md length
- 187 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories.
- The user wants to read and understand a repository
- SKILL.md covers When to apply, When not to apply, Clear boundaries and Output expectations, plus 1 more section
- Runs Python scripts from its folder
- Inspect model structure and training
What it does
Analyze Project is an agent skill from lllllllama/RigorPilot-Skills. 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.
Its SKILL.md is about 520 tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/analysis-policy.md` and `scripts/analyze_project.py`).
It sits in Development, covering Deep learning, Debugging and Refactoring. The repository describes itself as: README-first research reproduction skills with bounded execution, auditable evidence, and byte-preserving README annotations. The licence is MIT.
When your agent uses it
- The user wants to read and understand a repository
- Inspect model structure and training
- Inference entrypoints
- Review configs and insertion points
Example prompts
- “/analyze-project”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit fb3ccdf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Analyze Project loads about 519 tokens when it runs, and up to ~656 if it reads all its reference files. Until then it costs about 116 tokens; SKILL.md has 187 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from lllllllama/RigorPilot-Skills at commit fb3ccdf, republished under its MIT licence (© lllllllama). 187 words, ~519 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-project/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- 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.
© lllllllama, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (scripts, references) in skills/analyze-project of lllllllama/RigorPilot-Skills.
- SKILL.md
- agents/openai.yaml
- references/analysis-policy.md
- scripts/analyze_project.py
Open the folder on GitHubat commit fb3ccdf
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in lllllllama/RigorPilot-Skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Analyze Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analyze Project this skilllllllllama/RigorPilot-Skills | 497 | 1 repos | ~519 | Automated safety check: Pass | MIT | |
| Aoti Debugpytorch/pytorch | 104k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| The Art of Debuggingstas00/the-art-of-debugging | 1.7k | — | ~6.1k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Veomni DebugByteDance-Seed/VeOmni | 2.2k | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Code Review Graph Navigatorhandsontable/handsontable | 22k | — | ~939 | Automated safety check: Pass | Custom licence | |
| Andrej Karpathy Skillduolahypercho/andrej-karpathy-skills | 249 | — | ~793 | Automated safety check: Pass | MIT |
Similar skills
The Art of Debugging
stas00/the-art-of-debugging
Condensed debugging method and tool recipes for Unix, Python and PyTorch programs: crashes, hangs, segfaults, wrong output, CUDA OOM, NaN values and slowness.
Veomni Debug
ByteDance-Seed/VeOmni
A skill your agent uses for ANY bug, error, crash, wrong output, loss divergence, gradient explosion, test failure, CUDA error, distributed training hang, checkpoint load failure, or unexpected…
Code Review Graph Navigator
handsontable/handsontable
Queries a pre-built, Tree-sitter-based code graph of the whole monorepo instead of grepping call chains, for exploring, debugging, refactoring or reviewing code.
Andrej Karpathy Skill
duolahypercho/andrej-karpathy-skills
Apply Andrej Karpathy-inspired coding-agent guidelines in Codex.
Verdaccio Change Implementation
verdaccio/verdaccio
A workflow for implementing a Verdaccio bug fix, feature or refactor: pick the release lines, check existing options, edit the owning layer, test and add a changeset.
More from lllllllama/RigorPilot-Skills
All 11 skills in this repoAI Research Reproduction
lllllllama/RigorPilot-Skills
Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction.
AI Research Explore
lllllllama/RigorPilot-Skills
Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates.
Env And Assets Bootstrap
lllllllama/RigorPilot-Skills
Rigor Setup skill for README-first deep learning repo reproduction.
Explore Code
lllllllama/RigorPilot-Skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories.
Explore Run
lllllllama/RigorPilot-Skills
Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories.
Minimal Run And Audit
lllllllama/RigorPilot-Skills
Rigor Run skill for README-first deep learning repo reproduction.
Related
Categories
Questions about Analyze Project
What does Analyze Project do?
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Analyze Project is an agent skill from lllllllama/RigorPilot-Skills. Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories.
When should I use Analyze Project?
Analyze Project fits situations like: the user wants to read and understand a repository; inspect model structure and training; inference entrypoints; review configs and insertion points.
How do I install Analyze Project in Claude Code?
Run `npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a claude-code`. Or copy the skill folder (skills/analyze-project in lllllllama/RigorPilot-Skills) into .claude/skills/analyze-project in your project. Claude Code loads it when a task matches its description.
How do I install Analyze Project in Codex?
Run `npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a codex`. Or copy the skill folder (skills/analyze-project in lllllllama/RigorPilot-Skills) into .agents/skills/analyze-project in your project. Codex loads it when a task matches its description.
Can I use Analyze Project in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lllllllama/RigorPilot-Skills --skill analyze-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-project, .gemini/skills/analyze-project, .github/skills/analyze-project and .opencode/skills/analyze-project in your project.
What does Analyze Project need to run?
Going by SKILL.md and its folder, Analyze Project needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Analyze Project access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Analyze Project safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Analyze Project use?
Analyze Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Analyze Project use?
About 519 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 137 tokens, read only when the agent opens those files.
What are the alternatives to Analyze Project?
Skills that share tags, products or a category with Analyze Project: Aoti Debug (pytorch/pytorch, 104k stars), The Art of Debugging (stas00/the-art-of-debugging, 1.7k stars), Veomni Debug (ByteDance-Seed/VeOmni, 2.2k stars) and Code Review Graph Navigator (handsontable/handsontable, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analyze Project?
lllllllama (a GitHub user) maintains it in lllllllama/RigorPilot-Skills, which has 497 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 23, 2026.
Source: lllllllama/RigorPilot-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.