# Analyze Project > 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. Source: https://skillsagentes.com/skills/lllllllama/rigorpilot-skills/analyze-project Repository: https://github.com/lllllllama/RigorPilot-Skills Author: lllllllama License: MIT Updated: hace 19 días Context cost: 112 tok installed, 508 tok once triggered, 7.2k tok with every bundled file Bundle: 4 files, 28 KB Permissions requested: none declared ## Install ```bash npx -y skills add lllllllama/RigorPilot-Skills --skill analyze-project --agent claude-code ``` ## What it does - Genera un mapa de la estructura del modelo, entrypoints de entrenamiento e inferencia y relaciones entre configs - Sugiere de forma conservadora posibles puntos de inserción de código - Marca patrones de implementación sospechosos como heurísticas, no como bugs confirmados - Produce analysis_outputs/SUMMARY.md, RISKS.md y status.json - Puede ejecutar helpers ligeros de inspección estática, sin parchear el repositorio ## Use it when - El usuario quiere entender un repositorio de deep learning antes de modificarlo - Se necesita un mapa de estructura del modelo, entrypoints y configs - El usuario pide sugerencias conservadoras sobre puntos de inserción o patrones sospechosos - El usuario quiere explícitamente análisis de solo lectura, no ejecución pesada ## Don't bother when - La tarea principal es ejecutar un comando que falla o depurar un traceback - El usuario quiere adaptación especulativa de código o parcheo exploratorio amplio - La tarea es un resumen de literatura general sin análisis del repositorio ## What triggers it - "Ayúdame a entender la estructura de este repositorio antes de tocar nada" - "Mapea los entrypoints de entrenamiento e inferencia de este proyecto" - "Revisa las configs y dime posibles puntos de inserción de código" - "Detecta patrones de implementación sospechosos en este repo, sin modificar nada" ## Before you install - Requiere los archivos de referencia compartidos ../../references/agent-operating-principles.md, references/analysis-policy.md y ../../references/research-pitfall-checklist.md. ## Files - SKILL.md — 2 KB - agents/openai.yaml — 396 B - references/analysis-policy.md — 545 B - scripts/analyze_project.py — 25 KB ## SKILL.md Reproduced verbatim from lllllllama/RigorPilot-Skills under MIT. This section is the upstream document and is in English. # 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 `../../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 `../../references/research-pitfall-checklist.md`. --- Skills Agentes — https://skillsagentes.com/skills/lllllllama/rigorpilot-skills/analyze-project