# Related Paper Analyzer

Collect and analyze relevant papers, reports, and reference methods to inform method...

- Repository: https://github.com/zhnnky329/MathModeling-skills (1073 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-09-24
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add zhnnky329/MathModeling-skills --skill related-paper-analyzer -g -a claude-code -y`
Codex: `npx skills add zhnnky329/MathModeling-skills --skill related-paper-analyzer -g -a codex -y`
Cursor: `npx skills add zhnnky329/MathModeling-skills --skill related-paper-analyzer -g -a cursor -y`
Gemini CLI: `npx skills add zhnnky329/MathModeling-skills --skill related-paper-analyzer -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add zhnnky329/MathModeling-skills`

## Description

Collect and analyze relevant papers, reports, and reference methods to inform method selection without fabricating references or copying models blindly.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Purpose

Analyze user-provided papers and reports before final method selection.

This skill checks whether the user has placed original paper files under `workspace/papers/`, reads those originals, and extracts transferable method cues, assumptions, variables, validation ideas, and limitations for the current subquestions.

This skill does not fabricate references, browse for new papers, write the final method card, or copy a published model blindly.

# When to use

Use this skill:

- After `problem-parser` and `problem-classifier` have produced validated artifacts.
- Before `method-selector`.
- When the team wants to ground method selection in user-supplied literature rather than guessing from model names.
- When original papers, reports, or extracted paper text are available under `workspace/papers/`.

# Preconditions

The following should already exist or be provided:

- A validated problem parse.
- A validated problem classification artifact.
- At least one original paper file under `workspace/papers/`.

If no paper originals are present under `workspace/papers/`, stop and remind the user to place them there before analysis begins.

# Inputs

Use or request:

- `workspace/problem/problem-parser/problem_parse.json`, if available.
- `workspace/problem/problem-classifier/problem_classification.json`, if available.
- Original paper files under `workspace/papers/`.
- User notes about which papers matter most, if available.

# Workflow

1. Check `workspace/papers/` first.
   - Look for user-supplied paper originals or extracted paper text.
   - Accept formats such as `.pdf`, `.docx`, `.md`, `.txt`, or clearly named extracted text files.
   - Ignore `workspace/papers/related_paper_analysis.md` if it already exists.

2. Stop early if the paper folder is empty.
   - If no paper originals are found, tell the user to place the paper originals under `workspace/papers/`.
   - Do not fabricate literature summaries from memory.

The rest: https://github.com/zhnnky329/MathModeling-skills/blob/HEAD/.claude/skills/related-paper-analyzer/SKILL.md