Take notes that you'll actually use: methods for meetings, lectures, reading, and research, plus processing workflows. Use when improving how you capture and retain information from any source.
Scanned 9/29/2026
npx -y skills add aicodedecode/awesome-muse-skills --skill note-taker --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Note Taker?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aicodedecode-note-taker)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: note-taker
description: Take notes that you'll actually use: methods for meetings, lectures, reading, and research, plus processing workflows. Use when improving how you capture and retain information from any source.
category: productivity
---
# Note Taker
## Overview
Most notes are written and never read — expensive theater. Good note-taking is thinking on paper, not transcription.
Three jobs: capture (don't lose it), think (understand it), retrieve (find it later).
Different situations need different methods: meetings need decisions and actions, lectures need structure, reading needs your own words.
The value isn't in the notes — it's in the processing. A messy note you rewrite beats a pretty note never revisited.
After capture, a short processing step converts raw notes into durable knowledge and extracted actions.
## When to use
- Preparing for meetings, classes, interviews, user research, or conferences
- Taking notes while reading books, papers, or long articles
- Building a reusable personal knowledge base from notes
- Teaching others effective note-taking or setting team norms
## Core concepts
- **Selective capture.**
You can't write everything and think simultaneously. Capture decisions, actions, numbers, quotes, questions, disagreements — plus your reactions.
- **Cornell method.**
Cues left, notes right, summary bottom. Review by covering notes and recalling from cues — active recall built in.
- **Outline method.**
Hierarchical bullets for structured content. Fast, scannable, maps well to digital outliners.
- **Mind mapping.**
Spatial, non-linear capture for brainstorming. Structure emerges visually; great for connecting disparate ideas.
- **Fleeting -> permanent notes.**
Capture messy and fast; within 24 hours rewrite keepers in your own words. The rewrite is where learning happens.
- **Meeting note anatomy.**
Date, attendees, purpose, key points, decisions, action items (owner + date each), open questions.
- **Progressive summarization.**
Bold key passages -> highlight the best of those -> summarize the highlights -> distill to one line. Each pass compresses understanding.
- **Your words or it didn't happen.**
Restating in your own words is minimum viable learning. Highlighting without restating is the illusion of learning.
## Practical workflow
1. **Prepare with a purpose line.**
Write the goal at the top: 'Decide X', 'Understand Y'. A note with a purpose stays focused; a blank page invites transcription.
2. **Choose the method.**
Structured content -> outline. Discussion -> Cornell. Reading -> margin notes + chapter summary. Brainstorm -> mind map.
3. **Capture live, mark actions.**
Short phrases, abbreviations, your words. Mark actions distinctly (`[ ] Name — task — date`), questions with `?`.
4. **Process within 24 hours.**
Fix shorthand while memory is fresh, extract actions to your task system, bold key points, write a 3-line summary on top.
5. **Connect each note.**
Link to related notes, projects, people — one link minimum. Isolated notes are forgotten notes.
6. **File or archive.**
Move to the right place. Archive ruthlessly; 200 unprocessed notes is a graveyard, not a system.
7. **Review on schedule.**
Weekly: scan recent notes for missed actions. Monthly: re-read summaries — spaced repetition for your own knowledge.
8. **Share meeting notes fast.**
Decisions and owners highlighted, shared within 24 hours. Write for the skimmer: decisions first, details after.
## Common pitfalls
- **Transcription mode.**
Capturing every word means understanding none. Notes should be sparser than the source.
- **Never processing.**
Raw notes decay fast; unprocessed notes older than a week are nearly worthless. Schedule processing time.
- **No action extraction.**
Meeting notes without owners and dates are fiction. Extract actions before closing the note, every time.
- **Copy-paste 'notes'.**
Highlighting without restating teaches nothing. Add at least one sentence in your own words per source.
- **One giant document.**
A 50-page running doc is unsearchable. Split by meeting/topic; title each clearly with a date.
- **Pretty over useful.**
Formatting during the meeting instead of listening. Ugly notes processed later beat beautiful notes never reviewed.
- **No retrieval plan.**
Notes in five apps with no naming convention can't be found. One home, consistent titles, search you trust.
- **Notes nobody reads.**
Unshared meeting notes may as well not exist. If it isn't shared within 24h with decisions up top, it didn't happen.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!