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.
Works with
--- 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. license: MIT --- # 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`.
More Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
extract
pbakaus/impeccable
Extract and consolidate reusable components, design tokens, and patterns into your design system. Identifies opportunities for systematic reuse and enriches your component library. Use when the user asks to create components, refactor repeated UI patterns, build a design system, or extract tokens.
