agentleFS
flyer-Liflyer-Li/paper-analyst/SKILL.md

paper-analyst

Skill68 starsChanged 7 months agoMITView on GitHub

Analyze academic papers and research PDFs. Use this skill when the user uploads or pastes a research paper and wants to understand it. Triggers: 'analyze this paper', 'read this PDF', 'summarize this research', 'paper summary', 'research paper breakdown', 'explain this study', 'paper critique', 'academic paper analysis', '论文分析', '帮我看这篇论文', '解读这篇文章', '这篇 paper 讲什么', '帮我分析这个 PDF', '论文解读', '文献分析', '读一下这篇论文', '帮我总结这篇文章', '这篇论文的创新点', '论文方法分析', '论文结果', '帮我准备组会汇报', '生成 PPT 大纲'. Do NOT use for non-academic PDFs, spreadsheets, or general document tasks.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 1

    1. Mingel-github/claude-skills★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 1

    1. EtherealMingo/university-teacher-skills★ 16same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. About 0 are common, 8 are distinctive, and 12 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 12

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All outputs follow references/output-schema.md.

    line 9
  2. Very specific:

    Default mode: standard. Detect from user's request:

    line 27
  3. Very specific:

    If ambiguous, use standard and offer to switch.

    line 37
  4. Distinctive:

    If degraded: state reason in header line, proceed with available content, mark all gaps explicitly.

    line 48
  5. Very specific:

    Read references/paper-type-rubric.md and classify.

    line 56
  6. Very specific:

    Follow references/output-schema.md for the selected mode.

    line 61
  7. Very specific:

    Every uncertain field marked [不确定] or [未明确给出]

    line 67
  8. Very specific:

    Every contribution tagged [原文声明] or [模型归纳]

    line 68
  9. Distinctive:

    No section silently omitted — skipped sections state why

    line 69
  10. Very specific:

    Only in extended mode:

    line 96
  11. Distinctive:

    If insufficient info: explicitly state "信息不足,无法判断前作关系"

    line 102
  12. Very specific:

    Only in presentation or presentation_with_figures mode.

    line 106
  13. Distinctive:

    Before building the slide plan, check if the user specified any of:

    line 110
  14. Distinctive:

    If not specified, use defaults silently.

    line 117
  15. Distinctive:

    Before building the slide plan, run:

    line 121
  16. Very specific:

    Follow references/presentation-schema.md for structure.

    line 129
  17. Very specific:

    Follow references/presentation-style-guide.md for compression rules.

    line 130
  18. Very specific:

    Follow references/pptx-handoff.md for the exact handoff format.

    line 139
  19. Distinctive:

    Do NOT include speaker notes in the handoff

    line 142
  20. Distinctive:

    Call pptx skill automatically — do not ask the user first

    line 143

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Paper Analyst

Analyze academic papers from PDF or pasted text. Output in Chinese by default. All outputs follow references/output-schema.md. Paper type detection uses references/paper-type-rubric.md. Anti-hallucination rules in references/quality-checklist.md.

Quick Reference

FilePurpose
references/output-schema.mdSection structure and field rules
references/paper-type-rubric.mdHow to classify paper type
references/quality-checklist.mdAnti-hallucination checklist
references/presentation-schema.mdSlide plan JSON schema
references/presentation-style-guide.mdContent compression rules for slides
references/pptx-handoff.mdHow to call the pptx skill for rendering
scripts/extract_pdf_meta.pyOptional: extract PDF metadata to JSON

Mode Selection

Default mode: standard. Detect from user's request:

ModeTriggerOutput
quick"quick", "简单说", "一句话", "简要"Header + info + abstract + 3 contributions
standard(default)Full analysis: sections 1–5
extended"前作", "课题组", "prior work"standard + author/group prior work
presentation"PPT", "组会", "汇报大纲", "slides"standard + slide outline
presentation_with_figures"图表", "figures", "带图", "关键图"presentation + figure annotations

