Skills ZICQ category：Writing & Research analyze-project

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.

311180 installs

Official URL：skills.sh

What this skill does

Intro in this page language first. The official description stays in its original wording; we do not rewrite SKILL.md.

What it does

Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories

When to use it

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

How agents load it

Per Agent Skills progressive disclosure: name and description load at startup (~100 tokens); the full SKILL.md body loads when the skill activates; scripts/, references/, and assets/ load only as needed. This file's sections: analyze-project; When to apply; When not to apply; Clear boundaries; Output expectations; Notes.

File analysis

File analysis: besides SKILL.md, the body references references/agent-operating-principles.md, references/analysis-policy.md, references/research-pitfall-checklist.md. Those resources load on demand.

analyze-projectWhen to applyWhen not to applyClear boundariesOutput expectationsNotes

Source category：skills.sh agent-skill

Sources & links

Market sources：skills.sh

Full package on GitHub

OSS Skill ranking

SKILL.md & Agent activation

Official spec ↗

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.

DiscoverThe client exposes names and descriptions to the agent.
ActivateYour request or the task context selects the skill and loads its instructions.
Load resourcesReferenced scripts, documentation and assets are used when needed.

Files referenced by the instructions · 3

references/agent-operating-principles.md
references/analysis-policy.md
references/research-pitfall-checklist.md

These paths are extracted from the text. Check the upstream package to verify the files exist.

Invocation syntax and available tools depend on your Agent client. Client integration guide ↗

Install this skill

Skills CLI ↗

Choose the target agent and installation scope, keep referenced package files, then verify the skill appears in the client's catalog.

This skill references supporting files. Retrieve the complete directory from the source; copying SKILL.md alone may leave missing dependencies.

Ask your Agent to install

Copy these instructions to a compatible agent and confirm the target directory matches your client.

Install the agent skill "analyze-project" into my project. The full SKILL.md and official description are at https://zicq.com/en/skills/skl-d27dbd56194685ab-Analyze-Project.html
Save it as .cursor/skills/analyze-project/SKILL.md or .claude/skills/analyze-project/SKILL.md and keep the frontmatter name and description exactly as-is.
This skill also ships scripts/, references/, or assets/ — fetch the whole folder from https://github.com/lllllllama/rigorpilot-skills instead of creating only a SKILL.md.

Full package on GitHub ↗

Install from the terminal · Skills CLI

Requires Node.js and npx. First inspect the repository's skill list to confirm the name.

npx skills add 'https://github.com/lllllllama/rigorpilot-skills' --list

npx skills add 'https://github.com/lllllllama/rigorpilot-skills' --skill 'analyze-project'

The CLI lets you choose the agent interactively. The default scope is the project; use -g for user scope. Confirm package availability with the discovery command, then use npx skills list to inspect installed skills.

SKILL.md source Copy freely; the source file is unchanged

---
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`.

Readable layout

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.

Related skills

Writing & Research