mcpbeat Sign in

Analyze Project Agent Skill

by lllllllama

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.

7k tokens
context cost
the whole folder, loaded on every use
4
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
484
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/lllllllama/RigorPilot-Skills --skill analyze-project

What comes with it

26 898 bytes besides the instruction
agents/openai.yaml
references/analysis-policy.md
scripts/analyze_project.py

The instruction itself

6 sections, as written by the author

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.

How to use it

Copy the folder

Take lllllllama/analyze-project from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.