[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF1WCD5YY8ZN8XENQ25MV3":3,"skill-same:01M7AF1WCD5YY8ZN8XENQ25MV3":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},"01M7AF1WCD5YY8ZN8XENQ25MV3","competitor-brief-skill",null,"Create competitive analysis documents for product strategy decisions, feature prioritisation, and differentiation. Use when a competitor launches something new, entering a new market segment, or preparing for a strategy review. Trigger with \"competitive brief on\", \"what is [competitor] doing\", \"compare us to [competitor]\".","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\u002Fproduct-management\u002Fcompetitor-brief-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: competitor-brief-skill\ndescription: Create competitive analysis documents for product strategy decisions, feature prioritisation, and differentiation. Use when a competitor launches something new, entering a new market segment, or preparing for a strategy review. Trigger with \"competitive brief on\", \"what is [competitor] doing\", \"compare us to [competitor]\".\n---\n\n# Competitor Brief Skill\n\nBuild competitive intelligence briefs that inform product strategy, feature prioritisation, and market positioning. All competitive data must come from you, companyRAG collections, or web search — never from training data.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **MCP servers** (e.g. CRM like HubSpot\u002FSalesforce, analyst or review platforms) | Sales-call notes, churn interviews, prospect objections, RFP responses |\n| **companyRAG collections \u002F file upload** | Analyst reports, customer reviews, technical assessments, your own feature documentation |\n| **Web search** | Public product documentation, press coverage, job postings, patent applications, conference talks |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Competitive Brief Workflow\n\nRun these four phases in order. Each phase feeds the next.\n\n### Phase 1: Intelligence Gathering\n\nBefore analysis, establish what is known and what needs investigation.\n\n**Source inventory** — for each competitor being analysed:\n\n| Source Type | Examples | Reliability |\n| --- | --- | --- |\n| **Primary** | Direct product usage, free trials, public demos, published documentation | Highest — first-hand observation |\n| **Secondary** | Analyst reports, customer reviews (G2, Capterra), press coverage, blog posts | High — but may be outdated or biased |\n| **Field intelligence** | Sales-call notes, customer churn interviews, prospect objections, RFP responses | High for intent signals — but anecdotal |\n| **Public filings** | SEC filings, job postings, patent applications, conference talks | High for strategic direction — low for product detail |\n\n**Gap identification**: After inventorying sources, explicitly list what is NOT known. Unknown areas become research tasks, not assumptions.\n\n```\nINTELLIGENCE INVENTORY — [Competitor Name]\n  Known (sourced):    [List with source and recency date]\n  Partially known:    [List with gaps identified]\n  Unknown:            [List — these are research tasks, not areas to guess about]\n  Last updated:       [Date]\n```\n\n### Phase 2: Feature Comparison Matrix\n\nBuild a structured comparison of capabilities across evaluation dimensions relevant to your product category.\n\n**Matrix construction process**:\n\n1. Define dimensions: Use your product's own feature categories, not the competitor's marketing language. Dimensions should reflect how customers evaluate the category.\n2. Score capabilities: For each dimension, assess each player (your product + competitors):   - Strong: Fully addresses the need; no significant gaps   - Adequate: Addresses the core need; some limitations   - Weak: Partially addresses or does not address the need   - Unknown: Insufficient data — flag for research\n3. Add evidence: Every score must cite its source. Unsourced scores are assumptions.\n\n```\nFEATURE COMPARISON — [Category]\n| Dimension | Your Product | Competitor A | Competitor B | Notes |\n|---|---|---|---|---|\n| [dimension] | [score + source] | [score + source] | [score + source] | [key differences] |\n```\n\n**Scoring discipline**:\n\n- Score based on current shipped product, not announced roadmap\n- Do not give your own product favourable scores without evidence — self-serving analysis is worse than no analysis\n- \"Unknown\" is a valid and honest score — never fill gaps with assumptions\n- Refresh scores when any player ships a significant update\n\n### Phase 3: Strategic Analysis\n\nMove from feature comparison to strategic interpretation.\n\n#### Positioning Analysis\n\nMap each competitor's positioning along the dimensions that matter to your target segments:\n\n1. Value proposition: What problem do they lead with? Who is their ideal customer?\n2. Go-to-market motion: Self-serve vs. sales-led vs. partner-led? SMB vs. enterprise vs. both?\n3. Pricing model: Per-seat vs. usage-based vs. flat-rate? Free tier? Premium positioning?\n4. Differentiation claim: What do they say makes them different? Is the claim substantiated?\n\n#### Threat \u002F Opportunity Assessment\n\nFor each competitor, classify the strategic situation:\n\n| Signal | Classification | Implication |\n| --- | --- | --- |\n| Competitor strong where you are weak, in a dimension customers care about | **Threat — Active** | Requires response: build, partner, or reposition |\n| Competitor investing in your stronghold area (hiring, features, marketing) | **Threat — Emerging** | Monitor closely; prepare defensive positioning |\n| Competitor weak where you are strong, in a dimension customers care about | **Opportunity — Differentiation** | Amplify in positioning and sales enablement |\n| Competitor ignoring a segment or use case you serve well | **Opportunity — White space** | Lean into the underserved segment |\n| Competitor and you are equally strong | **Parity** | Compete on other dimensions (price, experience, trust, ecosystem) |\n\n#### Market Movement Indicators\n\nTrack signals that indicate strategic direction shifts:\n\n- Hiring patterns: What roles are they hiring for? (Engineering in new areas, sales in new geographies, specific domain expertise)\n- Partnership announcements: New integrations, channel partners, platform plays\n- Pricing changes: Lowering prices (land-grab), raising prices (value extraction), new tiers (segment expansion)\n- Acquisition activity: What capabilities are they buying?\n- Customer segment shifts: Are they moving upmarket, downmarket, or into adjacent segments?\n\n### Phase 4: Recommended Response\n\nFor each active threat or actionable opportunity, structure a response recommendation:\n\n```\nRESPONSE RECOMMENDATION:\n  Trigger:         [What competitive action prompted this?]\n  Classification:  [Threat — Active \u002F Threat — Emerging \u002F Opportunity]\n  Impact:          [Which of your segments, metrics, or positioning is affected?]\n  Response options:\n    1. [Build] — [What to build + rough scope + timeline implication]\n    2. [Partner] — [Partnership that could close the gap]\n    3. [Reposition] — [Messaging change to reframe the dimension]\n    4. [Monitor] — [Watch and reassess at next review cycle]\n  Recommended option: [number + rationale]\n  Decision owner:  [Who should approve this response?]\n  Urgency:         [Immediate \u002F This quarter \u002F Next planning cycle]\n```\n\n**Response selection criteria**:\n\n- Build when the gap is in a must-win dimension and you have the capacity\n- Partner when the gap is real but not your core competency\n- Reposition when the competitor's advantage matters less than they claim, or when you can reframe the evaluation criteria\n- Monitor when the threat is emerging but not yet impacting customers or pipeline\n\n## Output Template — Competitive Brief\n\n```\n# Competitive Brief — [Competitor Name]\nDate: [date]    |    Author: [name]    |    Classification: [Internal \u002F Confidential]\n\n## 1. Executive Summary\n[2-3 sentence overview: who they are, what changed, why it matters to us]\n\n## 2. Intelligence Inventory\n[Sources consulted, recency, known gaps]\n\n## 3. Feature Comparison Matrix\n[Structured comparison — see Phase 2]\n\n## 4. Positioning Analysis\n[Value proposition, GTM, pricing, differentiation — see Phase 3]\n\n## 5. Threat & Opportunity Assessment\n[Classified signals — see Phase 3]\n\n## 6. Recommended Response\n[Action items with owners and urgency — see Phase 4]\n\n## 7. Open Questions\n[What we still need to learn, with assigned research tasks]\n\n## 8. Review Cadence\n[When to revisit this brief — typically quarterly or after major competitor moves]\n```\n\n## Competitive Review Cadence\n\n| Trigger | Action |\n| --- | --- |\n| **Competitor launches major feature** | Update affected feature matrix rows; reassess threats |\n| **Quarterly planning** | Full brief refresh for top 2-3 competitors |\n| **Lost deal to competitor** | Post-mortem to update threat assessment and response |\n| **Entering new market segment** | Build new brief for segment-specific competitors |\n| **Competitor funding \u002F acquisition** | Update market movement indicators and strategic analysis |\n\n## Guardrails\n\n- NEVER generate competitor features, pricing, market share, or positioning from training data. All competitive claims must come from you, companyRAG collections, or web search with cited sources.\n- NEVER claim \"market standard\" or \"typical\" for any competitive dimension. Every assertion must be sourced.\n- When no competitor data is provided, generate the blank brief template and list the specific data needed — do not fill gaps with assumptions.\n- Source-label every assertion as `[From user \u002F companyRAG]`, `[From web search — {date}]`, `[Analysis framework]`, or `[AI assessment — verify]`.\n\n> **Tip:** Ask for DOCX, Markdown, or PPTX output via companyFILES to get a formatted brief ready to share.\n","# Competitor Brief Skill\n\nBuild competitive intelligence briefs that inform product strategy, feature prioritisation, and market positioning. All competitive data must come from you, companyRAG collections, or web search — never from training data.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **MCP servers** (e.g. CRM like HubSpot\u002FSalesforce, analyst or review platforms) | Sales-call notes, churn interviews, prospect objections, RFP responses |\n| **companyRAG collections \u002F file upload** | Analyst reports, customer reviews, technical assessments, your own feature documentation |\n| **Web search** | Public product documentation, press coverage, job postings, patent applications, conference talks |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Competitive Brief Workflow\n\nRun these four phases in order. Each phase feeds the next.\n\n### Phase 1: Intelligence Gathering\n\nBefore analysis, establish what is known and what needs investigation.\n\n**Source inventory** — for each competitor being analysed:\n\n| Source Type | Examples | Reliability |\n| --- | --- | --- |\n| **Primary** | Direct product usage, free trials, public demos, published documentation | Highest — first-hand observation |\n| **Secondary** | Analyst reports, customer reviews (G2, Capterra), press coverage, blog posts | High — but may be outdated or biased |\n| **Field intelligence** | Sales-call notes, customer churn interviews, prospect objections, RFP responses | High for intent signals — but anecdotal |\n| **Public filings** | SEC filings, job postings, patent applications, conference talks | High for strategic direction — low for product detail |\n\n**Gap identification**: After inventorying sources, explicitly list what is NOT known. Unknown areas become research tasks, not assumptions.\n\n```\nINTELLIGENCE INVENTORY — [Competitor Name]\n  Known (sourced):    [List with source and recency date]\n  Partially known:    [List with gaps identified]\n  Unknown:            [List — these are research tasks, not areas to guess about]\n  Last updated:       [Date]\n```\n\n### Phase 2: Feature Comparison Matrix\n\nBuild a structured comparison of capabilities across evaluation dimensions relevant to your product category.\n\n**Matrix construction process**:\n\n1. Define dimensions: Use your product's own feature categories, not the competitor's marketing language. Dimensions should reflect how customers evaluate the category.\n2. Score capabilities: For each dimension, assess each player (your product + competitors):   - Strong: Fully addresses the need; no significant gaps   - Adequate: Addresses the core need; some limitations   - Weak: Partially addresses or does not address the need   - Unknown: Insufficient data — flag for research\n3. Add evidence: Every score must cite its source. Unsourced scores are assumptions.\n\n```\nFEATURE COMPARISON — [Category]\n| Dimension | Your Product | Competitor A | Competitor B | Notes |\n|---|---|---|---|---|\n| [dimension] | [score + source] | [score + source] | [score + source] | [key differences] |\n```\n\n**Scoring discipline**:\n\n- Score based on current shipped product, not announced roadmap\n- Do not give your own product favourable scores without evidence — self-serving analysis is worse than no analysis\n- \"Unknown\" is a valid and honest score — never fill gaps with assumptions\n- Refresh scores when any player ships a significant update\n\n### Phase 3: Strategic Analysis\n\nMove from feature comparison to strategic interpretation.\n\n#### Positioning Analysis\n\nMap each competitor's positioning along the dimensions that matter to your target segments:\n\n1. Value proposition: What problem do they lead with? Who is their ideal customer?\n2. Go-to-market motion: Self-serve vs. sales-led vs. partner-led? SMB vs. enterprise vs. both?\n3. Pricing model: Per-seat vs. usage-based vs. flat-rate? Free tier? Premium positioning?\n4. Differentiation claim: What do they say makes them different? Is the claim substantiated?\n\n#### Threat \u002F Opportunity Assessment\n\nFor each competitor, classify the strategic situation:\n\n| Signal | Classification | Implication |\n| --- | --- | --- |\n| Competitor strong where you are weak, in a dimension customers care about | **Threat — Active** | Requires response: build, partner, or reposition |\n| Competitor investing in your stronghold area (hiring, features, marketing) | **Threat — Emerging** | Monitor closely; prepare defensive positioning |\n| Competitor weak where you are strong, in a dimension customers care about | **Opportunity — Differentiation** | Amplify in positioning and sales enablement |\n| Competitor ignoring a segment or use case you serve well | **Opportunity — White space** | Lean into the underserved segment |\n| Competitor and you are equally strong | **Parity** | Compete on other dimensions (price, experience, trust, ecosystem) |\n\n#### Market Movement Indicators\n\nTrack signals that indicate strategic direction shifts:\n\n- Hiring patterns: What roles are they hiring for? (Engineering in new areas, sales in new geographies, specific domain expertise)\n- Partnership announcements: New integrations, channel partners, platform plays\n- Pricing changes: Lowering prices (land-grab), raising prices (value extraction), new tiers (segment expansion)\n- Acquisition activity: What capabilities are they buying?\n- Customer segment shifts: Are they moving upmarket, downmarket, or into adjacent segments?\n\n### Phase 4: Recommended Response\n\nFor each active threat or actionable opportunity, structure a response recommendation:\n\n```\nRESPONSE RECOMMENDATION:\n  Trigger:         [What competitive action prompted this?]\n  Classification:  [Threat — Active \u002F Threat — Emerging \u002F Opportunity]\n  Impact:          [Which of your segments, metrics, or positioning is affected?]\n  Response options:\n    1. [Build] — [What to build + rough scope + timeline implication]\n    2. [Partner] — [Partnership that could close the gap]\n    3. [Reposition] — [Messaging change to reframe the dimension]\n    4. [Monitor] — [Watch and reassess at next review cycle]\n  Recommended option: [number + rationale]\n  Decision owner:  [Who should approve this response?]\n  Urgency:         [Immediate \u002F This quarter \u002F Next planning cycle]\n```\n\n**Response selection criteria**:\n\n- Build when the gap is in a must-win dimension and you have the capacity\n- Partner when the gap is real but not your core competency\n- Reposition when the competitor's advantage matters less than they claim, or when you can reframe the evaluation criteria\n- Monitor when the threat is emerging but not yet impacting customers or pipeline\n\n## Output Template — Competitive Brief\n\n```\n# Competitive Brief — [Competitor Name]\nDate: [date]    |    Author: [name]    |    Classification: [Internal \u002F Confidential]\n\n## 1. Executive Summary\n[2-3 sentence overview: who they are, what changed, why it matters to us]\n\n## 2. Intelligence Inventory\n[Sources consulted, recency, known gaps]\n\n## 3. Feature Comparison Matrix\n[Structured comparison — see Phase 2]\n\n## 4. Positioning Analysis\n[Value proposition, GTM, pricing, differentiation — see Phase 3]\n\n## 5. Threat & Opportunity Assessment\n[Classified signals — see Phase 3]\n\n## 6. Recommended Response\n[Action items with owners and urgency — see Phase 4]\n\n## 7. Open Questions\n[What we still need to learn, with assigned research tasks]\n\n## 8. Review Cadence\n[When to revisit this brief — typically quarterly or after major competitor moves]\n```\n\n## Competitive Review Cadence\n\n| Trigger | Action |\n| --- | --- |\n| **Competitor launches major feature** | Update affected feature matrix rows; reassess threats |\n| **Quarterly planning** | Full brief refresh for top 2-3 competitors |\n| **Lost deal to competitor** | Post-mortem to update threat assessment and response |\n| **Entering new market segment** | Build new brief for segment-specific competitors |\n| **Competitor funding \u002F acquisition** | Update market movement indicators and strategic analysis |\n\n## Guardrails\n\n- NEVER generate competitor features, pricing, market share, or positioning from training data. All competitive claims must come from you, companyRAG collections, or web search with cited sources.\n- NEVER claim \"market standard\" or \"typical\" for any competitive dimension. Every assertion must be sourced.\n- When no competitor data is provided, generate the blank brief template and list the specific data needed — do not fill gaps with assumptions.\n- Source-label every assertion as `[From user \u002F companyRAG]`, `[From web search — {date}]`, `[Analysis framework]`, or `[AI assessment — verify]`.\n\n> **Tip:** Ask for DOCX, Markdown, or PPTX output via companyFILES to get a formatted brief ready to share.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fproduct-management\u002Fcompetitor-brief-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 competitor-brief-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill competitor-brief-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill competitor-brief-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fproduct-management\u002Fcompetitor-brief-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",[],[]]