Skill

analyze-project

From lllllllama-ai-paper-reproduction-skill

Analyzes deep learning research repositories: maps model structures, training/inference entrypoints, configs, insertion points; flags suspicious patterns. Read-only, no code changes.

Python

ai-ml

npx claudepluginhub lllllllama/ai-research-workflow-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- The user wants to understand a deep learning repository before changing it.

Supporting Assets

agents/openai.yamlreferences/analysis-policy.mdscripts/analyze_project.py

SKILL.md

Similar Skills

repo-intake-and-plan

Scans repositories to map structure, extract documented commands from READMEs/project files, classify inference/evaluation/training candidates, and plan minimal trustworthy AI reproduction.

4 files

lllllllama-ai-paper-reproduction-skill

repo-research

167

Clones GitHub repositories for deep analysis of code, architecture, dependencies; generates reports with integration suggestions and local project comparisons. Supports theme-based repo discovery.

15 files

legal-skills

review-health

Performs first-pass strategic review of repositories, producing evidence-cited maps calibrated to reference classes to guide where to engage, tread carefully, or leave alone. Advisory only.

7 files

claude-swe-workflows

Stats

Stars10

Forks0

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

analyze-project

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.

analyze-project

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.