[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV47PD0PWAHVZ5GFVQRHDH":3,"skill-same:01M7EV47PD0PWAHVZ5GFVQRHDH":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EV47PD0PWAHVZ5GFVQRHDH","ams-note-taker",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-note-taker\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: note-taker\ndescription: 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.\ncategory: productivity\n---\n\n# Note Taker\n\n## Overview\n\nMost notes are written and never read — expensive theater. Good note-taking is thinking on paper, not transcription.\n\nThree jobs: capture (don't lose it), think (understand it), retrieve (find it later).\n\nDifferent situations need different methods: meetings need decisions and actions, lectures need structure, reading needs your own words.\n\nThe value isn't in the notes — it's in the processing. A messy note you rewrite beats a pretty note never revisited.\n\nAfter capture, a short processing step converts raw notes into durable knowledge and extracted actions.\n\n## When to use\n\n- Preparing for meetings, classes, interviews, user research, or conferences\n- Taking notes while reading books, papers, or long articles\n- Building a reusable personal knowledge base from notes\n- Teaching others effective note-taking or setting team norms\n\n## Core concepts\n\n- **Selective capture.**\n  You can't write everything and think simultaneously. Capture decisions, actions, numbers, quotes, questions, disagreements — plus your reactions.\n- **Cornell method.**\n  Cues left, notes right, summary bottom. Review by covering notes and recalling from cues — active recall built in.\n- **Outline method.**\n  Hierarchical bullets for structured content. Fast, scannable, maps well to digital outliners.\n- **Mind mapping.**\n  Spatial, non-linear capture for brainstorming. Structure emerges visually; great for connecting disparate ideas.\n- **Fleeting -> permanent notes.**\n  Capture messy and fast; within 24 hours rewrite keepers in your own words. The rewrite is where learning happens.\n- **Meeting note anatomy.**\n  Date, attendees, purpose, key points, decisions, action items (owner + date each), open questions.\n- **Progressive summarization.**\n  Bold key passages -> highlight the best of those -> summarize the highlights -> distill to one line. Each pass compresses understanding.\n- **Your words or it didn't happen.**\n  Restating in your own words is minimum viable learning. Highlighting without restating is the illusion of learning.\n\n## Practical workflow\n\n1. **Prepare with a purpose line.**\n   Write the goal at the top: 'Decide X', 'Understand Y'. A note with a purpose stays focused; a blank page invites transcription.\n2. **Choose the method.**\n   Structured content -> outline. Discussion -> Cornell. Reading -> margin notes + chapter summary. Brainstorm -> mind map.\n3. **Capture live, mark actions.**\n   Short phrases, abbreviations, your words. Mark actions distinctly (`[ ] Name — task — date`), questions with `?`.\n4. **Process within 24 hours.**\n   Fix shorthand while memory is fresh, extract actions to your task system, bold key points, write a 3-line summary on top.\n5. **Connect each note.**\n   Link to related notes, projects, people — one link minimum. Isolated notes are forgotten notes.\n6. **File or archive.**\n   Move to the right place. Archive ruthlessly; 200 unprocessed notes is a graveyard, not a system.\n7. **Review on schedule.**\n   Weekly: scan recent notes for missed actions. Monthly: re-read summaries — spaced repetition for your own knowledge.\n8. **Share meeting notes fast.**\n   Decisions and owners highlighted, shared within 24 hours. Write for the skimmer: decisions first, details after.\n\n## Common pitfalls\n\n- **Transcription mode.**\n  Capturing every word means understanding none. Notes should be sparser than the source.\n- **Never processing.**\n  Raw notes decay fast; unprocessed notes older than a week are nearly worthless. Schedule processing time.\n- **No action extraction.**\n  Meeting notes without owners and dates are fiction. Extract actions before closing the note, every time.\n- **Copy-paste 'notes'.**\n  Highlighting without restating teaches nothing. Add at least one sentence in your own words per source.\n- **One giant document.**\n  A 50-page running doc is unsearchable. Split by meeting\u002Ftopic; title each clearly with a date.\n- **Pretty over useful.**\n  Formatting during the meeting instead of listening. Ugly notes processed later beat beautiful notes never reviewed.\n- **No retrieval plan.**\n  Notes in five apps with no naming convention can't be found. One home, consistent titles, search you trust.\n- **Notes nobody reads.**\n  Unshared meeting notes may as well not exist. If it isn't shared within 24h with decisions up top, it didn't happen.\n","# Note Taker\n\n## Overview\n\nMost notes are written and never read — expensive theater. Good note-taking is thinking on paper, not transcription.\n\nThree jobs: capture (don't lose it), think (understand it), retrieve (find it later).\n\nDifferent situations need different methods: meetings need decisions and actions, lectures need structure, reading needs your own words.\n\nThe value isn't in the notes — it's in the processing. A messy note you rewrite beats a pretty note never revisited.\n\nAfter capture, a short processing step converts raw notes into durable knowledge and extracted actions.\n\n## When to use\n\n- Preparing for meetings, classes, interviews, user research, or conferences\n- Taking notes while reading books, papers, or long articles\n- Building a reusable personal knowledge base from notes\n- Teaching others effective note-taking or setting team norms\n\n## Core concepts\n\n- **Selective capture.**\n  You can't write everything and think simultaneously. Capture decisions, actions, numbers, quotes, questions, disagreements — plus your reactions.\n- **Cornell method.**\n  Cues left, notes right, summary bottom. Review by covering notes and recalling from cues — active recall built in.\n- **Outline method.**\n  Hierarchical bullets for structured content. Fast, scannable, maps well to digital outliners.\n- **Mind mapping.**\n  Spatial, non-linear capture for brainstorming. Structure emerges visually; great for connecting disparate ideas.\n- **Fleeting -> permanent notes.**\n  Capture messy and fast; within 24 hours rewrite keepers in your own words. The rewrite is where learning happens.\n- **Meeting note anatomy.**\n  Date, attendees, purpose, key points, decisions, action items (owner + date each), open questions.\n- **Progressive summarization.**\n  Bold key passages -> highlight the best of those -> summarize the highlights -> distill to one line. Each pass compresses understanding.\n- **Your words or it didn't happen.**\n  Restating in your own words is minimum viable learning. Highlighting without restating is the illusion of learning.\n\n## Practical workflow\n\n1. **Prepare with a purpose line.**\n   Write the goal at the top: 'Decide X', 'Understand Y'. A note with a purpose stays focused; a blank page invites transcription.\n2. **Choose the method.**\n   Structured content -> outline. Discussion -> Cornell. Reading -> margin notes + chapter summary. Brainstorm -> mind map.\n3. **Capture live, mark actions.**\n   Short phrases, abbreviations, your words. Mark actions distinctly (`[ ] Name — task — date`), questions with `?`.\n4. **Process within 24 hours.**\n   Fix shorthand while memory is fresh, extract actions to your task system, bold key points, write a 3-line summary on top.\n5. **Connect each note.**\n   Link to related notes, projects, people — one link minimum. Isolated notes are forgotten notes.\n6. **File or archive.**\n   Move to the right place. Archive ruthlessly; 200 unprocessed notes is a graveyard, not a system.\n7. **Review on schedule.**\n   Weekly: scan recent notes for missed actions. Monthly: re-read summaries — spaced repetition for your own knowledge.\n8. **Share meeting notes fast.**\n   Decisions and owners highlighted, shared within 24 hours. Write for the skimmer: decisions first, details after.\n\n## Common pitfalls\n\n- **Transcription mode.**\n  Capturing every word means understanding none. Notes should be sparser than the source.\n- **Never processing.**\n  Raw notes decay fast; unprocessed notes older than a week are nearly worthless. Schedule processing time.\n- **No action extraction.**\n  Meeting notes without owners and dates are fiction. Extract actions before closing the note, every time.\n- **Copy-paste 'notes'.**\n  Highlighting without restating teaches nothing. Add at least one sentence in your own words per source.\n- **One giant document.**\n  A 50-page running doc is unsearchable. Split by meeting\u002Ftopic; title each clearly with a date.\n- **Pretty over useful.**\n  Formatting during the meeting instead of listening. Ugly notes processed later beat beautiful notes never reviewed.\n- **No retrieval plan.**\n  Notes in five apps with no naming convention can't be found. One home, consistent titles, search you trust.\n- **Notes nobody reads.**\n  Unshared meeting notes may as well not exist. If it isn't shared within 24h with decisions up top, it didn't happen.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-note-taker",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-note-taker",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-note-taker",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-note-taker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-note-taker\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","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\u002FCSS, 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.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","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).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]