[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETG1RFPQC8Z3477EHTPRZZ":3,"skill-same:01M7ETG1RFPQC8Z3477EHTPRZZ":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},"01M7ETG1RFPQC8Z3477EHTPRZZ","ams-meeting-optimizer",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-meeting-optimizer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: meeting-optimizer\ndescription: Make meetings fewer, shorter, and better: agenda design, facilitation, async alternatives, and meeting audits. Use when calendars are full of low-value meetings or you're redesigning team collaboration norms.\ncategory: productivity\n---\n\n# Meeting Optimizer\n\n## Overview\n\nMeetings are the most expensive communication: everyone's time simultaneously, plus prep and recovery.\n\nMost run on autopilot: no agenda, wrong attendees, no decisions, no follow-through.\n\nOptimize = question each meeting (async instead?), design survivors, facilitate tightly, record decisions.\n\nGoal isn't zero meetings — it's meetings that earn their cost.\n\n## When to use\n\n- Team complains about too many meetings (or silently disengages in them)\n- Meetings run over, drift, or end without decisions\n- Designing meeting culture for a new team or company\n- Deciding between a meeting and an async alternative\n- Preparing to facilitate an important meeting well\n\n## Core concepts\n\n- **Purpose before scheduling.**\n  Decide, align, create, or connect. 'Sync' isn't a purpose — what decision or output justifies gathering everyone?\n- **The agenda is the meeting.**\n  Topics, owner per topic, timeboxes, pre-reads — shared 24h ahead. No agenda = permission to decline.\n- **Minimum viable attendees.**\n  Roles: decider, contributor, informed. Informed people get notes, not invites. Easier to add than to un-waste an hour.\n- **Async by default.**\n  Status, FYI, approvals, doc feedback, first-draft brainstorming — all better async: written, on your schedule, with a record.\n- **Decisions need records.**\n  Close every meeting: what was decided, owner, date. Share within hours. Unrecorded decisions get re-litigated.\n- **Timebox ruthlessly.**\n  25\u002F50 defaults, hard stops, visible parking lot. Ending 10 min early is a gift; overrun steals from the next commitment.\n- **Pre-reads, not presentations.**\n  Information transfer happens before, in writing. Meeting time is for questions, debate, decisions.\n- **Facilitator + note-taker.**\n  Separate roles, rotate them. Facilitator runs the agenda; note-taker captures decisions and actions live.\n\n## Practical workflow\n\n1. **Audit current meetings.**\n   List recurring meetings: purpose, attendees, frequency, cost (people x time x freq). Score: keep \u002F shorten \u002F async \u002F kill.\n2. **Apply the async test.**\n   'Could a doc + 48h of comments do this?' If yes, convert. Start with status meetings — almost always convertible.\n3. **Template the survivors.**\n   Decision meeting (options, recommendation, decision), weekly team (wins, priorities, blockers), 1:1 (their agenda first).\n4. **Set facilitation norms.**\n   Start on time regardless, timebox visibly, end 5 min early for action review. Rotate facilitation team-wide.\n5. **Run tight meetings.**\n   Open with purpose + desired outcome, work the agenda, park tangents visibly, close with decisions read back aloud.\n6. **Follow through fast.**\n   Notes within hours. Actions into task systems with dates — not left in the doc. Review open actions next time.\n7. **Re-audit quarterly.**\n   Every recurring meeting re-earns its slot. Kill liberally; calendars refill on their own if you let them.\n8. **Default to shorter.**\n   Change your defaults to 25\u002F50. Most 60-min meetings fit in 50; most 30-min in 25. The constraint sharpens discussion.\n\n## Common pitfalls\n\n- **Status meetings as docs-in-disguise.**\n  Written updates are faster to consume and searchable. The most convertible — and most common — waste.\n- **Inviting everyone 'just in case'.**\n  Twelve attendees, three talkers. Contributors get invites; everyone else gets notes.\n- **No pre-reads.**\n  Burning synchronous time on what could be read. Send materials early; start with questions.\n- **Decision-free endings.**\n  'Great discussion!' with no decision or owners. Even 'decide Tuesday with Sam's data' is a decision + owner + date.\n- **Back-to-back scheduling.**\n  No prep, debrief, or note capture. Buffers are hygiene, not luxury.\n- **Recurring meeting inertia.**\n  A 2022 weekly nobody would schedule today. Sunset it; let it be re-proposed with fresh purpose if needed.\n- **Camera theater.**\n  Mandating cameras without fixing purpose. Fix agenda and size first; engagement follows good design.\n- **No written record.**\n  Verbal decisions remembered differently by each attendee. Notes are the meeting's only durable output.\n","# Meeting Optimizer\n\n## Overview\n\nMeetings are the most expensive communication: everyone's time simultaneously, plus prep and recovery.\n\nMost run on autopilot: no agenda, wrong attendees, no decisions, no follow-through.\n\nOptimize = question each meeting (async instead?), design survivors, facilitate tightly, record decisions.\n\nGoal isn't zero meetings — it's meetings that earn their cost.\n\n## When to use\n\n- Team complains about too many meetings (or silently disengages in them)\n- Meetings run over, drift, or end without decisions\n- Designing meeting culture for a new team or company\n- Deciding between a meeting and an async alternative\n- Preparing to facilitate an important meeting well\n\n## Core concepts\n\n- **Purpose before scheduling.**\n  Decide, align, create, or connect. 'Sync' isn't a purpose — what decision or output justifies gathering everyone?\n- **The agenda is the meeting.**\n  Topics, owner per topic, timeboxes, pre-reads — shared 24h ahead. No agenda = permission to decline.\n- **Minimum viable attendees.**\n  Roles: decider, contributor, informed. Informed people get notes, not invites. Easier to add than to un-waste an hour.\n- **Async by default.**\n  Status, FYI, approvals, doc feedback, first-draft brainstorming — all better async: written, on your schedule, with a record.\n- **Decisions need records.**\n  Close every meeting: what was decided, owner, date. Share within hours. Unrecorded decisions get re-litigated.\n- **Timebox ruthlessly.**\n  25\u002F50 defaults, hard stops, visible parking lot. Ending 10 min early is a gift; overrun steals from the next commitment.\n- **Pre-reads, not presentations.**\n  Information transfer happens before, in writing. Meeting time is for questions, debate, decisions.\n- **Facilitator + note-taker.**\n  Separate roles, rotate them. Facilitator runs the agenda; note-taker captures decisions and actions live.\n\n## Practical workflow\n\n1. **Audit current meetings.**\n   List recurring meetings: purpose, attendees, frequency, cost (people x time x freq). Score: keep \u002F shorten \u002F async \u002F kill.\n2. **Apply the async test.**\n   'Could a doc + 48h of comments do this?' If yes, convert. Start with status meetings — almost always convertible.\n3. **Template the survivors.**\n   Decision meeting (options, recommendation, decision), weekly team (wins, priorities, blockers), 1:1 (their agenda first).\n4. **Set facilitation norms.**\n   Start on time regardless, timebox visibly, end 5 min early for action review. Rotate facilitation team-wide.\n5. **Run tight meetings.**\n   Open with purpose + desired outcome, work the agenda, park tangents visibly, close with decisions read back aloud.\n6. **Follow through fast.**\n   Notes within hours. Actions into task systems with dates — not left in the doc. Review open actions next time.\n7. **Re-audit quarterly.**\n   Every recurring meeting re-earns its slot. Kill liberally; calendars refill on their own if you let them.\n8. **Default to shorter.**\n   Change your defaults to 25\u002F50. Most 60-min meetings fit in 50; most 30-min in 25. The constraint sharpens discussion.\n\n## Common pitfalls\n\n- **Status meetings as docs-in-disguise.**\n  Written updates are faster to consume and searchable. The most convertible — and most common — waste.\n- **Inviting everyone 'just in case'.**\n  Twelve attendees, three talkers. Contributors get invites; everyone else gets notes.\n- **No pre-reads.**\n  Burning synchronous time on what could be read. Send materials early; start with questions.\n- **Decision-free endings.**\n  'Great discussion!' with no decision or owners. Even 'decide Tuesday with Sam's data' is a decision + owner + date.\n- **Back-to-back scheduling.**\n  No prep, debrief, or note capture. Buffers are hygiene, not luxury.\n- **Recurring meeting inertia.**\n  A 2022 weekly nobody would schedule today. Sunset it; let it be re-proposed with fresh purpose if needed.\n- **Camera theater.**\n  Mandating cameras without fixing purpose. Fix agenda and size first; engagement follows good design.\n- **No written record.**\n  Verbal decisions remembered differently by each attendee. Notes are the meeting's only durable output.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-meeting-optimizer",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-meeting-optimizer",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-meeting-optimizer",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-meeting-optimizer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-meeting-optimizer\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",[],[]]