Help us improve
Share bugs, ideas, or general feedback.
From grimoire
Applies Cornell Notes method to capture lecture or reading notes in a structured three-section format that builds review and retrieval practice.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireHow this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:apply-cornell-notesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Divide your note page into three sections — right column for real-time capture, left column for review questions written after, and a bottom summary written from memory — building retrieval practice directly into the note-taking workflow without requiring a separate study session.
Generates learning notes from conversations: Classic mode for concise recaps, Mastery for detailed rules, misconceptions, and Core Loop code history. Supports Korean/English with beginner-friendly terms.
Design study strategies and instructional activities that use testing and recall to strengthen long-term memory through retrieval practice.
Crawls online course pages to extract lecture schedules, slides, and videos, then synthesizes structured vault notes per lecture. Also refines existing course notes.
Share bugs, ideas, or general feedback.
Divide your note page into three sections — right column for real-time capture, left column for review questions written after, and a bottom summary written from memory — building retrieval practice directly into the note-taking workflow without requiring a separate study session.
Adopted by: AVID (Advancement Via Individual Determination) mandates Cornell Notes as its core note-taking system across 6,000+ schools in all 50 US states, serving approximately 650,000 students annually — the largest structured academic readiness program in the United States. Taught in academic skills programs at Cornell University, Penn State, University of Arizona, University of Edinburgh, and the majority of US and UK university learning centers. Walter Pauk's "How to Study in College" — the canonical study skills textbook, 10 editions over 50 years — describes and advocates Cornell Notes throughout. Impact: Hattie's Visible Learning (2009, 800+ meta-analyses) rates note-taking strategies at effect size ~0.44, above the 0.40 meaningful-intervention threshold. Williams & Eggert (2002) meta-analysis of note-taking research found that organized, review-oriented note-taking (the Cornell model) consistently outperforms linear transcription for retention on assessments. The cue column mechanism is a direct implementation of retrieval practice: Roediger & Karpicke (2006) demonstrated that a single retrieval attempt produces 50% better long-term recall than re-studying for equal time. Pauk's key insight — that the review cue questions must be written after, not during, the lecture — forces active reformulation that encodes material more deeply than transcription. Why best: Linear note-taking (writing everything in sequence) is efficient for capture but creates no built-in review mechanism — the notes sit unused until exam time. Cornell Notes does what linear notes cannot: it forces active review within 24 hours (cue column), builds a retrieval practice routine (cover the notes, answer from cues), and requires summary synthesis (bottom strip). The alternative — taking linear notes and then making flashcards or summaries separately — requires a separate study session that most learners skip. Cornell Notes makes the review non-optional: the cue column is blank until you fill it, which creates visible incompleteness that drives completion.
Sources: Walter Pauk (1962, 2013); AVID methodology; Hattie (2009) "Visible Learning"; Williams & Eggert (2002); Roediger & Karpicke (2006)
Divide every note page into three regions before the lecture or reading session:
┌─────────────────────────────────────────────────────┐
│ CUE COLUMN │ NOTES COLUMN │
│ (~2.5 in / 30%) │ (~6 in / 60–65%) │
│ │ │
│ [Fill in AFTER] │ [Capture DURING] │
│ │ │
│ │ │
│ │ │
│ │ │
├──────────────────────┴──────────────────────────────┤
│ SUMMARY STRIP (~2 in / bottom of page) │
│ [Write from memory AFTER reviewing cues] │
└─────────────────────────────────────────────────────┘
For digital note-taking: use a two-column table (30%/70%) with a merged footer row. In Notion, OneNote, or Obsidian: create templates with this structure so setup time is zero.
Write in the right column only. Rules:
? in the margin — do not stop to resolve during captureExample (lecture on HTTP caching):
Cache-Control header — tells browser how to cache
max-age=3600 → browser can use cached copy for 1hr
no-store → never cache (sensitive data)
must-revalidate → check with server before using expired cache
ETag — fingerprint of resource content
server sends ETag in response
browser sends If-None-Match on next request
if unchanged: 304 Not Modified (no body sent) → faster
? When does browser decide cache is "stale"?
Do NOT fill the cue column during capture. The right column is for raw notes; the left is for later.
Within 24 hours of the lecture or reading session (before the next one):
Example (same notes):
CUE COLUMN │ NOTES COLUMN
─────────────────────────┼────────────────────────────────
What does Cache-Control │ Cache-Control header — tells
do? 3 key directives? │ browser how to cache
│ max-age=3600 → ...
─────────────────────────┼────────────────────────────────
What is ETag? How does │ ETag — fingerprint of resource
conditional GET work? │ content ...
─────────────────────────┼────────────────────────────────
Cue quality check: can you answer the cue question without looking at the right column? If not, rewrite the cue to be more specific.
At the bottom of each page, after completing the cues, write a 3–5 sentence summary of the page's content without looking at the notes:
Cache-Control and ETag are the two primary HTTP caching mechanisms. Cache-Control
sets policy for how long a response can be reused without checking the server;
no-store disables caching entirely for sensitive responses. ETags enable conditional
requests — the browser reuses its cached copy if the ETag matches, receiving a 304
Not Modified instead of a full response body.
If you cannot write the summary without looking at the notes, re-read the right column and try again. The inability to summarize reveals where understanding is incomplete.
For scheduled review (daily → weekly → spaced per your schedule):
✗✗ items: re-read the right column and reattempt from memory (not just re-read)Review session (5–10 min per page):
"What does Cache-Control do? 3 key directives?" → answer without looking
Uncover → verify → ✓ or ✗
"What is ETag? How does conditional GET work?" → answer without looking
Uncover → verify → ✓ or ✗
Items marked ✗ go into the next spaced repetition cycle (see apply-spaced-repetition).