agentsclimarketplace
Sign in

Analyze project

Skill bg-szy/TOP-SKILLS/skills/marketplace/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.From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill analyze-project

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 308 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 1 file

32.6 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,790. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.