literature-reading

Installation
SKILL.md

Literature interpretation

Use this Skill after paper-reading has produced a local MinerU publication. Work from the parsed Markdown, metadata.json, and linked assets with the host's local file, search, and image-viewing capabilities. Do not invent a separate reading or analysis MCP tool.

Defaults

  • Unless the user asks about a specific question, section, figure, table, or equation, perform a complete professional interpretation of the paper.
  • Return the interpretation in the conversation by default. Write a Markdown file only when the user requests one or the result is too long to remain useful in chat.
  • Follow the user's language and desired depth. Preserve titles, identifiers, formulas, units, sample names, and technical terms when translation could change their meaning.

Workflow

  1. Confirm the paper from the Markdown frontmatter and metadata.json, including title, Zotero key, DOI when present, and selected attachment. If no readable parsed publication is available, return to paper-reading instead of reconstructing the paper from metadata or memory.
  2. Map the document structure first: headings, captions, tables, equations, and image links. Then read progressively so long papers do not overflow the working context.
  3. For a complete interpretation, cover every substantive section, normally including the abstract, background, research question, methods or argument, results, discussion, limitations, and conclusion. Do not treat the abstract and conclusion as a substitute for the full paper.
  4. Explain the paper's problem, approach, critical conditions or assumptions, main evidence, quantitative results, reasoning, contribution, limitations, applicability, and unresolved questions. Adapt these dimensions to the paper rather than forcing a fixed report template.
  5. Attach reproducible source locators to important claims: relative Markdown filename, section heading, stable line range or identifying phrase, and figure/table/equation identifier when relevant. Keep conditions, units, comparison direction, and reported uncertainty with numerical results.
  6. Distinguish paper evidence, the authors' own interpretation, the Agent's interpretation, and uncertainty. Mark missing information as unreported or unavailable; do not fill it from general knowledge.
Installs
4
GitHub Stars
5
First Seen
Sep 21, 2026