Skip to content

afeezadebayo/research-learning-skills / active-reading-notes

active-reading-notes

Verified

Read actively and take useful notes: a purpose and questions, previewing, reading depths from skim to study, questioning the text, recall instead of rereading, notes in your own words, accurate quotes and sources, summaries, linking notes to projects and reviewing them. Use whenever someone wants to read books, papers or reports more effectively, take better notes, remember what they read, summarise a book or turn reading into useful knowledge.

Active Reading and Notes

Most reading is wasted. People highlight, reread and close the book or article with little they can use a week later. A large review of learning techniques by John Dunlosky and colleagues rated highlighting and rereading as low-utility study methods, while practice testing and spaced practice rated high. [Research, Dunlosky et al. 2013] Active reading changes the goal from "getting through" a text to extracting what matters for a purpose, writing it in your own words and connecting it to what you already know, so the ideas can be found and used later.

This skill reads books, reports, papers and articles actively and turns them into useful notes: setting a purpose, previewing before reading, reading at the right depth, questioning the text, writing notes in your own words, capturing sources and quotes accurately, linking notes to projects and reviewing them so knowledge stays available.

Operating principles

  1. Read with a purpose. Know the question or use before you start.
  2. Preview first. Structure, summary and conclusions guide where to spend time.
  3. Match depth to value. Skim most, read some closely, study a few deeply.
  4. Write in your own words. Paraphrasing forces understanding; copying does not.
  5. Capture sources precisely. Page numbers and exact quotes when quoting.
  6. Connect and use. Notes link to projects, questions and other notes.

Reading depths

DepthWhat you doUse for
Skim (5 to 10 min)Title, summary, headings, figures, conclusionsDeciding whether to read; getting the gist
Read (30 to 60 min)Read key sections, note main arguments and evidenceMost work reading
Study (hours)Read fully, question, summarise, test yourselfCore sources, exams, deep expertise
Mortimer Adler and Charles Van Doren's How to Read a Book describes similar levels, from inspectional to analytical reading. [Reference, How to Read a Book]

When to use, and when not to

Use it for books, research papers, reports, long articles, documentation and course material you need to understand, apply or cite.

Don't apply deep note-taking to everything; most content only needs a skim and a one-line note or nothing at all.

Inputs

  • The text and why you are reading it.
  • Your note-taking tool (paper, notes app, Obsidian, Notion or similar).
  • Projects or questions the reading supports.
  • Time available.

Workflow

Step 1. Set the purpose

Write one or two questions you want the text to answer, or the decision it informs.

Step 2. Preview

Read the title, summary or abstract, contents, headings, figures and conclusions. Decide the depth.

Step 3. Read actively

Ask as you read: what is the main claim? What evidence supports it? Do I agree? How does it connect to what I know?

Step 4. Pause and recall

At the end of each section, close the text and write the key point from memory. This retrieval strengthens memory more than rereading.

Step 5. Write notes in your own words

One idea per note where possible, with the source and page.

Step 6. Capture quotes carefully

Only quotes you may use, exactly as written, with page numbers.

Step 7. Summarise

A short summary of the whole text: main argument, key evidence, your view and how you will use it.

Step 8. Connect

Link notes to projects, related notes and questions; tag by topic.

Step 9. Review and use

Revisit notes when working on related tasks; turn key ideas into flashcards if you need to remember them.

Note templates

Book or report summary

Title, author, year | Read: <date> | Depth: <skim/read/study>
Why I read it: <question>
Main argument (3 sentences, my words):
Key ideas (with pages):
1. ...
Evidence and examples:
What I disagree with or question:
How I will use it: <projects, actions>
Related notes: <links>

Single idea note

Idea: <one sentence in my words>
Explanation: <2 to 4 sentences>
Source: <author, title, page>
Links: <related ideas, projects>

Questions to ask while reading

  • What problem is the author solving?
  • What are the key terms, and how are they defined?
  • What is the strongest evidence, and what is missing?
  • What would someone who disagrees say?
  • What can I do differently because of this?

Reading a research paper in 20 minutes

  1. Title and abstract: what question and what answer?
  2. Figures and tables: what do the main results show?
  3. Conclusion and limitations: what do the authors claim and admit?
  4. Introduction: why does it matter, and what came before?
  5. Methods: only if you need to judge quality or reuse the approach. Write a five-line note: question, method, main finding, limitations, relevance to you.

Choosing what to read

Keep a reading list linked to goals and projects, not to everything that looks interesting. Before starting a book, skim the contents and a chapter; drop books that are not useful. Finishing everything you start is not a virtue when time is limited.

Notes systems

ApproachGood for
Summary per sourceQuick reference to what a book or report says
Idea notes linked together (often called a Zettelkasten)Building connected knowledge over years
Project notesCollecting what is needed for one deliverable
Many people combine all three: a summary per source, idea notes for key concepts and links into active projects.

Using AI while reading

Ask an AI assistant to explain a hard passage in plain words, generate questions to test your understanding or compare an author's argument with others. Write the final notes yourself, because explaining ideas in your own words is what builds understanding.

Review your notes monthly and delete what no longer helps.

Link each summary to at least one project.

Edge cases and judgement calls

SituationWhat to do
Very long reportsRead the summary and the sections that answer your questions
Dense academic papersAbstract, figures, conclusion first; then methods if needed
Reading for examsStudy depth plus self-testing and spaced review
Reading on screensUse annotation tools; export highlights then rewrite as notes
AI summariesUse as a preview; read key sections yourself before relying on them
Many sources on one topicSynthesis notes that compare authors

Handoffs to related skills

  • Remembering what you read: spaced-repetition
  • Explaining to understand: explain-to-learn
  • Learning plans: learning-plans
  • Literature reviews: literature-review
  • Knowledge management systems: the Knowledge Management skills

Worked example

A growth manager read business books but remembered little. She started writing one question before each book, previewing chapters, writing a three-sentence summary after each chapter from memory and creating one idea note per useful concept, linked to current projects. A book on pricing produced eight idea notes, two of which shaped a pricing test the following month. Six months later her notes held over 200 linked ideas she could search and reuse in proposals and talks.

Common mistakes

  • Reading without a purpose.
  • Highlighting and rereading instead of recalling.
  • Copying text instead of paraphrasing.
  • No page numbers for quotes.
  • Notes that are never connected or used.

Output format

1. Purpose and questions
2. Chosen reading depth
3. Notes (summary and idea notes)
4. Quotes with pages
5. Links to projects and other notes
6. Follow-up actions and review plan

Self-check before you answer

  • Is there a clear purpose for reading?
  • Are notes in your own words with sources and pages?
  • Did you recall key points from memory?
  • Are notes linked to projects or questions?

Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/productivity/research-learning/active-reading-notes/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 114kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 114kUpdated Claude CodeCodexVerifiedInstall