ams-note-taker
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
03 SKILL.md 正文
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
- 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.
- Choose the method. Structured content -> outline. Discussion -> Cornell. Reading -> margin notes + chapter summary. Brainstorm -> mind map.
- Capture live, mark actions.
Short phrases, abbreviations, your words. Mark actions distinctly (
[ ] Name — task — date), questions with?. - 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.
- Connect each note. Link to related notes, projects, people — one link minimum. Isolated notes are forgotten notes.
- File or archive. Move to the right place. Archive ruthlessly; 200 unprocessed notes is a graveyard, not a system.
- Review on schedule. Weekly: scan recent notes for missed actions. Monthly: re-read summaries — spaced repetition for your own knowledge.
- 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.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).