If ambiguous, use standard and offer to switch.

Workflow

Step 1: Assess Input Quality

Classify PDF quality before analysis:

  • 良好: Full text extractable
  • 降级处理: Partial text, scanned sections, garbled encoding
  • 严重降级: Minimal text, image-only PDF

If degraded: state reason in header line, proceed with available content, mark all gaps explicitly. Never fabricate content to fill gaps.

Optional: if user has Python, suggest running scripts/extract_pdf_meta.py first for structured metadata.

Step 2: Classify Paper Type

Read references/paper-type-rubric.md and classify. Do NOT assume AI/ML. Output the type label and 2–3 evidence indicators before proceeding.

Step 3: Execute Analysis

Follow references/output-schema.md for the selected mode. Apply all rules from references/quality-checklist.md throughout every section.

Step 4: Self-Check Before Output

Verify before finalizing:

  • Every uncertain field marked [不确定] or [未明确给出]
  • Every contribution tagged [原文声明] or [模型归纳]
  • No section silently omitted — skipped sections state why
  • Paper type label matches rubric evidence

Anti-Hallucination Rules

Full rules in references/quality-checklist.md. Non-negotiable constraints:

  1. Source tagging: [原文声明] = directly stated in paper (cite location); [模型归纳] = inferred by model (state reasoning basis)
  2. Uncertainty: [未明确给出] when absent; [不确定] when ambiguous
  3. No domain assumption: classify paper type first, always
  4. No fabrication: venue, DOI, year, affiliations not in text → [未明确给出]
  5. Evidence binding: each contribution must cite section/figure/table/quote
  6. Degraded PDF: state which sections were unreadable; do not fill gaps

Degraded Input Fallback

SituationAction
Only abstract availablequick mode, note limitation
Scanned PDF, no textAsk user for text or OCR first
Missing references sectionSkip prior work analysis, note absence
Figures unreadableSkip figure analysis, note absence
Non-English paperTranslate key sections, note source language

Extended Mode: Author Prior Work

Only in extended mode:

  1. Extract all author names from paper
  2. Identify self-citations in reference list (shared authors)
  3. Infer research group focus from affiliations + paper title
  4. List prior works from reference list only — no web search, no external knowledge
  5. Tag all output: [基于论文内引用,非外部检索]
  6. If insufficient info: explicitly state "信息不足,无法判断前作关系"

Presentation Mode: PPT Generation

Only in presentation or presentation_with_figures mode.

Step A: Collect Overrides

Before building the slide plan, check if the user specified any of:

  • audience (lab / conference / general) — default: lab
  • duration_hint (10min / 20min / 30min) — default: 20min
  • talk_style (technical / overview / discussion) — default: technical
  • emphasis (which sections to expand)
  • skip (which sections to omit)

If not specified, use defaults silently.

Step B0: Extract PDF Figures (presentation_with_figures only)

Before building the slide plan, run:

python scripts/extract_pdf_figures.py <pdf_path>

This saves all figures to figures/ and writes figures/index.json with name, path, and page for each image. Use this index when assigning figure_ref paths in the handoff.

Step B: Build Slide Plan

Follow references/presentation-schema.md for structure. Follow references/presentation-style-guide.md for compression rules.

  • Map each slide role to the corresponding output-schema section
  • Apply user overrides (emphasis → expand, skip → omit)
  • For presentation_with_figures: set figure_needed: true on method/result slides where a figure is the primary evidence; add figure_ref and figure_hint
  • Slide count from duration_hint (10min→6-7, 20min→9-10, 30min→12-14)

Step C: Call pptx Skill

Follow references/pptx-handoff.md for the exact handoff format.

  • Strip all [原文声明] / [模型归纳] tags before passing to pptx
  • Do NOT include speaker notes in the handoff
  • Call pptx skill automatically — do not ask the user first
  • Exception: if user said "只要大纲" / "just the outline", output the slide plan as text and skip pptx

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.