ams-meeting-optimizer
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
03 SKILL.md 正文
Meeting Optimizer
Overview
Meetings are the most expensive communication: everyone's time simultaneously, plus prep and recovery.
Most run on autopilot: no agenda, wrong attendees, no decisions, no follow-through.
Optimize = question each meeting (async instead?), design survivors, facilitate tightly, record decisions.
Goal isn't zero meetings — it's meetings that earn their cost.
When to use
- Team complains about too many meetings (or silently disengages in them)
- Meetings run over, drift, or end without decisions
- Designing meeting culture for a new team or company
- Deciding between a meeting and an async alternative
- Preparing to facilitate an important meeting well
Core concepts
- Purpose before scheduling. Decide, align, create, or connect. 'Sync' isn't a purpose — what decision or output justifies gathering everyone?
- The agenda is the meeting. Topics, owner per topic, timeboxes, pre-reads — shared 24h ahead. No agenda = permission to decline.
- Minimum viable attendees. Roles: decider, contributor, informed. Informed people get notes, not invites. Easier to add than to un-waste an hour.
- Async by default. Status, FYI, approvals, doc feedback, first-draft brainstorming — all better async: written, on your schedule, with a record.
- Decisions need records. Close every meeting: what was decided, owner, date. Share within hours. Unrecorded decisions get re-litigated.
- Timebox ruthlessly. 25/50 defaults, hard stops, visible parking lot. Ending 10 min early is a gift; overrun steals from the next commitment.
- Pre-reads, not presentations. Information transfer happens before, in writing. Meeting time is for questions, debate, decisions.
- Facilitator + note-taker. Separate roles, rotate them. Facilitator runs the agenda; note-taker captures decisions and actions live.
Practical workflow
- Audit current meetings. List recurring meetings: purpose, attendees, frequency, cost (people x time x freq). Score: keep / shorten / async / kill.
- Apply the async test. 'Could a doc + 48h of comments do this?' If yes, convert. Start with status meetings — almost always convertible.
- Template the survivors. Decision meeting (options, recommendation, decision), weekly team (wins, priorities, blockers), 1:1 (their agenda first).
- Set facilitation norms. Start on time regardless, timebox visibly, end 5 min early for action review. Rotate facilitation team-wide.
- Run tight meetings. Open with purpose + desired outcome, work the agenda, park tangents visibly, close with decisions read back aloud.
- Follow through fast. Notes within hours. Actions into task systems with dates — not left in the doc. Review open actions next time.
- Re-audit quarterly. Every recurring meeting re-earns its slot. Kill liberally; calendars refill on their own if you let them.
- Default to shorter. Change your defaults to 25/50. Most 60-min meetings fit in 50; most 30-min in 25. The constraint sharpens discussion.
Common pitfalls
- Status meetings as docs-in-disguise. Written updates are faster to consume and searchable. The most convertible — and most common — waste.
- Inviting everyone 'just in case'. Twelve attendees, three talkers. Contributors get invites; everyone else gets notes.
- No pre-reads. Burning synchronous time on what could be read. Send materials early; start with questions.
- Decision-free endings. 'Great discussion!' with no decision or owners. Even 'decide Tuesday with Sam's data' is a decision + owner + date.
- Back-to-back scheduling. No prep, debrief, or note capture. Buffers are hygiene, not luxury.
- Recurring meeting inertia. A 2022 weekly nobody would schedule today. Sunset it; let it be re-proposed with fresh purpose if needed.
- Camera theater. Mandating cameras without fixing purpose. Fix agenda and size first; engagement follows good design.
- No written record. Verbal decisions remembered differently by each attendee. Notes are the meeting's only durable output.
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).