[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF48W7G8DMAHRAM125B192":3,"skill-same:01M7AF48W7G8DMAHRAM125B192":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},"01M7AF48W7G8DMAHRAM125B192","outreach-skill",null,"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\".","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\u002Foutreach-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: outreach-skill\ndescription: 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\".\n---\n\n# Outreach Skill\n\nPair prospect intelligence with message crafting to produce personalised, multi-channel outreach — initial messages, subject-line variants, follow-up sequences, and LinkedIn connection requests. Prospect data comes from you, a connected MCP source, companyRAG collections, or file upload.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CRM via MCP** (e.g. Salesforce, HubSpot, Dynamics) | Prior interactions, deal history, contact status, do-not-contact flags |\n| **Sales-engagement \u002F enrichment tools via MCP** (e.g. LinkedIn, company website, news) | Role context, recent activity, company signals, mutual connections |\n| **companyRAG collections** | ICP definitions, messaging frameworks, relevant proof points |\n| **companyRAG \u002F file upload** | Trigger events, public statements, shared interests, context material |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Outreach Workflow\n\n```\n1. CHECK existing relationship\n   |\n   +--> Search CRM for prospect and account\n   |      EXISTING CONTACT --> Review history, last interaction, opt-out status\n   |      PRIOR DEAL --> Adjust tone: re-engagement, not cold outreach\n   |      NO RECORD --> Proceed as net-new outreach\n   |\n2. RESEARCH the prospect (person-level)\n   |\n   +--> Current role, tenure, and scope of responsibility\n   +--> Recent professional activity (posts, talks, job change, promotion)\n   +--> Stated priorities or challenges (interviews, panel quotes, blog posts)\n   +--> Mutual connections or shared context (events, groups, alma mater)\n   |\n3. RESEARCH the account (company-level)\n   |\n   +--> Recent signals: funding, product launch, leadership change, hiring surge\n   +--> Industry context: regulatory shifts, competitive moves, market trends\n   +--> Technology stack indicators (if relevant to your solution)\n   |\n4. IDENTIFY personalisation hooks\n   |\n   +--> Match prospect\u002Faccount signals to value propositions\n   +--> Rank hooks by specificity and recency (see Hook Ranking below)\n   +--> Select 1-2 primary hooks per message\n   |\n5. DRAFT message(s)\n   |\n   +--> Select channel and format (see Channel Routing below)\n   +--> Apply message structure (see Message Architecture below)\n   +--> Generate subject-line variants (email only)\n   +--> Review against quality criteria\n   |\n6. BUILD follow-up sequence (if multi-touch)\n   |\n   +--> Design 3-5 touch sequence with varied angles\n   +--> Space touches appropriately (see Sequence Architecture below)\n   +--> Each touch adds new value or angle — never just \"bumping\" the thread\n   |\n7. COMPILE output (see Output Template below)\n```\n\n## Hook Ranking\n\nNot all personalisation is equal. Rank hooks by impact:\n\n| Rank | Hook Type | Example | Why It Works |\n| --- | --- | --- | --- |\n| 1 | **Trigger event + role match** | \"Saw you just took over EMEA ops — that's when teams often evaluate...\" | Timely + relevant to their new mandate |\n| 2 | **Stated priority + your value** | \"You mentioned [priority] at [event] — we help teams...\" | Proves research + direct relevance |\n| 3 | **Mutual connection referral** | \"[Name] suggested I reach out because...\" | Warm intro through trusted contact |\n| 4 | **Company signal + implication** | \"With [company]'s expansion into [market], teams often face...\" | Shows you understand their business context |\n| 5 | **Shared context** | \"Fellow [group] member — noticed your post about...\" | Genuine common ground |\n| 6 | **Industry trend + specificity** | \"Teams in [their specific sub-sector] are dealing with...\" | Relevant but less personal |\n\nHooks ranked 1-3 are strong enough to open a message. Hooks ranked 4-6 are supporting context, better as second-sentence reinforcement.\n\n## Channel Routing\n\n| Channel | Best For | Length Guideline | Tone |\n| --- | --- | --- | --- |\n| **Email** | Detailed value prop, multi-stakeholder, formal industries | 80-150 words body | Professional |\n| **LinkedIn message** | Peer-to-peer, tech\u002Fstartup, after connection accepted | 50-80 words | Conversational |\n| **LinkedIn InMail** | Cold outreach when no email, senior prospects | 60-100 words | Professional-casual |\n| **LinkedIn connection request** | First touch, building network | Under 300 characters | Brief, specific |\n\n## Message Architecture\n\nEvery outreach message follows this structure regardless of channel:\n\n### Line-by-Line Framework\n\n| Section | Purpose | Length |\n| --- | --- | --- |\n| **Opening line** | Personalised hook — why you are reaching out to them specifically | 1 sentence |\n| **Context bridge** | Connect the hook to a problem or opportunity they likely face | 1-2 sentences |\n| **Value statement** | What outcome you help achieve — not what your product does | 1 sentence |\n| **Proof point** | Credibility signal — specific result, named customer, metric | 1 sentence (optional in short formats) |\n| **Call to action** | Specific, low-friction ask | 1 sentence |\n\n### Opening-Line Patterns (Select Based on Hook)\n\n- Trigger: \"I noticed [specific event] — when teams go through [change], they often...\"\n- Referral: \"[Name] mentioned you're the right person to talk to about [topic]...\"\n- Content: \"Your [post\u002Ftalk] on [topic] resonated — especially the point about...\"\n- Observation: \"Looking at how [company] is approaching [initiative], I had a thought about...\"\n\n### Call-to-Action Patterns\n\n| CTA Type | When to Use | Example |\n| --- | --- | --- |\n| **Question CTA** | Discovery-stage, low commitment | \"Is [specific problem] on your radar this quarter?\" |\n| **Meeting CTA** | When intent signals are present | \"Worth a 20-minute conversation next week?\" |\n| **Resource CTA** | Nurture-stage, building credibility | \"I put together a [brief\u002Fanalysis] — want me to send it over?\" |\n| **Introduction CTA** | Multi-threaded, need different stakeholder | \"Who on your team owns [function]?\" |\n\n## Subject-Line Methodology (Email Only)\n\nGenerate 3 subject-line variants per email, testing different angles:\n\n| Variant Type | Pattern | Example |\n| --- | --- | --- |\n| **Trigger-based** | References the specific signal | \"[Company]'s EMEA expansion + [topic]\" |\n| **Question-based** | Poses the problem as a question | \"How is [company] handling [challenge]?\" |\n| **Outcome-based** | Leads with the result | \"[Metric improvement] for [their industry] teams\" |\n\nSubject-line rules: under 50 characters preferred, no ALL CAPS, no spam-trigger words, no false urgency, no misleading Re: or Fwd: prefixes.\n\n## Sequence Architecture\n\nFor multi-touch sequences, vary the angle with each touch:\n\n| Touch | Timing | Angle | Channel |\n| --- | --- | --- | --- |\n| 1 | Day 0 | Primary hook + value statement | Email or LinkedIn |\n| 2 | Day 3-4 | New proof point or case study angle | Same or alternate |\n| 3 | Day 7-8 | Industry insight or resource offer | Alternate channel |\n| 4 | Day 14 | Different stakeholder angle or referral ask | Email |\n| 5 | Day 21-28 | Break-up: direct ask about fit\u002Ftiming | Email |\n\n### Sequence Rules\n\n- Each touch must introduce new value or a new angle — never \"just following up\" or \"bumping this\".\n- If the prospect responds at any point, exit the sequence and respond conversationally.\n- Respect opt-out signals: explicit requests, auto-replies indicating leave, or company-level do-not-contact.\n- Adjust timing for prospect seniority: C-suite gets longer gaps between touches.\n- Maximum sequence length: 5 touches over 4 weeks for cold outreach.\n\n## Output Template — Outreach Package\n\n```\n# Outreach: [Prospect Name] at [Company]\n**Channel**: [Email \u002F LinkedIn \u002F Multi-channel]\n**Sequence Length**: [Single message \u002F X-touch sequence]\n**Prospect Context**: [1-2 sentence summary of research]\n\n## Research Summary\n- **Role**: [Title, scope, tenure]\n- **Signals**: [Key triggers identified — with dates and sources]\n- **Hooks Selected**: [Ranked hooks chosen for this outreach]\n\n## Message 1: Initial Outreach\n**Subject Line Options** (email only):\n1. [Variant A]\n2. [Variant B]\n3. [Variant C]\n\n**Body**:\n[Full message text — plain text, no markdown formatting]\n\n---\n\n## Message 2: Follow-Up 1\n**Timing**: [Days after Message 1]\n**Angle**: [What is new in this touch]\n\n**Subject**: [Reply to thread or new subject]\n\n**Body**:\n[Full message text]\n\n---\n\n[Continue for each sequence touch]\n\n## Personalisation Notes\n- [Why specific hooks were chosen]\n- [Alternative angles if these don't land]\n- [Contacts to CC or reference if warming the thread]\n```\n\n## Guardrails\n\n1. Never fabricate prospect details. All names, titles, company facts, and activity must come from CRM, enrichment, web search, or user input. If research is thin, use bracketed placeholders: \"[insert specific signal].\"\n2. Never invent mutual connections. Only reference a mutual connection if confirmed by the user or CRM data.\n3. Opt-out awareness. If CRM indicates opt-out, do-not-contact, or unsubscribed status, refuse to draft outreach and flag the restriction.\n4. Source labeling. Tag research — [From CRM], [From LinkedIn], [From web search], [From user input], [AI draft].\n\n> **Tip:** Ask for DOCX or Markdown output via companyFILES to get a formatted outreach package ready to share.\n","# Outreach Skill\n\nPair prospect intelligence with message crafting to produce personalised, multi-channel outreach — initial messages, subject-line variants, follow-up sequences, and LinkedIn connection requests. Prospect data comes from you, a connected MCP source, companyRAG collections, or file upload.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CRM via MCP** (e.g. Salesforce, HubSpot, Dynamics) | Prior interactions, deal history, contact status, do-not-contact flags |\n| **Sales-engagement \u002F enrichment tools via MCP** (e.g. LinkedIn, company website, news) | Role context, recent activity, company signals, mutual connections |\n| **companyRAG collections** | ICP definitions, messaging frameworks, relevant proof points |\n| **companyRAG \u002F file upload** | Trigger events, public statements, shared interests, context material |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Outreach Workflow\n\n```\n1. CHECK existing relationship\n   |\n   +--> Search CRM for prospect and account\n   |      EXISTING CONTACT --> Review history, last interaction, opt-out status\n   |      PRIOR DEAL --> Adjust tone: re-engagement, not cold outreach\n   |      NO RECORD --> Proceed as net-new outreach\n   |\n2. RESEARCH the prospect (person-level)\n   |\n   +--> Current role, tenure, and scope of responsibility\n   +--> Recent professional activity (posts, talks, job change, promotion)\n   +--> Stated priorities or challenges (interviews, panel quotes, blog posts)\n   +--> Mutual connections or shared context (events, groups, alma mater)\n   |\n3. RESEARCH the account (company-level)\n   |\n   +--> Recent signals: funding, product launch, leadership change, hiring surge\n   +--> Industry context: regulatory shifts, competitive moves, market trends\n   +--> Technology stack indicators (if relevant to your solution)\n   |\n4. IDENTIFY personalisation hooks\n   |\n   +--> Match prospect\u002Faccount signals to value propositions\n   +--> Rank hooks by specificity and recency (see Hook Ranking below)\n   +--> Select 1-2 primary hooks per message\n   |\n5. DRAFT message(s)\n   |\n   +--> Select channel and format (see Channel Routing below)\n   +--> Apply message structure (see Message Architecture below)\n   +--> Generate subject-line variants (email only)\n   +--> Review against quality criteria\n   |\n6. BUILD follow-up sequence (if multi-touch)\n   |\n   +--> Design 3-5 touch sequence with varied angles\n   +--> Space touches appropriately (see Sequence Architecture below)\n   +--> Each touch adds new value or angle — never just \"bumping\" the thread\n   |\n7. COMPILE output (see Output Template below)\n```\n\n## Hook Ranking\n\nNot all personalisation is equal. Rank hooks by impact:\n\n| Rank | Hook Type | Example | Why It Works |\n| --- | --- | --- | --- |\n| 1 | **Trigger event + role match** | \"Saw you just took over EMEA ops — that's when teams often evaluate...\" | Timely + relevant to their new mandate |\n| 2 | **Stated priority + your value** | \"You mentioned [priority] at [event] — we help teams...\" | Proves research + direct relevance |\n| 3 | **Mutual connection referral** | \"[Name] suggested I reach out because...\" | Warm intro through trusted contact |\n| 4 | **Company signal + implication** | \"With [company]'s expansion into [market], teams often face...\" | Shows you understand their business context |\n| 5 | **Shared context** | \"Fellow [group] member — noticed your post about...\" | Genuine common ground |\n| 6 | **Industry trend + specificity** | \"Teams in [their specific sub-sector] are dealing with...\" | Relevant but less personal |\n\nHooks ranked 1-3 are strong enough to open a message. Hooks ranked 4-6 are supporting context, better as second-sentence reinforcement.\n\n## Channel Routing\n\n| Channel | Best For | Length Guideline | Tone |\n| --- | --- | --- | --- |\n| **Email** | Detailed value prop, multi-stakeholder, formal industries | 80-150 words body | Professional |\n| **LinkedIn message** | Peer-to-peer, tech\u002Fstartup, after connection accepted | 50-80 words | Conversational |\n| **LinkedIn InMail** | Cold outreach when no email, senior prospects | 60-100 words | Professional-casual |\n| **LinkedIn connection request** | First touch, building network | Under 300 characters | Brief, specific |\n\n## Message Architecture\n\nEvery outreach message follows this structure regardless of channel:\n\n### Line-by-Line Framework\n\n| Section | Purpose | Length |\n| --- | --- | --- |\n| **Opening line** | Personalised hook — why you are reaching out to them specifically | 1 sentence |\n| **Context bridge** | Connect the hook to a problem or opportunity they likely face | 1-2 sentences |\n| **Value statement** | What outcome you help achieve — not what your product does | 1 sentence |\n| **Proof point** | Credibility signal — specific result, named customer, metric | 1 sentence (optional in short formats) |\n| **Call to action** | Specific, low-friction ask | 1 sentence |\n\n### Opening-Line Patterns (Select Based on Hook)\n\n- Trigger: \"I noticed [specific event] — when teams go through [change], they often...\"\n- Referral: \"[Name] mentioned you're the right person to talk to about [topic]...\"\n- Content: \"Your [post\u002Ftalk] on [topic] resonated — especially the point about...\"\n- Observation: \"Looking at how [company] is approaching [initiative], I had a thought about...\"\n\n### Call-to-Action Patterns\n\n| CTA Type | When to Use | Example |\n| --- | --- | --- |\n| **Question CTA** | Discovery-stage, low commitment | \"Is [specific problem] on your radar this quarter?\" |\n| **Meeting CTA** | When intent signals are present | \"Worth a 20-minute conversation next week?\" |\n| **Resource CTA** | Nurture-stage, building credibility | \"I put together a [brief\u002Fanalysis] — want me to send it over?\" |\n| **Introduction CTA** | Multi-threaded, need different stakeholder | \"Who on your team owns [function]?\" |\n\n## Subject-Line Methodology (Email Only)\n\nGenerate 3 subject-line variants per email, testing different angles:\n\n| Variant Type | Pattern | Example |\n| --- | --- | --- |\n| **Trigger-based** | References the specific signal | \"[Company]'s EMEA expansion + [topic]\" |\n| **Question-based** | Poses the problem as a question | \"How is [company] handling [challenge]?\" |\n| **Outcome-based** | Leads with the result | \"[Metric improvement] for [their industry] teams\" |\n\nSubject-line rules: under 50 characters preferred, no ALL CAPS, no spam-trigger words, no false urgency, no misleading Re: or Fwd: prefixes.\n\n## Sequence Architecture\n\nFor multi-touch sequences, vary the angle with each touch:\n\n| Touch | Timing | Angle | Channel |\n| --- | --- | --- | --- |\n| 1 | Day 0 | Primary hook + value statement | Email or LinkedIn |\n| 2 | Day 3-4 | New proof point or case study angle | Same or alternate |\n| 3 | Day 7-8 | Industry insight or resource offer | Alternate channel |\n| 4 | Day 14 | Different stakeholder angle or referral ask | Email |\n| 5 | Day 21-28 | Break-up: direct ask about fit\u002Ftiming | Email |\n\n### Sequence Rules\n\n- Each touch must introduce new value or a new angle — never \"just following up\" or \"bumping this\".\n- If the prospect responds at any point, exit the sequence and respond conversationally.\n- Respect opt-out signals: explicit requests, auto-replies indicating leave, or company-level do-not-contact.\n- Adjust timing for prospect seniority: C-suite gets longer gaps between touches.\n- Maximum sequence length: 5 touches over 4 weeks for cold outreach.\n\n## Output Template — Outreach Package\n\n```\n# Outreach: [Prospect Name] at [Company]\n**Channel**: [Email \u002F LinkedIn \u002F Multi-channel]\n**Sequence Length**: [Single message \u002F X-touch sequence]\n**Prospect Context**: [1-2 sentence summary of research]\n\n## Research Summary\n- **Role**: [Title, scope, tenure]\n- **Signals**: [Key triggers identified — with dates and sources]\n- **Hooks Selected**: [Ranked hooks chosen for this outreach]\n\n## Message 1: Initial Outreach\n**Subject Line Options** (email only):\n1. [Variant A]\n2. [Variant B]\n3. [Variant C]\n\n**Body**:\n[Full message text — plain text, no markdown formatting]\n\n---\n\n## Message 2: Follow-Up 1\n**Timing**: [Days after Message 1]\n**Angle**: [What is new in this touch]\n\n**Subject**: [Reply to thread or new subject]\n\n**Body**:\n[Full message text]\n\n---\n\n[Continue for each sequence touch]\n\n## Personalisation Notes\n- [Why specific hooks were chosen]\n- [Alternative angles if these don't land]\n- [Contacts to CC or reference if warming the thread]\n```\n\n## Guardrails\n\n1. Never fabricate prospect details. All names, titles, company facts, and activity must come from CRM, enrichment, web search, or user input. If research is thin, use bracketed placeholders: \"[insert specific signal].\"\n2. Never invent mutual connections. Only reference a mutual connection if confirmed by the user or CRM data.\n3. Opt-out awareness. If CRM indicates opt-out, do-not-contact, or unsubscribed status, refuse to draft outreach and flag the restriction.\n4. Source labeling. Tag research — [From CRM], [From LinkedIn], [From web search], [From user input], [AI draft].\n\n> **Tip:** Ask for DOCX or Markdown output via companyFILES to get a formatted outreach package ready to share.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fsales\u002Foutreach-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 outreach-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill outreach-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill outreach-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Foutreach-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},"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":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},"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":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},"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",[],[],{"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",[],[]]