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.
仅记录已同意可选统计的用户事件。浏览按账号、Skill 与上海自然日去重;下载按账号、Skill、版本与上海自然日去重,统计仅表示客户端成功交付安装包,不保证包已保存到磁盘。安装仅在客户端成功完成 Skill 写入后记录,并按账号与 Skill 去重 90 天;撤回同意会清理个人去重记录,重新开启后再次安装可能再次计数。“本周”指最近 7 个上海自然日。收藏为当前总数。
Skill 步骤
--- 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.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`.
版本历史
已发布版本会持续保留,可用于校验和恢复。
Imported from lllllllama/rigorpilot-skills@ZIP 467e9239f333c6bd80e64d31301838b4a00182023e59b2360156bec04d417a9e