skills/research-learning-knowledge/paper-workbench/SKILL.md
Researcher-profile-driven paper intake and literature workbench for academic workflows. Use this whenever the user wants to skim, deep-read, card, compare, synthesize, map research gaps, or build a literature review from papers, arXiv/AlphaXiv links, DOIs, PDFs, landing pages, or existing paper JSON / workbench artifacts. Normalize sources into `paper-record`, then route into scan, deep-read, card, synthesis, review, or compatibility modes (`json`, `interpret`, `xray`). Trigger even when the user only says things like “精读这篇”, “整合这几篇”, “找研究空白”, or “搭综述框架”.
npx skillsauth add bahayonghang/my-claude-code-settings paper-workbenchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Unified entrypoint for paper intake, strategic reading, multi-paper synthesis, and review construction.
Keep paper-record as the normalization layer. Do not merge high-level
analysis back into the normalized record.
In the
pythoncommands below,<skill-dir>is this skill's base directory, announced when the skill loads. Substitute that literal path; it is not an environment variable. Bundled scripts self-locate, so only the path needs to resolve.
Use this skill when the job is to:
Do not use this skill when the primary job is to implement a paper from its methods into working code. That implementation work is out of scope for this skill.
paper-record — normalized single-paper factsresearcher-profile — user research anchorpaper-deep-read — single-paper strategic analysis artifactliterature-synthesis — cross-paper integration artifactreview-outline — literature-review planning artifactdoi.org/... URLspaper-record JSONresearcher-profile, paper-deep-read, literature-synthesis, or
review-outline JSON$ARGUMENTS, the latest user message, or a
pasted JSON artifact.scripts/normalize_paper.py first.researcher-profile or collect only the missing fields.scan
deep-read
card
interpret
xray
json
paper-recordsynthesis
review
jsonscansynthesissynthesis and mark any gap mapping as provisionalFor any paper-like input, run:
python "<skill-dir>/scripts/normalize_paper.py" \
--source "<paper-source>" \
--lang "<lang>" \
--fulltext "<auto|prefer|never>"
Use --save only when the user asked to persist the normalized JSON.
Before deep-read, card, synthesis, or review, prefer a
researcher-profile.
If missing, collect only these fields:
research_fieldcore_questionthesis (optional)target_tierstageIf the user clearly wants no back-and-forth, proceed with a generic profile-light analysis and explicitly mark that personalization is limited.
If the user wants persistence, create or update the profile with:
python "<skill-dir>/scripts/workbench_io.py" init-profile \
--path "<profile-path>" \
--research-field "<field>" \
--core-question "<question>" \
--thesis "<optional-thesis>" \
--target-tier "<target-tier>" \
--stage "<stage>"
When the user asks to save a deep read, synthesis, or review plan, write a JSON artifact plus an optional Markdown or Org sidecar:
python "<skill-dir>/scripts/workbench_io.py" save-artifact \
--workspace "<workspace-dir>" \
--artifact-type "<paper-deep-read|literature-synthesis|review-outline>" \
--title "<artifact-title>" \
--payload-file "<json-payload-file>" \
--profile-path "<optional-profile-path>" \
--source-record "<path-to-paper-record>" \
--sidecar-file "<optional-md-or-org>"
作者观点 from 系统分析[信息待核实]synthesis and review must integrate arguments across papers rather than
serially summarizing each paperreview paragraphs must use PEEL as a micro-argument structure, not a
citation listdeep-read:
references/routing.md — source classification and routing logicreferences/schema.md — canonical paper-record contractreferences/artifacts.md — researcher-profile and higher-level artifactsreferences/migration.md — compatibility and alias mappingreferences/ANALYSIS_FRAMEWORK.md — x-ray five-dimension critique frameworkreferences/template-paper.org — Org sidecar template for deep-read / interpret outputreferences/template-xray.org — Org sidecar template for x-ray critique outputreferences/modes/json.md — machine-readable output rulesreferences/modes/interpret.md — lightweight explanation pathreferences/modes/xray.md — compact critique pathreferences/modes/scan.md — single-paper quick triagereferences/modes/deep-read.md — full single-paper deconstructionreferences/modes/card.md — literature card onlyreferences/modes/synthesis.md — cross-paper integrationreferences/modes/review.md — literature-review planning and writingtools
文献深度解读助手,像研究生导师一样交互式解读 Zotero 库中的学术论文,面向计算机科学、深度学习、自动化等方向(个人向)。当用户提供文献题目、DOI、PDF 或要求解读某篇论文时触发,通过 Zotero MCP 优先获取全文,并根据用户意图自动选择快速筛选、导师深读或研究复盘模式。完整深读时先完成叙事类型判断、阅读前预检、novelty 校准和作者思考路径重建,再整体概览,并基于图例、正文和表格逐图详细解读(Zotero MCP 无法提取 PDF 图片,解读基于文字信息,必要时提醒上传图片)。适用于:(1)快速判断文献是否值得深读 (2)深入理解某篇论文 (3)学习文章中的方法和技术 (4)批判性分析研究设计 (5)寻找研究灵感。需要多篇论文综合、对比或找研究空白,或 arXiv/DOI 批量规范化时,改用 paper-workbench。
development
Review Codex, Claude, OpenAI, or other agent skill directories as reusable capability packages. Use when asked to audit, review, improve, score, rewrite, debrand, package, or document a SKILL.md, skill package, marketplace skill, or agent skill directory, especially when the user wants a comprehensive findings-first report with concrete patch recommendations and validation steps.
development
Turn vague or complex Codex tasks into strong `/goal` commands with outcome, verification, constraints, boundaries, iteration policy, completion evidence, and pause/block conditions. Use when the user asks for Codex goal instructions, Goal 指令, 目标指令, `/goal` prompts, 中文 Goal 模板, plan-to-goal interviews, success criteria, verification commands, or bounded agent work definitions.
tools
Write, debug, and validate ast-grep structural code search rules. Use this skill when the user needs syntax-aware code search, AST pattern matching, structural refactor discovery, language-construct queries, or searches that plain text tools like rg can miss, such as finding functions with particular descendants, calls inside specific contexts, missing error handling, React hook shapes, decorators, or other Tree-sitter-backed code structures.