AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Academic Repo Analyzer

skill-azhi-ss-academic-figure-skills-academic-repo-analyzer · by Azhi-ss

Quick-understanding doc for ML/DL repositories — task type, stack, architecture, and figure-worthy innovations. Use when the user wants repo analysis, 仓库分析, or to understand a codebase before figure planning.

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-azhi-ss-academic-figure-skills-academic-repo-analyzer

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-azhi-ss-academic-figure-skills-academic-repo-analyzer)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
15d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Academic Repo Analyzer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Academic Repo Analyzer

Produce a 仓库快速理解文档 for downstream figure planning.

Keywords: → keywords.md Missing info: → ../docs/missing-info-policy.md

Input Contract

  • Prefer: repo path, README, deps, entry scripts, model files, configs
  • Minimum: any one of README / entry script / model file
  • Missing: partial analysis with 推断 / 待确认

Output Contract — Quick Understanding Doc

  • overview (name, task, framework, architecture one-liner)
  • completeness block
  • stack details
  • model / algorithm notes
  • train / inference flow (or “evidence insufficient”)
  • figure suggestions for paper-analyzer

Steps

Step 1: Scan structure

Locate README, dependency files, entry scripts (train|main|eval|inference), configs/, models|networks|src/, data loaders.

Done when: tree of key paths exists and each must-read class is read or marked missing.

Step 2: Task + stack

Use keywords.md. Classify task type and framework from imports, deps, and paths.

Done when: task type + primary framework are stated with file evidence.

Step 3: Architecture + algorithms

From model files: backbone family, key modules, losses, training tricks. Prefer evidence over naming guesses.

Done when: architecture summary cites concrete classes/files, or is marked 推断.

Step 4: Emit quick-understanding doc

# 仓库快速理解文档
## 仓库概览
| 项目 | 内容 |
| 仓库名称 / 任务类型 / 核心框架 / 主要架构 / 一句话描述 | ... |
## 信息完整度说明
## 技术栈详情
## 模型架构分析
## 工作流程
## 配图建议(→ paper-analyzer)

Done when: Output Contract fields are filled; figure suggestions list concrete types (framework / arch / module / …).

Sparse-input cases

| gap | action | |-----|--------| | no README | infer from code; label as structure-inferred | | no entry scripts | module-level understanding only | | no model files | stack/task only; soft architecture language | | huge repo | sample top-level + 3–5 core files; mark limited sample | | almost nothing | pre-analysis + minimum materials list (README → deps → entry → model → config) |

Tooling cues

Prefer the environment’s file/search tools. Typical digs: dependency files, class.*Model|Network|Transformer, loss|criterion, model package entrypoints.

Stop

Stop when the quick-understanding doc is delivered. Suggest paper-analyzer only if the user wants figure planning next.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.