thinkreader-summary
Skill42 starsChanged 2 months agoMITView on GitHub
Create a fixed four-part paper summary whose claims link back to precise PDF evidence. Use only for /summary.
In this repository8 other files it gives its agents.
- thinkreader-annotationSkill
- abzu-app-controlSkill
- audit-skillSkill
- abzu-codebaseSkill
- abzu-mindmapSkill
- abzu-reportSkill
- abzu-slidesSkill
- abzu-wikiSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 8
Create one concise Markdown document for the whole paper.
- Distinctive: line 17
Always read rules.md and the App's Summary writer rule supplied with this Skill.
- Distinctive: line 23
Run in the same native conversation as reading and annotations.
- Distinctive: line 34
Keep uncovered evidence in the summary citations.
≈ “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
ThinkReader evidence-linked summary
Create one concise Markdown document for the whole paper. Read the PaperMap first, then the complete EvidenceIndex by section. Use paper evidence only. The reading surface is a narrow sidebar beside the PDF: default to at most 1000 body units (Han characters or English words), excluding headings and evidence links. Long papers may extend slightly to about 1200. Explicit user length instructions override this target; short papers need less. This is writing guidance: do not count, rewrite, compress, truncate or reject a completed draft because of its length.
Always read rules.md and the App's Summary writer rule supplied with
this Skill. For research/survey, follow the four sections and their order for the
inferred type and selected language; other documents use a useful source-based structure.
The App's paper_id and EvidenceUnit
IDs are link targets, not prose.
Run in the same native conversation as reading and annotations. Infer the document
type from its actual evidence; do not ask for a separate JSON classification.
Reuse complete evidence already read in this task; use thinkreader_context for
the outline and missing evidence pages. Follow next_offset without clipping text.
Save with thinkreader_summary, not direct file writes or JSON in the final reply.
The output is a research aid: synthesize relationships across sections while
keeping every important claim one click away from the original PDF location.
Existing annotations are optional and never a prerequisite. The semantic pass does not
edit them. After commit, the App first appends the summary tag to an existing annotation
covering cited evidence, preserving its content, author, marks, hints, replies and layout.
Keep uncovered evidence in the summary citations; never create PDF cards for evidence bookkeeping.
Repeated runs must not multiply cards or tags; matching and tag writes are tool work, not extra LLM output.
Output language and document type
Use the language selected for the current task for ALL titles, headings, labels and prose. Chinese examples below illustrate semantics only; translate them for English output. For paper_type=other (fixtures, test pages and non-research material), choose a useful concise structure from the actual evidence instead of forcing a research/survey template. Never invent results to fill a template.
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.

