[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF3VGG29AX0T2X9WQ5MWDN":3,"skill-same:01M7AF3VGG29AX0T2X9WQ5MWDN":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},"01M7AF3VGG29AX0T2X9WQ5MWDN","call-summary-skill",null,"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\".","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\u002Fsales\u002Fcall-summary-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: call-summary-skill\ndescription: 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\".\n---\n\n# Call Summary Skill\n\nTurn call notes or transcripts into actionable intelligence and draft customer-ready follow-up emails. The skill produces call summaries, action-item registers, objection logs, and follow-up drafts. You provide all call content, or it comes from a connected source.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CRM via MCP** (e.g. HubSpot, Salesforce) | Account context, opportunity stage, known stakeholders, prior call notes |\n| **Call-recording \u002F transcription via MCP** (e.g. Gong) | Raw transcripts, participant lists, timestamps of key moments |\n| **companyTRANSCRIBE** (if enabled) | Transcribes a call recording (audio or video) attached to the chat with speaker labels, or retrieves your existing transcripts |\n| **companyM365** (if enabled) | Transcripts of Teams meetings |\n| **companyRAG collections** | Discovery summaries, competitive profiles, product info for context-aware follow-ups |\n| **File upload (transcripts)** | Transcript or notes files you drop directly into the chat |\n\n> **No connected source?** Paste the transcript or notes in chat or upload the relevant files — the skill works the same way.\n\n## Call-Processing Workflow\n\n```\n1. INGEST call content\n   |\n   +--> Accept raw transcript, structured notes, or bullet-point recap\n   +--> Identify call type: Discovery \u002F Demo \u002F Negotiation \u002F Check-In \u002F Other\n   +--> Identify participants (from transcript headers, notes, or user input)\n   |\n2. EXTRACT key topics\n   |\n   +--> Categorize discussion points (see Topic Categorization below)\n   +--> Capture direct quotes that carry weight (decisions, commitments, objections)\n   +--> Note topics raised but not resolved — these become open items\n   |\n3. IDENTIFY action items\n   |\n   +--> For each commitment or next step mentioned:\n   |      Owner (our side \u002F their side \u002F joint)\n   |      Action (specific and verifiable)\n   |      Deadline (stated or inferred from context)\n   |      Priority (blocks deal progression \u002F important \u002F nice-to-have)\n   |\n4. FLAG objections and concerns\n   |\n   +--> Capture the objection as stated (not paraphrased away)\n   +--> Note whether it was addressed, partially addressed, or left open\n   +--> Record the response given (if any) for consistency in future calls\n   +--> Classify by type (see Objection Classification below)\n   |\n5. ASSESS deal impact\n   |\n   +--> Did the call advance, stall, or regress the deal?\n   +--> What changed about our understanding of the opportunity?\n   +--> Are there new stakeholders, risks, or timeline shifts?\n   |\n6. DRAFT follow-up (see Follow-Up Email Framework below)\n   |\n7. COMPILE output (see Output Templates below)\n```\n\n## Topic Categorization\n\nClassify each discussion topic to make the summary scannable:\n\n| Category | What It Covers | CRM Relevance |\n| --- | --- | --- |\n| **Requirements** | Stated needs, use cases, evaluation criteria | Update opportunity requirements |\n| **Decision Process** | Timeline, stakeholders involved, approval steps | Update close date, decision map |\n| **Budget \u002F Commercial** | Pricing discussion, budget constraints, ROI expectations | Update deal value, stage |\n| **Technical** | Integration needs, security, compliance, architecture | Log as technical requirements |\n| **Competitive** | Mentions of alternatives, incumbent vendor, evaluation comparison | Update competitive field in CRM |\n| **Relationship** | Rapport signals, internal politics, champion strength indicators | Update stakeholder notes |\n| **Next Steps** | Agreed actions, follow-up meetings, deliverables promised | Create CRM tasks |\n\n## Objection Classification\n\n| Type | Definition | Follow-Up Priority |\n| --- | --- | --- |\n| **Deal-blocking** | Objection that will prevent close if unresolved | Immediate |\n| **Stage-blocking** | Prevents advancement to next stage but not necessarily a deal-killer | High |\n| **Concern** | Expressed worry that needs addressing but is not blocking progress | Medium |\n| **Skepticism** | General doubt about value or approach — needs proof points | Medium |\n| **Clarification** | Misunderstanding or information gap — easily resolved with data | Low |\n\nFor each objection, track: stated objection (verbatim or near-verbatim), classification, response given during the call, resolution status (resolved \u002F partially addressed \u002F open), and recommended follow-up action.\n\n## Follow-Up Email Framework\n\nThe follow-up email should be sendable with minimal editing. Structure:\n\n### Tone Calibration\n\n| Relationship Stage | Tone | Formality |\n| --- | --- | --- |\n| **First interaction** | Professional, appreciative of time | Formal |\n| **Active evaluation** | Collaborative, momentum-focused | Semi-formal |\n| **Established rapport** | Direct, efficient, partnership tone | Conversational |\n| **Executive audience** | Concise, outcome-focused | Formal |\n\n### Email Structure\n\n```\nSubject: [Descriptive, action-oriented — never generic like \"Meeting follow-up\"]\n\n[Opening: 1 sentence — thank + reference a specific moment from the call]\n\n[Summary: 3-5 bullet points of what was discussed — phrased in terms\n of their priorities and language, not your product features]\n\n[Action Items: clear table or list]\n  - What we committed to doing → by when\n  - What we're asking them to do → by when\n\n[Next Step: specific — date, time, agenda for next interaction]\n\n[Close: 1 sentence — express enthusiasm about the specific outcome\n discussed, not generic excitement]\n```\n\n### Follow-Up Quality Checklist\n\n- References something specific from the conversation (proves you listened)\n- Uses their language and terminology, not internal jargon\n- Action items have owners and dates\n- Next step is specific and time-bound\n- No markdown formatting (plain text or minimal HTML for email clients)\n- Subject line would make sense in their inbox without additional context\n- Appropriate length: 150-250 words for standard follow-ups\n\n## Output Template — Call Summary\n\n```\n# Call Summary: [Meeting Title \u002F Company Name]\n**Date**: [Call date]  |  **Duration**: [Actual length]\n**Call Type**: [Discovery \u002F Demo \u002F Negotiation \u002F Check-In]\n**Participants**: [List with roles]\n\n## Key Topics Discussed\n| # | Topic   | Category   | Summary                |\n|---|---------|------------|------------------------|\n| 1 | [Topic] | [Category] | [2-3 sentence summary] |\n| 2 | [Topic] | [Category] | [2-3 sentence summary] |\n\n## Action Items\n| #  | Action            | Owner | Deadline | Priority         |\n|----|-------------------|-------|----------|------------------|\n| 1  | [Specific action] | [Who] | [When]   | [Classification] |\n\n## Objections & Concerns\n| Objection   | Type             | Status           | Follow-Up Needed     |\n|-------------|------------------|------------------|----------------------|\n| [As stated] | [Classification] | [Open\u002FAddressed] | [Recommended action] |\n\n## Deal Impact Assessment\n- **Deal Movement**: [Advanced \u002F Stalled \u002F Regressed \u002F Neutral]\n- **Stage Recommendation**: [Stay \u002F Advance to X \u002F Flag for review]\n- **New Information**: [What we learned that changes our understanding]\n- **Risk Changes**: [New risks surfaced or existing risks mitigated]\n\n## Follow-Up Email Draft\n[Ready-to-send email following the framework above]\n```\n\n## Processing Notes for Transcript Quality\n\n| Input Quality | Handling |\n| --- | --- |\n| **Full transcript** | Extract verbatim quotes for key moments; comprehensive summary |\n| **Structured notes** | Organize into framework; flag potential gaps in coverage |\n| **Bullet-point recap** | Build summary from bullets; note that nuance may be missing |\n| **Partial \u002F fragmentary** | Summarize what is available; clearly mark sections as \"[Incomplete — ask rep to fill gaps]\" |\n\n## Guardrails\n\n1. Never fabricate call content. Every topic, quote, and action item must be traceable to the provided notes or transcript. Ambiguous content: \"[Unclear from notes — verify with attendees]\".\n2. Never invent attendee reactions. Do not characterise sentiment or buy-in unless explicitly stated in the notes.\n3. Objection accuracy. Capture objections as close to verbatim as the source allows. Do not soften, reframe, or minimise stated concerns.\n4. Source labeling. Tag assertions — [From transcript], [From notes], [From user input], [AI interpretation]. AI interpretations must be flagged for verification.\n\n> **Tip:** Ask for DOCX or Markdown output via companyFILES to get a formatted summary ready to share.\n","# Call Summary Skill\n\nTurn call notes or transcripts into actionable intelligence and draft customer-ready follow-up emails. The skill produces call summaries, action-item registers, objection logs, and follow-up drafts. You provide all call content, or it comes from a connected source.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CRM via MCP** (e.g. HubSpot, Salesforce) | Account context, opportunity stage, known stakeholders, prior call notes |\n| **Call-recording \u002F transcription via MCP** (e.g. Gong) | Raw transcripts, participant lists, timestamps of key moments |\n| **companyTRANSCRIBE** (if enabled) | Transcribes a call recording (audio or video) attached to the chat with speaker labels, or retrieves your existing transcripts |\n| **companyM365** (if enabled) | Transcripts of Teams meetings |\n| **companyRAG collections** | Discovery summaries, competitive profiles, product info for context-aware follow-ups |\n| **File upload (transcripts)** | Transcript or notes files you drop directly into the chat |\n\n> **No connected source?** Paste the transcript or notes in chat or upload the relevant files — the skill works the same way.\n\n## Call-Processing Workflow\n\n```\n1. INGEST call content\n   |\n   +--> Accept raw transcript, structured notes, or bullet-point recap\n   +--> Identify call type: Discovery \u002F Demo \u002F Negotiation \u002F Check-In \u002F Other\n   +--> Identify participants (from transcript headers, notes, or user input)\n   |\n2. EXTRACT key topics\n   |\n   +--> Categorize discussion points (see Topic Categorization below)\n   +--> Capture direct quotes that carry weight (decisions, commitments, objections)\n   +--> Note topics raised but not resolved — these become open items\n   |\n3. IDENTIFY action items\n   |\n   +--> For each commitment or next step mentioned:\n   |      Owner (our side \u002F their side \u002F joint)\n   |      Action (specific and verifiable)\n   |      Deadline (stated or inferred from context)\n   |      Priority (blocks deal progression \u002F important \u002F nice-to-have)\n   |\n4. FLAG objections and concerns\n   |\n   +--> Capture the objection as stated (not paraphrased away)\n   +--> Note whether it was addressed, partially addressed, or left open\n   +--> Record the response given (if any) for consistency in future calls\n   +--> Classify by type (see Objection Classification below)\n   |\n5. ASSESS deal impact\n   |\n   +--> Did the call advance, stall, or regress the deal?\n   +--> What changed about our understanding of the opportunity?\n   +--> Are there new stakeholders, risks, or timeline shifts?\n   |\n6. DRAFT follow-up (see Follow-Up Email Framework below)\n   |\n7. COMPILE output (see Output Templates below)\n```\n\n## Topic Categorization\n\nClassify each discussion topic to make the summary scannable:\n\n| Category | What It Covers | CRM Relevance |\n| --- | --- | --- |\n| **Requirements** | Stated needs, use cases, evaluation criteria | Update opportunity requirements |\n| **Decision Process** | Timeline, stakeholders involved, approval steps | Update close date, decision map |\n| **Budget \u002F Commercial** | Pricing discussion, budget constraints, ROI expectations | Update deal value, stage |\n| **Technical** | Integration needs, security, compliance, architecture | Log as technical requirements |\n| **Competitive** | Mentions of alternatives, incumbent vendor, evaluation comparison | Update competitive field in CRM |\n| **Relationship** | Rapport signals, internal politics, champion strength indicators | Update stakeholder notes |\n| **Next Steps** | Agreed actions, follow-up meetings, deliverables promised | Create CRM tasks |\n\n## Objection Classification\n\n| Type | Definition | Follow-Up Priority |\n| --- | --- | --- |\n| **Deal-blocking** | Objection that will prevent close if unresolved | Immediate |\n| **Stage-blocking** | Prevents advancement to next stage but not necessarily a deal-killer | High |\n| **Concern** | Expressed worry that needs addressing but is not blocking progress | Medium |\n| **Skepticism** | General doubt about value or approach — needs proof points | Medium |\n| **Clarification** | Misunderstanding or information gap — easily resolved with data | Low |\n\nFor each objection, track: stated objection (verbatim or near-verbatim), classification, response given during the call, resolution status (resolved \u002F partially addressed \u002F open), and recommended follow-up action.\n\n## Follow-Up Email Framework\n\nThe follow-up email should be sendable with minimal editing. Structure:\n\n### Tone Calibration\n\n| Relationship Stage | Tone | Formality |\n| --- | --- | --- |\n| **First interaction** | Professional, appreciative of time | Formal |\n| **Active evaluation** | Collaborative, momentum-focused | Semi-formal |\n| **Established rapport** | Direct, efficient, partnership tone | Conversational |\n| **Executive audience** | Concise, outcome-focused | Formal |\n\n### Email Structure\n\n```\nSubject: [Descriptive, action-oriented — never generic like \"Meeting follow-up\"]\n\n[Opening: 1 sentence — thank + reference a specific moment from the call]\n\n[Summary: 3-5 bullet points of what was discussed — phrased in terms\n of their priorities and language, not your product features]\n\n[Action Items: clear table or list]\n  - What we committed to doing → by when\n  - What we're asking them to do → by when\n\n[Next Step: specific — date, time, agenda for next interaction]\n\n[Close: 1 sentence — express enthusiasm about the specific outcome\n discussed, not generic excitement]\n```\n\n### Follow-Up Quality Checklist\n\n- References something specific from the conversation (proves you listened)\n- Uses their language and terminology, not internal jargon\n- Action items have owners and dates\n- Next step is specific and time-bound\n- No markdown formatting (plain text or minimal HTML for email clients)\n- Subject line would make sense in their inbox without additional context\n- Appropriate length: 150-250 words for standard follow-ups\n\n## Output Template — Call Summary\n\n```\n# Call Summary: [Meeting Title \u002F Company Name]\n**Date**: [Call date]  |  **Duration**: [Actual length]\n**Call Type**: [Discovery \u002F Demo \u002F Negotiation \u002F Check-In]\n**Participants**: [List with roles]\n\n## Key Topics Discussed\n| # | Topic   | Category   | Summary                |\n|---|---------|------------|------------------------|\n| 1 | [Topic] | [Category] | [2-3 sentence summary] |\n| 2 | [Topic] | [Category] | [2-3 sentence summary] |\n\n## Action Items\n| #  | Action            | Owner | Deadline | Priority         |\n|----|-------------------|-------|----------|------------------|\n| 1  | [Specific action] | [Who] | [When]   | [Classification] |\n\n## Objections & Concerns\n| Objection   | Type             | Status           | Follow-Up Needed     |\n|-------------|------------------|------------------|----------------------|\n| [As stated] | [Classification] | [Open\u002FAddressed] | [Recommended action] |\n\n## Deal Impact Assessment\n- **Deal Movement**: [Advanced \u002F Stalled \u002F Regressed \u002F Neutral]\n- **Stage Recommendation**: [Stay \u002F Advance to X \u002F Flag for review]\n- **New Information**: [What we learned that changes our understanding]\n- **Risk Changes**: [New risks surfaced or existing risks mitigated]\n\n## Follow-Up Email Draft\n[Ready-to-send email following the framework above]\n```\n\n## Processing Notes for Transcript Quality\n\n| Input Quality | Handling |\n| --- | --- |\n| **Full transcript** | Extract verbatim quotes for key moments; comprehensive summary |\n| **Structured notes** | Organize into framework; flag potential gaps in coverage |\n| **Bullet-point recap** | Build summary from bullets; note that nuance may be missing |\n| **Partial \u002F fragmentary** | Summarize what is available; clearly mark sections as \"[Incomplete — ask rep to fill gaps]\" |\n\n## Guardrails\n\n1. Never fabricate call content. Every topic, quote, and action item must be traceable to the provided notes or transcript. Ambiguous content: \"[Unclear from notes — verify with attendees]\".\n2. Never invent attendee reactions. Do not characterise sentiment or buy-in unless explicitly stated in the notes.\n3. Objection accuracy. Capture objections as close to verbatim as the source allows. Do not soften, reframe, or minimise stated concerns.\n4. Source labeling. Tag assertions — [From transcript], [From notes], [From user input], [AI interpretation]. AI interpretations must be flagged for verification.\n\n> **Tip:** Ask for DOCX or Markdown output via companyFILES to get a formatted summary ready to share.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fsales\u002Fcall-summary-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 call-summary-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill call-summary-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill call-summary-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fcall-summary-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},"01M7AF3PXV26B9Y5DS2ZYSZDK4","call-prep-skill","Build a comprehensive call brief from CRM, calendar, and email context — attendees, deal history, open questions, recommended angles. Use when preparing for a sales call, demo, or customer meeting. Trigger with \"prep call with [person\u002Fcompany]\", \"call brief for\", \"what should I know before this meeting\".","https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fcall-prep-skill\u002FSKILL.md",[],[]]