[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792YYXZ1N8R51JYNQR4PPSW":3,"skill-same:01M792YYXZ1N8R51JYNQR4PPSW":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M792YYXZ1N8R51JYNQR4PPSW","meeting-notes",null,"Turn notes or a transcript into decisions, action items with owners and deadlines, and a parking lot. Use when summarizing meetings, tracking decisions, or extracting action items.","poorvith-mp\u002Fskills-writing","poorvith-mp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F277478855?v=4","01M78Z5K0YH1Z3PX815PGQ96ND","Poorvith M P","01M792XRHPBHAWHV437S3556E5",0,"MIT","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fmeeting-notes\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: meeting-notes\nlast_reviewed: 2026-09-06\ngroup: Documents\ndescription: >-\n  Turn notes or a transcript into decisions, action items with owners and deadlines, and a parking\n  lot. Use when summarizing meetings, tracking decisions, or extracting action items.\n---\n\n# meeting-notes\n\n## Core Philosophy\nDumping an unedited, 10-page raw automated audio transcription into Slack or Notion after a meeting is not helpful; it is an abdication of editorial responsibility. Raw transcripts are filled with conversational tangents, stuttering, and half-formed thoughts. High-impact meeting notes represent executive synthesis: extracting binding decisions, assigning clear action items with single accountable owners and due dates, capturing critical debate context, and shelving off-topic discussions in a parking lot.\n\n---\n\n## 4-Step Executive Meeting Synthesis Protocol\n\n### Step 1: Real-Time Listening & Signal Filtering\n1. **Filter the 90% Noise**:\n   - Ignore pleasantries, small talk, scheduling back-and-forths, and circular debates.\n   - Listen aggressively for trigger verbs: *\"We agreed that...\", \"I will own...\", \"The deadline is...\", \"We decided not to...\"*\n\n### Step 2: The Decision Ledger (What Was Decided)\n1. **Binding Outcomes First**:\n   - Document decisions made as unambiguous declarative statements:\n     - *Decision*: We will deprecate the v1 REST API on October 31, 2026.\n     - *Decision*: Approved $15,000 budget for Q3 security penetration test.\n\n### Step 3: The DRI Action Item Register (Who Does What by When)\n1. **Directly Responsible Individual (DRI) Model**:\n   - Every action item must have **exactly ONE individual owner** (shared ownership means zero ownership).\n   - Must include an explicit, deterministic due date (never \"soon\" or \"next sprint\"):\n     - *Format*: `[ ] [Action Verb + Deliverable] — @OwnerName (Due: YYYY-MM-DD)`\n     - *Example*: `[ ] Draft RFC for OAuth token exchange — @Sarah (Due: 2026-09-12)`\n\n### Step 4: Critical Context & The Parking Lot\n1. **Key Debate Rationale**:\n   - Capture *why* a decision was reached (the trade-offs considered):\n     - *\"Considered AWS DynamoDB vs PostgreSQL; chose Postgres due to team familiarity and lower transactional cost.\"*\n2. **The Parking Lot (Scope Defense)**:\n   - Record valuable off-topic ideas parked for future discussion so participants feel heard without derailing the meeting.\n\n---\n\n## Deliverable Format: Executive Meeting Notes (`MEETING-NOTES.md`)\n\n```markdown\n# Executive Meeting Notes: [Meeting Title]\n*Date: [YYYY-MM-DD HH:MM] | Facilitator: [Name] | Note Taker: [Name]*\n*Attendees: [Name 1], [Name 2], [Name 3] | Absent: [Name 4]*\n\n## 1. Decisions Made\n1. **Database Selection**: Standardized on PostgreSQL 16 for the billing microservice.\n2. **Sprint Timeline**: Delayed Sprint 15 launch by 3 days to accommodate external SOC 2 audit.\n3. **Budget Approval**: Approved $8,000 annual spend for Datadog APM expansion.\n\n## 2. Action Items (DRI Register)\n| Action Item \u002F Deliverable | Single Owner (DRI) | Due Date | Status |\n|---|---|---|---|\n| Provision staging RDS Postgres cluster | @Dave (DevOps) | 2026-09-09 | Pending |\n| Update OpenAPI specification with new `\u002Fbilling` schema | @Elena (Backend) | 2026-09-11 | Pending |\n| Schedule follow-up compliance sync with Legal | @Marcus (PM) | 2026-09-08 | Completed |\n\n## 3. Key Discussion Rationale & Trade-offs\n- **Postgres vs MongoDB**: MongoDB was evaluated for schema flexibility, but discarded due to lack of ACID transactional guarantees across multi-tier billing subscriptions.\n- **Audit Preparedness**: Security team confirmed all IAM roles must be pruned before Friday.\n\n## 4. Parking Lot (Deferred Topics)\n- *Topic*: Migration from REST to gRPC for internal worker communication.\n  - *Next Action*: Deferred to Q4 architecture offsite.\n```\n\n---\n\n## Worked Example: Executive Product Steering Committee Notes\n\n- **Meeting Duration**: 60 minutes of high-stakes heated debate across 8 engineering leads.\n- **Deliverable**: Condensed into a 1-page markdown memo distributed to `#leadership` within 15 minutes of call completion.\n- **Outcome**: 3 major strategic decisions ratified; 4 action items completed on time; zero confusion regarding owners.\n\n---\n\n## Verification Checklist\n\n- [ ] Notes published and distributed within 60 minutes of meeting completion.\n- [ ] Decisions made are prominently listed at the top.\n- [ ] Every action item has exactly one designated individual owner and an explicit date.\n- [ ] Summary captures underlying rationale and trade-offs, not verbatim speech.\n- [ ] Off-topic discussions are captured in a structured Parking Lot.\n\n---\n\n## Anti-Patterns\n\n- **The Unedited Transcript**: Pasting 15 pages of Otter.ai raw speech text into a channel.\n- **Multiple Owners**: Writing \"Action: Team will review API docs\" (guarantees nobody does it).\n- **Vague Deadlines**: Assigning action items with deadlines like \"ASAP\" or \"ongoing\".\n","# meeting-notes\n\n## Core Philosophy\nDumping an unedited, 10-page raw automated audio transcription into Slack or Notion after a meeting is not helpful; it is an abdication of editorial responsibility. Raw transcripts are filled with conversational tangents, stuttering, and half-formed thoughts. High-impact meeting notes represent executive synthesis: extracting binding decisions, assigning clear action items with single accountable owners and due dates, capturing critical debate context, and shelving off-topic discussions in a parking lot.\n\n---\n\n## 4-Step Executive Meeting Synthesis Protocol\n\n### Step 1: Real-Time Listening & Signal Filtering\n1. **Filter the 90% Noise**:\n   - Ignore pleasantries, small talk, scheduling back-and-forths, and circular debates.\n   - Listen aggressively for trigger verbs: *\"We agreed that...\", \"I will own...\", \"The deadline is...\", \"We decided not to...\"*\n\n### Step 2: The Decision Ledger (What Was Decided)\n1. **Binding Outcomes First**:\n   - Document decisions made as unambiguous declarative statements:\n     - *Decision*: We will deprecate the v1 REST API on October 31, 2026.\n     - *Decision*: Approved $15,000 budget for Q3 security penetration test.\n\n### Step 3: The DRI Action Item Register (Who Does What by When)\n1. **Directly Responsible Individual (DRI) Model**:\n   - Every action item must have **exactly ONE individual owner** (shared ownership means zero ownership).\n   - Must include an explicit, deterministic due date (never \"soon\" or \"next sprint\"):\n     - *Format*: `[ ] [Action Verb + Deliverable] — @OwnerName (Due: YYYY-MM-DD)`\n     - *Example*: `[ ] Draft RFC for OAuth token exchange — @Sarah (Due: 2026-09-12)`\n\n### Step 4: Critical Context & The Parking Lot\n1. **Key Debate Rationale**:\n   - Capture *why* a decision was reached (the trade-offs considered):\n     - *\"Considered AWS DynamoDB vs PostgreSQL; chose Postgres due to team familiarity and lower transactional cost.\"*\n2. **The Parking Lot (Scope Defense)**:\n   - Record valuable off-topic ideas parked for future discussion so participants feel heard without derailing the meeting.\n\n---\n\n## Deliverable Format: Executive Meeting Notes (`MEETING-NOTES.md`)\n\n```markdown\n# Executive Meeting Notes: [Meeting Title]\n*Date: [YYYY-MM-DD HH:MM] | Facilitator: [Name] | Note Taker: [Name]*\n*Attendees: [Name 1], [Name 2], [Name 3] | Absent: [Name 4]*\n\n## 1. Decisions Made\n1. **Database Selection**: Standardized on PostgreSQL 16 for the billing microservice.\n2. **Sprint Timeline**: Delayed Sprint 15 launch by 3 days to accommodate external SOC 2 audit.\n3. **Budget Approval**: Approved $8,000 annual spend for Datadog APM expansion.\n\n## 2. Action Items (DRI Register)\n| Action Item \u002F Deliverable | Single Owner (DRI) | Due Date | Status |\n|---|---|---|---|\n| Provision staging RDS Postgres cluster | @Dave (DevOps) | 2026-09-09 | Pending |\n| Update OpenAPI specification with new `\u002Fbilling` schema | @Elena (Backend) | 2026-09-11 | Pending |\n| Schedule follow-up compliance sync with Legal | @Marcus (PM) | 2026-09-08 | Completed |\n\n## 3. Key Discussion Rationale & Trade-offs\n- **Postgres vs MongoDB**: MongoDB was evaluated for schema flexibility, but discarded due to lack of ACID transactional guarantees across multi-tier billing subscriptions.\n- **Audit Preparedness**: Security team confirmed all IAM roles must be pruned before Friday.\n\n## 4. Parking Lot (Deferred Topics)\n- *Topic*: Migration from REST to gRPC for internal worker communication.\n  - *Next Action*: Deferred to Q4 architecture offsite.\n```\n\n---\n\n## Worked Example: Executive Product Steering Committee Notes\n\n- **Meeting Duration**: 60 minutes of high-stakes heated debate across 8 engineering leads.\n- **Deliverable**: Condensed into a 1-page markdown memo distributed to `#leadership` within 15 minutes of call completion.\n- **Outcome**: 3 major strategic decisions ratified; 4 action items completed on time; zero confusion regarding owners.\n\n---\n\n## Verification Checklist\n\n- [ ] Notes published and distributed within 60 minutes of meeting completion.\n- [ ] Decisions made are prominently listed at the top.\n- [ ] Every action item has exactly one designated individual owner and an explicit date.\n- [ ] Summary captures underlying rationale and trade-offs, not verbatim speech.\n- [ ] Off-topic discussions are captured in a structured Parking Lot.\n\n---\n\n## Anti-Patterns\n\n- **The Unedited Transcript**: Pasting 15 pages of Otter.ai raw speech text into a channel.\n- **Multiple Owners**: Writing \"Action: Team will review API docs\" (guarantees nobody does it).\n- **Vague Deadlines**: Assigning action items with deadlines like \"ASAP\" or \"ongoing\".\n",{"name":5,"group":24,"description":7,"last_reviewed":25},"Documents",1788652800000,"main","036f70c9d6ddd7a7e8b6691aa3ae0279b0649433","skills\u002Fmeeting-notes",2,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskillary","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp","poorvithmp.com","Shipping tools for problems people notice too late.","2026-10-02 21:32:55",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add poorvith-mp\u002Fskills-writing --skill meeting-notes",{"tool":42,"command":43},"bunx","bunx skills add poorvith-mp\u002Fskills-writing --skill meeting-notes",{"tool":45,"command":46},"pnpm","pnpm dlx skills add poorvith-mp\u002Fskills-writing --skill meeting-notes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fmeeting-notes\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"evals\u002Frouting.yaml","REFERENCE","参考文档",1005,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fmeeting-notes\u002Fevals\u002Frouting.yaml",{"path":57,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":61},"meeting-notes.skill","OTHER","其他",3257,"https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fmeeting-notes\u002Fmeeting-notes.skill",[63,69,76,83,90,97],{"skillNo":64,"name":65,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79309BVEDZ4AB80FM7N45XV","writing-taste","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-taste\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79303W7E8AD1M3EC1T9TXEE","translation","Translate while preserving register, idiom and domain terms, flagging what doesn't carry across. Use when translating text across languages preserving nuance, tone, and idioms.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftranslation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79300EK34V2MZRPVMV3PP41","thread-to-blog-converter","Moved to modernized catalog in skillary. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-blog-converter\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M792ZTRHZGD0YY4AE5ARWZC5","thread-to-article","Expand an X or LinkedIn thread into a structured article with added context, headings and links. Use when expanding social threads into long-form articles, or vice versa.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Fthread-to-article\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M792ZRYX1PPQ737CGQB28T1E","technical-writer","Moved to technical-docs in skills-writing. Removed in v4.1.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-writer\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M792ZMCF8S5GJMNKJ984ARDF","technical-docs","Write API references, user guides, setup manuals and architecture docs with consistent terminology. Use when writing developer documentation, API guides, or tutorials.","https:\u002F\u002Fgithub.com\u002Fpoorvith-mp\u002Fskills-writing\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-docs\u002FSKILL.md",[],[]]