[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF335KXY99EF6D3R36TZKF":3,"skill-same:01M7AF335KXY99EF6D3R36TZKF":46},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7AF335KXY99EF6D3R36TZKF","meeting-prep-skill",null,"Generate agenda drafts and pre-read briefings from calendar context, prior meeting notes, and connected sources. Use when preparing for any meeting, creating agendas, or compiling pre-reads. Trigger with \"prep for my meeting with\", \"create agenda for\", \"meeting brief for\".","innFactory-AI\u002Fcompany-ai-stack-skills","innFactory-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F165681221?v=4","01M7AEC27VD0D1QX2XBX441MDW","innFactory AI","01M7AEC28G25HQ9H9SN58MNV27",0,"MIT","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fproductivity\u002Fmeeting-prep-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: meeting-prep-skill\ndescription: Generate agenda drafts and pre-read briefings from calendar context, prior meeting notes, and connected sources. Use when preparing for any meeting, creating agendas, or compiling pre-reads. Trigger with \"prep for my meeting with\", \"create agenda for\", \"meeting brief for\".\n---\n\n# Meeting Prep Skill\n\nGather context from calendars, email, chat, and notes to draft agendas, compile pre-read briefings, and suggest talking points for any meeting. The data comes from you, a connected MCP source, or companyRAG collections.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **Calendar via MCP** (e.g. Google Calendar, Outlook) | Meeting title, time, attendees, location, attached agenda |\n| **Email via MCP** (e.g. Gmail, Outlook) | Recent correspondence with attendees, shared documents |\n| **Chat via MCP** (e.g. Slack, Microsoft Teams) | Recent conversations with attendees, channel context |\n| **Documents via MCP** (e.g. Notion, Confluence, Google Docs) | Prior meeting notes, shared documents, project pages |\n| **CRM via MCP** (e.g. Salesforce, HubSpot) | Account history, deal status, contact details (for external meetings) |\n| **Issue tracker via MCP** (e.g. Jira, Linear, Asana) | Open items relevant to the meeting topic |\n| **companyM365** (if enabled) | Outlook calendar and mail, Teams messages and OneDrive\u002FSharePoint documents from your Microsoft 365 account |\n| **companyRAG \u002F file upload** | Recurring meeting templates, background documents |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Preparation Workflow\n\nFollow these steps for every meeting preparation request. The depth of preparation scales with meeting importance — a quick 1:1 needs less than a board presentation.\n\n### Step 1: Identify the Meeting\n\nEstablish the basics:\n\n- Meeting type: 1:1, team standup, project review, client call, board meeting, interview, brainstorm, decision meeting, informational, retrospective\n- Attendees: Who is attending? What are their roles? Are any attendees external (clients, partners, vendors)?\n- Duration: How long is the meeting? This constrains the agenda.\n- Objective: What should be true after this meeting that is not true before? If the user cannot articulate this, help them define it — a meeting without an objective is a meeting without value.\n- Recurrence: Is this a one-off or recurring meeting? For recurring meetings, pull prior meeting notes if available.\n\n### Step 2: Gather Context\n\nPull relevant information from connected sources:\n\n**Prior meetings with these attendees:**\n\n- Last meeting notes, action items, decisions made\n- Outstanding action items from previous sessions\n- Topics that were deferred or parked\n\n**Recent correspondence:**\n\n- Email threads with attendees from the past 1-2 weeks\n- Chat messages in relevant channels\n- Shared documents recently edited\n\n**Relevant project\u002Faccount status:**\n\n- Open tasks or issues related to the meeting topic\n- For external meetings: account status, deal stage, recent interactions from CRM\n- For project meetings: milestone status, blockers, recent changes\n\n**Background documents:**\n\n- Any pre-reads already shared by the organiser\n- Relevant policies, specifications, or reference materials from companyRAG collections\n\nIf connected sources are not available, ask the user to provide the context they have. Even a 2-sentence summary of \"what this meeting is about and what happened last time\" dramatically improves preparation quality.\n\n### Step 3: Draft Agenda\n\nConstruct the agenda using this framework:\n\n**Agenda structure:**\n\n```\n# [Meeting Title]\nDate: [date and time]\nDuration: [length]\nAttendees: [list]\nObjective: [what should be true after this meeting]\n\n## Agenda\n\n1. [Opening \u002F Check-in]                          [X min]\n   - [Brief context-setter or warm-up]\n\n2. [Topic A — highest priority]                   [X min]\n   - Context: [1-2 sentences of background]\n   - Decision needed: [yes\u002Fno — if yes, what decision]\n   - Pre-read: [link or reference, if any]\n\n3. [Topic B]                                      [X min]\n   - Context: [...]\n   - Decision needed: [...]\n\n4. [Topic C]                                      [X min]\n   - Context: [...]\n\n5. [Action items and next steps]                  [5 min]\n   - Review decisions made\n   - Assign action items with owners and deadlines\n\n## Open Items from Last Meeting\n  - [Item 1] — Owner: [name] — Status: [done \u002F in progress \u002F not started]\n  - [Item 2] — ...\n```\n\n**Agenda principles:**\n\n- Time-box every item. Total time allocations must not exceed meeting duration minus 5 minutes (buffer for overrun and wrap-up).\n- Prioritise ruthlessly. Put the most important or time-sensitive topic first. If the meeting runs over, at least the critical item was addressed.\n- Distinguish decisions from discussions. Mark topics that require a decision — these need the decision-maker present and enough context for an informed choice.\n- Limit to 3-5 substantive items for a 30-minute meeting, 5-7 for a 60-minute meeting. More items than that guarantees nothing gets adequate attention.\n- Include open items from the last meeting. Accountability requires visibility.\n\n### Step 4: Compile Pre-Read Briefing\n\nFor meetings where attendees need background (project reviews, client calls, board meetings), produce a briefing document:\n\n```\n# Meeting Brief: [Title]\nPrepared: [date]\nMeeting: [date and time]\n\n## TL;DR\n  [2-3 sentences: why we're meeting, what's most important, what we need to decide]\n\n## Context\n  [Background the attendees need — keep it to 1 page maximum. Link to detailed sources rather than reproducing them.]\n\n## Key Data Points\n  - [Metric or fact 1] — Source: [where this came from]\n  - [Metric or fact 2] — Source: [...]\n  - [Metric or fact 3] — Source: [...]\n\n## Open Questions\n  1. [Question that needs to be resolved in this meeting]\n  2. [Question 2]\n\n## Relevant History\n  - [Date]: [What happened — decision, milestone, or change]\n  - [Date]: [...]\n\n## Suggested Talking Points\n  - [Point 1 — what to raise and why]\n  - [Point 2]\n  - [Point 3]\n```\n\n**Briefing principles:**\n\n- Brevity over comprehensiveness. A 1-page brief that gets read beats a 10-page document that doesn't.\n- Source everything. Every data point, claim, or historical reference must cite its source so attendees can dig deeper if needed.\n- Lead with the decision or ask. If the meeting needs a decision, put the question and options first — context second.\n\n### Step 5: Suggest Talking Points\n\nBased on the gathered context, suggest specific talking points the user should raise:\n\n| Type | When to Suggest | Format |\n| --- | --- | --- |\n| **Follow-up from prior meeting** | An action item was assigned or a topic was deferred | \"Last time we agreed to [X]. Status update?\" |\n| **Proactive update** | The user has progress or news relevant to attendees | \"Share that [milestone] was completed \u002F [blocker] was resolved\" |\n| **Question to ask** | Information is needed from an attendee | \"Ask [person] about [topic] — needed for [reason]\" |\n| **Risk to flag** | A risk or concern should be raised early | \"Flag that [risk] could affect [timeline\u002Foutcome]\" |\n| **Decision to drive** | A pending decision needs attention | \"We need to decide on [topic] — options are [A] or [B]\" |\n\n## Meeting Type Quick Guides\n\nAdapt the workflow depth to the meeting type:\n\n| Meeting Type | Preparation Depth | Key Focus |\n| --- | --- | --- |\n| **1:1 (manager\u002Freport)** | Light — 5-10 min prep | Open action items, blockers, career\u002Fdevelopment topics |\n| **Team standup** | Minimal — 2 min prep | Your status, blockers, help needed |\n| **Project review** | Medium — 15-20 min prep | Milestone status, risks, decisions needed, timeline |\n| **Client\u002Fexternal call** | Full — 20-30 min prep | Account history, relationship context, objectives, pre-read |\n| **Board\u002Fexecutive** | Full — 30+ min prep | Narrative structure, key metrics, decisions, pre-read package |\n| **Interview** | Medium — 15 min prep | Role requirements, candidate background, prepared questions |\n| **Brainstorm** | Light — 10 min prep | Problem definition, constraints, seed ideas, creative prompts |\n\n## Guardrails\n\n- NEVER fabricate meeting history or attendee backgrounds — if prior notes or org data are unavailable, ask the user.\n- NEVER generate fake metrics or data points for briefings — use `[Data needed — ask user]` as a placeholder.\n- NEVER assume the meeting objective — ask before drafting the agenda.\n- Flag outputs: `[From connected source]`, `[From user input]`, `[Suggested]`, `[Data needed]`.\n\n> **Tip:** Ask for DOCX or Markdown output via companyFILES to get a formatted agenda or briefing ready to share.\n","# Meeting Prep Skill\n\nGather context from calendars, email, chat, and notes to draft agendas, compile pre-read briefings, and suggest talking points for any meeting. The data comes from you, a connected MCP source, or companyRAG collections.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **Calendar via MCP** (e.g. Google Calendar, Outlook) | Meeting title, time, attendees, location, attached agenda |\n| **Email via MCP** (e.g. Gmail, Outlook) | Recent correspondence with attendees, shared documents |\n| **Chat via MCP** (e.g. Slack, Microsoft Teams) | Recent conversations with attendees, channel context |\n| **Documents via MCP** (e.g. Notion, Confluence, Google Docs) | Prior meeting notes, shared documents, project pages |\n| **CRM via MCP** (e.g. Salesforce, HubSpot) | Account history, deal status, contact details (for external meetings) |\n| **Issue tracker via MCP** (e.g. Jira, Linear, Asana) | Open items relevant to the meeting topic |\n| **companyM365** (if enabled) | Outlook calendar and mail, Teams messages and OneDrive\u002FSharePoint documents from your Microsoft 365 account |\n| **companyRAG \u002F file upload** | Recurring meeting templates, background documents |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Preparation Workflow\n\nFollow these steps for every meeting preparation request. The depth of preparation scales with meeting importance — a quick 1:1 needs less than a board presentation.\n\n### Step 1: Identify the Meeting\n\nEstablish the basics:\n\n- Meeting type: 1:1, team standup, project review, client call, board meeting, interview, brainstorm, decision meeting, informational, retrospective\n- Attendees: Who is attending? What are their roles? Are any attendees external (clients, partners, vendors)?\n- Duration: How long is the meeting? This constrains the agenda.\n- Objective: What should be true after this meeting that is not true before? If the user cannot articulate this, help them define it — a meeting without an objective is a meeting without value.\n- Recurrence: Is this a one-off or recurring meeting? For recurring meetings, pull prior meeting notes if available.\n\n### Step 2: Gather Context\n\nPull relevant information from connected sources:\n\n**Prior meetings with these attendees:**\n\n- Last meeting notes, action items, decisions made\n- Outstanding action items from previous sessions\n- Topics that were deferred or parked\n\n**Recent correspondence:**\n\n- Email threads with attendees from the past 1-2 weeks\n- Chat messages in relevant channels\n- Shared documents recently edited\n\n**Relevant project\u002Faccount status:**\n\n- Open tasks or issues related to the meeting topic\n- For external meetings: account status, deal stage, recent interactions from CRM\n- For project meetings: milestone status, blockers, recent changes\n\n**Background documents:**\n\n- Any pre-reads already shared by the organiser\n- Relevant policies, specifications, or reference materials from companyRAG collections\n\nIf connected sources are not available, ask the user to provide the context they have. Even a 2-sentence summary of \"what this meeting is about and what happened last time\" dramatically improves preparation quality.\n\n### Step 3: Draft Agenda\n\nConstruct the agenda using this framework:\n\n**Agenda structure:**\n\n```\n# [Meeting Title]\nDate: [date and time]\nDuration: [length]\nAttendees: [list]\nObjective: [what should be true after this meeting]\n\n## Agenda\n\n1. [Opening \u002F Check-in]                          [X min]\n   - [Brief context-setter or warm-up]\n\n2. [Topic A — highest priority]                   [X min]\n   - Context: [1-2 sentences of background]\n   - Decision needed: [yes\u002Fno — if yes, what decision]\n   - Pre-read: [link or reference, if any]\n\n3. [Topic B]                                      [X min]\n   - Context: [...]\n   - Decision needed: [...]\n\n4. [Topic C]                                      [X min]\n   - Context: [...]\n\n5. [Action items and next steps]                  [5 min]\n   - Review decisions made\n   - Assign action items with owners and deadlines\n\n## Open Items from Last Meeting\n  - [Item 1] — Owner: [name] — Status: [done \u002F in progress \u002F not started]\n  - [Item 2] — ...\n```\n\n**Agenda principles:**\n\n- Time-box every item. Total time allocations must not exceed meeting duration minus 5 minutes (buffer for overrun and wrap-up).\n- Prioritise ruthlessly. Put the most important or time-sensitive topic first. If the meeting runs over, at least the critical item was addressed.\n- Distinguish decisions from discussions. Mark topics that require a decision — these need the decision-maker present and enough context for an informed choice.\n- Limit to 3-5 substantive items for a 30-minute meeting, 5-7 for a 60-minute meeting. More items than that guarantees nothing gets adequate attention.\n- Include open items from the last meeting. Accountability requires visibility.\n\n### Step 4: Compile Pre-Read Briefing\n\nFor meetings where attendees need background (project reviews, client calls, board meetings), produce a briefing document:\n\n```\n# Meeting Brief: [Title]\nPrepared: [date]\nMeeting: [date and time]\n\n## TL;DR\n  [2-3 sentences: why we're meeting, what's most important, what we need to decide]\n\n## Context\n  [Background the attendees need — keep it to 1 page maximum. Link to detailed sources rather than reproducing them.]\n\n## Key Data Points\n  - [Metric or fact 1] — Source: [where this came from]\n  - [Metric or fact 2] — Source: [...]\n  - [Metric or fact 3] — Source: [...]\n\n## Open Questions\n  1. [Question that needs to be resolved in this meeting]\n  2. [Question 2]\n\n## Relevant History\n  - [Date]: [What happened — decision, milestone, or change]\n  - [Date]: [...]\n\n## Suggested Talking Points\n  - [Point 1 — what to raise and why]\n  - [Point 2]\n  - [Point 3]\n```\n\n**Briefing principles:**\n\n- Brevity over comprehensiveness. A 1-page brief that gets read beats a 10-page document that doesn't.\n- Source everything. Every data point, claim, or historical reference must cite its source so attendees can dig deeper if needed.\n- Lead with the decision or ask. If the meeting needs a decision, put the question and options first — context second.\n\n### Step 5: Suggest Talking Points\n\nBased on the gathered context, suggest specific talking points the user should raise:\n\n| Type | When to Suggest | Format |\n| --- | --- | --- |\n| **Follow-up from prior meeting** | An action item was assigned or a topic was deferred | \"Last time we agreed to [X]. Status update?\" |\n| **Proactive update** | The user has progress or news relevant to attendees | \"Share that [milestone] was completed \u002F [blocker] was resolved\" |\n| **Question to ask** | Information is needed from an attendee | \"Ask [person] about [topic] — needed for [reason]\" |\n| **Risk to flag** | A risk or concern should be raised early | \"Flag that [risk] could affect [timeline\u002Foutcome]\" |\n| **Decision to drive** | A pending decision needs attention | \"We need to decide on [topic] — options are [A] or [B]\" |\n\n## Meeting Type Quick Guides\n\nAdapt the workflow depth to the meeting type:\n\n| Meeting Type | Preparation Depth | Key Focus |\n| --- | --- | --- |\n| **1:1 (manager\u002Freport)** | Light — 5-10 min prep | Open action items, blockers, career\u002Fdevelopment topics |\n| **Team standup** | Minimal — 2 min prep | Your status, blockers, help needed |\n| **Project review** | Medium — 15-20 min prep | Milestone status, risks, decisions needed, timeline |\n| **Client\u002Fexternal call** | Full — 20-30 min prep | Account history, relationship context, objectives, pre-read |\n| **Board\u002Fexecutive** | Full — 30+ min prep | Narrative structure, key metrics, decisions, pre-read package |\n| **Interview** | Medium — 15 min prep | Role requirements, candidate background, prepared questions |\n| **Brainstorm** | Light — 10 min prep | Problem definition, constraints, seed ideas, creative prompts |\n\n## Guardrails\n\n- NEVER fabricate meeting history or attendee backgrounds — if prior notes or org data are unavailable, ask the user.\n- NEVER generate fake metrics or data points for briefings — use `[Data needed — ask user]` as a placeholder.\n- NEVER assume the meeting objective — ask before drafting the agenda.\n- Flag outputs: `[From connected source]`, `[From user input]`, `[Suggested]`, `[Data needed]`.\n\n> **Tip:** Ask for DOCX or Markdown output via companyFILES to get a formatted agenda or briefing ready to share.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fproductivity\u002Fmeeting-prep-skill","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills","https:\u002F\u002Fgithub.com\u002FinnFactory-AI","https:\u002F\u002Finnfactory.ai","Engineering AI. Enabling Tomorrow.","2026-11-13 19:54:47",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill meeting-prep-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill meeting-prep-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill meeting-prep-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fproductivity\u002Fmeeting-prep-skill\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7AF4HHK5B987T44HW7BZFVZ","sales-asset-skill","Produce tailored one-pagers, landing pages, case study drafts, and demo narratives personalised to a specific deal and buyer persona. Use when preparing collateral for a specific deal, building leave-behind materials, or customising standard assets for a prospect. Trigger with \"create a one-pager for\", \"sales deck for [deal]\", \"customise this asset for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fsales-asset-skill\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7AF4D32V0FJE0QGCBZSQ7BW","pipeline-review-skill","Analyse deal health, surface stale or at-risk opportunities, and produce a prioritised weekly action plan. Use when preparing for a pipeline review meeting, assessing forecast accuracy, or identifying stuck deals. Trigger with \"review my pipeline\", \"pipeline health check\", \"deal risk analysis\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fpipeline-review-skill\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7AF48W7G8DMAHRAM125B192","outreach-skill","Research a prospect then draft personalised outreach with research-backed hooks, subject-line variants, and follow-up sequences. Use when cold-emailing a prospect, writing LinkedIn outreach, or building a multi-touch sequence. Trigger with \"draft outreach to [person\u002Fcompany]\", \"write cold email to\", \"outreach sequence for\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Foutreach-skill\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7AF43VKNPQ7G1NTQ4MRH40J","forecast-skill","Build a weighted revenue forecast with risk flags, commit recommendations, and gap-to-quota analysis. Use when preparing for a forecast call, evaluating end-of-quarter projections, or assessing pipeline coverage. Trigger with \"build forecast\", \"forecast for this quarter\", \"where do I stand against quota\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fforecast-skill\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7AF3Z5N61VYSEJRYWXR4JP1","deal-strategy-skill","Map stakeholder power dynamics, surface deal risks, and recommend a step-by-step engagement strategy. Use when entering a complex deal, preparing for an executive sponsor meeting, or diagnosing a stuck opportunity. Trigger with \"plan deal strategy for\", \"stakeholder map\", \"how do I advance this deal\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fdeal-strategy-skill\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7AF3VGG29AX0T2X9WQ5MWDN","call-summary-skill","Extract action items, key topics, and objections from call notes or transcripts and draft a customer-facing follow-up email. Use after a sales call, demo, or discovery session. Trigger with \"summarise this call\", \"call notes from\", \"write follow-up for this meeting\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fcall-summary-skill\u002FSKILL.md",[],[]]