literature-reader
Skill0 starsChanged 30 days agoMITView on GitHub
Read one or several academic papers in PDF form and produce a structured Chinese reading note. Two output modes: a detailed HTML report (including cross-paper comparison), or a three-part reading report suited to a Chinese submission or a supervisor briefing. Use when the user asks to read a paper, take literature notes, write a reading report, or review a reference. Chinese trigger words: 读这篇论文, 帮我看看这篇文献, 做文献笔记, 写读书报告, 文献阅读笔记, 看论文.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- wpsnote/wpsnote-skillstheir own version, first seen Apr 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- wpsnote/wpsnote-skills★ 184same 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
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 70
No subheadings or numbering inside the report
- Distinctive: line 100
Write the DOCX in one pass: write the content first, then write the DOCX once.
- Distinctive: line 113
Keep ecological terminology accurate.
≈ “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.
Files
User research direction: configurable in the body (for example "diversity of a given taxon in a given ecosystem"). The "relevance to my own research" section is written against that direction; when it is not configured, use a generic "implications for the work" instead.
Literature Reader
Two output modes, chosen automatically from the user's trigger words or set manually.
Mode selection
The trigger-word table lives in references/output-templates-zh.md. In short: a
reading-note request produces a structured HTML file; a reading-report request produces a
plain-text three-part report; an unqualified request defaults to HTML and the user can
switch it by asking for a reading report.
Mode 1: Detailed HTML report
Output
The HTML file is saved to the folder that holds the PDF. File naming is specified in
references/output-templates-zh.md.
Structure
The section tree for the single-paper note — and, when two or more PDFs are supplied, the
additional comparison report — is in references/output-templates-zh.md. The headings
themselves are written in Chinese.
Cover, in order: basic information (title, authors, year, journal, DOI), research background, scientific question, methods summary (design, techniques, statistics, sample size), key quantitative results, conclusions and novelty, limitations, and finally the relevance-to-your-own-research block.
The relevance block must cover at least three of these five angles: method transfer, citable data, mechanistic insight, filling a stated gap, and framework crossover.
HTML styling
- Card layout, CSS inlined, no external resources
- Soft professional palette, Chinese fonts prioritised
- Key terms bold or highlighted, alternating row shading in tables
- Responsive (desktop and mobile)
Mode 2: Three-part reading report
Output
Plain text, ready to paste into Word or hand to a supervisor.
Paragraph structure
The three-part, two-part and review-paper variants, the required opening phrasings for
each paragraph, and the style rules (paragraph count, citation format, fonts, sentence
length) are all in references/output-templates-zh.md.
Key constraints:
- Results must be quantified (numbers, percentages, trend words)
- Short sentences separated by full stops
- No subheadings or numbering inside the report
- The second paragraph must carry both a transferable method and an explicit link to the user's own research
- Priority in the final paragraph: transfer > implication > limitation; limitations are optional
Selecting method highlights
Pick two or three, in priority order: direct relevance to the user's own topic; novel experimental design or statistics; data acquisition route; novel quantitative index or calculation; novel angle on the scientific question.
Workflow
- Confirm the PDF path and decide the mode (HTML or reading report)
- Extract the PDF content
- Pull the information into the template for the chosen mode
- Generate the output (HTML file or plain text)
- The relevance section must be written against the user's own research direction, or as a generic "implications for the work" when none is configured
Efficiency rules (highest priority)
- Extract the PDF in one pass: pull the full text or the key results pages (5 pages or fewer) at once; do not work through it page by page over several rounds
- Do not trace every number back: once you have enough from the PDF, write the report; do not then re-search the PDF to verify each value. A source annotation is enough — no per-number grep
- Write the DOCX in one pass: write the content first, then write the DOCX once; do not repeatedly clear and rebuild it
- Keep the whole job to 3–5 tool calls: extract PDF (1) → write DOCX (1) → final check (1, optional)
Notes
- Scientific accuracy first: stay strictly with the PDF text; never add content that is not in the source
- Mark anything that cannot be extracted as not stated in the source, or as insufficient information
- Keep ecological terminology accurate; retain the English term where that is the correct usage
- The relevance section must not be a generic template — cover at least three of the five angles for every paper
- Review papers may focus on field progress and the gaps that remain
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
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.

