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/feynman.md

View on GitHub
# Feynman Comprehension Loop

Use this reference for `feynman` mode. The objective is to expose and repair understanding gaps through retrieval, not to produce childlike wording for its own sake.

## Procedure

1. **Set the target** — name the idea, mechanism, or chapter-level claim to learn.
2. **Read for structure** — identify the central claim, key terms, mechanism, and evidence.
3. **Close the source** — do not look at the text or analysis notes.
4. **Explain from memory** — use plain language and preserve causal or logical links.
5. **Mark uncertainty** — tag every vague phrase, skipped step, undefined term, or appeal to jargon.
6. **Locate the first broken link** — find the earliest point where the explanation stops being justified.
7. **Return narrowly** — reread only the material needed to repair that gap.
8. **Rewrite the explanation** — replace jargon with a mechanism, concrete example, or boundary condition.
9. **Test transfer** — apply the idea to a new case and predict what should happen.
10. **Test contrast** — explain a case where the idea should not apply.
11. **Schedule retrieval** — create short recall prompts for later review.

## Gap Types

- **Definition gap** — a term cannot be explained without repeating itself.
- **Mechanism gap** — steps are listed but causality or logic is missing.
- **Evidence gap** — the claim is remembered but its support is not.
- **Boundary gap** — the learner cannot say when the claim fails.
- **Transfer gap** — the learner repeats the source but cannot use the idea elsewhere.

## Output Template

```markdown
## Learning target
[One precise concept or claim]

## Closed-book explanation
[Plain-language explanation reconstructed from memory]

## Detected gaps
- [Gap type]: [specific missing link]

## Corrected explanation
[Repaired explanation with the missing mechanism or evidence]

## Transfer test
[New scenario and predicted outcome]

## Boundary test
[Scenario where the idea should not apply]

## Recall prompts
1. [Question that retrieves the central mechanism]
2. [Question that retrieves evidence]
3. [Question that retrieves a limitation]
```

## Quality Rules

- Simplicity must not delete an essential condition.
- An analogy must identify where the analogy breaks.
- Reopening the source before attempting retrieval invalidates the gap test.
- Recognition (`this looks familiar`) is not recall (`I can reconstruct it`).
- Review questions should retrieve relationships and mechanisms, not isolated vocabulary.

## Sources

1. Adler, M. J. & Van Doren, C. — *How to Read a Book* (rev. ed., 1972) — the analytical-reading stages this workflow's deep mode follows.
2. Gleick, J. — *Genius: The Life and Science of Richard Feynman* (1992) — primary biographical account of Feynman's learn-by-teaching notebook practice.
3. Farnam Street — "The Feynman Technique: The Best Way to Learn Anything" (fs.blog/feynman-technique) — the canonical four-step formulation used here.
4. Karpicke, J. D. & Roediger, H. L. — "The Critical Importance of Retrieval for Learning", *Science* 319 (2008) — evidence that recall attempts, not re-reading, drive retention.
5. Dunlosky, J. et al. — "Improving Students' Learning With Effective Learning Techniques", *Psychological Science in the Public Interest* 14 (2013) — rates practice testing and self-explanation as highest-utility techniques, re-reading as low-utility.
6. Chi, M. T. H. et al. — "Self-Explanations: How Students Study and Use Examples", *Cognitive Science* 13 (1989) — the self-explanation effect behind the teach-back step.
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