Skip to content

alirezarezvani/claude-skills / research/deepread

deepread

Verified

Use when the user asks to deeply read a book, article, PDF, or document set; extract claims and evidence; build a knowledge map; or learn through Feynman explanation and recall. Covers quick, deep, map, Feynman, and whole-book reading modes.

FileKindSize
.claude-plugin/plugin.jsonconfig777 B
SKILL.mdskill md8.0 KB
references/feynman.mdmarkdown3.5 KB
references/knowledge-map.mdmarkdown3.0 KB

references/knowledge-map.md

View on GitHub
# Evidence-Centered Knowledge Map

Use this reference for `map` mode. A useful map preserves reasoning, not just headings.

## Node Types

- `THESIS`: the central claim or explanatory model.
- `CLAIM`: a supporting or opposing proposition.
- `REASON`: a logical bridge between claims.
- `EVIDENCE`: an observation, quotation, record, or study.
- `DATA`: numerical evidence with unit, population, period, and baseline.
- `EXAMPLE`: an illustration that does not by itself establish generality.
- `CONCEPT`: a term whose definition matters to the argument.
- `ASSUMPTION`: an unstated premise.
- `COUNTERARGUMENT`: an alternative conclusion or explanation.
- `LIMITATION`: a boundary on scope or confidence.
- `QUESTION`: an unresolved issue or retrieval prompt.

## Edge Labels

Every edge must use a meaningful label: `supports`, `explains`, `defines`, `illustrates`, `depends on`, `qualifies`, `contradicts`, or `raises`.

Never use unlabeled proximity as a substitute for a relationship.

## Required Metadata

For evidence and data nodes, include:

- source location;
- the claim they connect to;
- confidence label;
- missing context or caveat.

## Markdown Output

```text
THESIS: [central claim]
├── supports → CLAIM: [supporting claim]
│   ├── because → REASON: [logical bridge]
│   ├── supports → EVIDENCE: [evidence] ([location])
│   └── qualifies → LIMITATION: [boundary]
├── depends on → ASSUMPTION: [unstated premise]
└── contradicted by → COUNTERARGUMENT: [strong alternative]
```

When the user requests FreeMind or XMind-compatible output, render the same hierarchy as valid FreeMind XML and escape all source-derived text used in XML attributes.

## Quality Check

Before delivering the map, verify:

1. Every major claim connects to the thesis.
2. Every evidence node connects to a specific claim.
3. Examples are labeled as examples.
4. Contradictions and limitations remain visible.
5. The map contains no conclusion that exists only because of layout.

## Sources

1. Novak, J. D. & Cañas, A. J. — "The Theory Underlying Concept Maps and How to Construct and Use Them" (IHMC CmapTools Technical Report, 2008) — the concept-mapping method this map structure derives from.
2. Toulmin, S. — *The Uses of Argument* (1958) — claim / grounds / warrant decomposition mirrored by the claim–reason–evidence fields.
3. Ahrens, S. — *How to Take Smart Notes* (2017) — atomic, linked notes as durable knowledge structure.
4. Adler, M. J. & Van Doren, C. — *How to Read a Book* (1972) — syntopical reading: mapping how multiple sources answer the same question.
5. Weinstein, Y., Madan, C. R. & Sumeracki, M. A. — "Teaching the Science of Learning", *Cognitive Research* 3 (2018) — elaboration and concrete-example strategies encoded in the map's link labels.
6. Hattie, J. & Donoghue, G. M. — "Learning Strategies: A Synthesis and Conceptual Model", *npj Science of Learning* 1 (2016) — where organization/mapping strategies help in the acquisition→consolidation cycle.
canvas-designanthropics/skillsCreate beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
docxanthropics/skillsUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pdfanthropics/skillsUse this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
pptxanthropics/skillsUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.Stars: 198kUpdated Claude CodeCodexVerifiedInstall