[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AF4HHK5B987T44HW7BZFVZ":3,"skill-same:01M7AF4HHK5B987T44HW7BZFVZ":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},"01M7AF4HHK5B987T44HW7BZFVZ","sales-asset-skill",null,"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\".","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\u002Fsales-asset-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sales-asset-skill\ndescription: 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\".\n---\n\n# Sales Asset Skill\n\nProduce deal-specific sales collateral — one-pagers, case study drafts, executive summaries, demo narratives, and proposal inserts — personalised to the buyer's industry, role, and stated priorities. All product information, case studies, pricing, and deal context comes from you, companyRAG collections, or a connected CRM.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CRM via MCP** (e.g. HubSpot, Salesforce) | Deal stage, deal value, stakeholders, competitive situation, closed-won notes |\n| **companyRAG collections** | Product specs, case studies, proof points, industry references |\n| **File upload** | Discovery notes, battlecards, account research, call summaries |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Asset-Type Routing\n\nIdentify the right asset format based on the sales situation:\n\n| Situation | Recommended Asset | Purpose |\n| --- | --- | --- |\n| First meeting — leave-behind for champion | **One-Pager** | Concise overview the champion can forward internally |\n| Executive sponsor engagement | **Executive Summary** | Business-outcome focused, minimal technical detail |\n| Technical evaluation underway | **Solution Brief** | Architecture, integration, security, compliance focus |\n| Prospect asked \"who else uses this?\" | **Case Study Draft** | Social proof mapped to their industry\u002Fuse case |\n| Demo scheduled — need a narrative arc | **Demo Narrative** | Storyline tying demo flow to their specific pain |\n| Proposal or RFP response section | **Proposal Insert** | Tailored section addressing specific evaluation criteria |\n| Multi-stakeholder deal — different needs | **Messaging Matrix** | Stakeholder-specific value props in one reference doc |\n\nWhen the user's request does not clearly map to one type, ask clarifying questions about audience, timing, and intended use before drafting.\n\n## Asset Creation Workflow\n\n```\n1. IDENTIFY asset type and audience\n   |\n   +--> Route to asset type (table above)\n   +--> Identify primary audience: role, seniority, technical depth\n   +--> Identify secondary audience: who else will see this?\n   +--> Determine context: where in the deal cycle, what prompted the request\n   |\n2. GATHER deal context\n   |\n   +--> From CRM: deal stage, value, stakeholders, competitive situation\n   +--> From user: specific pain points, evaluation criteria, buyer language\n   +--> From companyRAG collections: product specs, case studies, proof points\n   +--> From prior skills: account research, call summaries, battlecard intel\n   |\n3. MAP messaging to persona\n   |\n   +--> Apply the Persona-Message Matrix (see below)\n   +--> Select value propositions ranked by relevance to this buyer\n   +--> Choose proof points that match their industry and company size\n   +--> Adapt language register to audience seniority and function\n   |\n4. GENERATE draft\n   |\n   +--> Apply the asset-specific template (see Asset Templates below)\n   +--> Ensure every claim is backed by a source or flagged as needing one\n   +--> Check against quality criteria before presenting\n   |\n5. REVIEW and refine\n   |\n   +--> Run the Asset Review Checklist (see below)\n   +--> Flag sections that need user input or approval\n   +--> Suggest alternative framings for key messages\n```\n\n## Persona-Message Matrix\n\nMatch messaging emphasis to the buyer's role and priorities:\n\n| Persona | Primary Concerns | Message Emphasis | Proof-Point Type |\n| --- | --- | --- | --- |\n| **C-Suite \u002F Executive** | Revenue impact, risk, strategic alignment | Business outcomes, ROI, competitive advantage | Revenue metrics, market position |\n| **VP \u002F Director** | Team productivity, budget justification | Operational efficiency, time-to-value, TCO | Productivity gains, cost savings |\n| **Manager \u002F Team Lead** | Day-to-day impact, adoption, workflow fit | Ease of use, integration, support quality | User satisfaction, adoption rates |\n| **Technical Evaluator** | Architecture, security, scalability | Technical specs, compliance, API coverage | Technical benchmarks, certifications |\n| **Procurement** | Cost, contract terms, vendor risk | Pricing transparency, vendor stability, SLAs | Financial health, customer count |\n| **End User \u002F Practitioner** | Daily workflow, learning curve, reliability | Usability, speed, reliability, support | User testimonials, ease-of-use metrics |\n\n### Language Register by Seniority\n\n| Audience Level | Register | Avoid |\n| --- | --- | --- |\n| **Executive** | Concise, outcome-first, strategic framing, minimal jargon | Feature lists, technical specifications, acronyms |\n| **Management** | Balanced — outcomes with supporting detail, metric-driven | Vague claims without numbers, excessive length |\n| **Practitioner** | Specific, practical, workflow-oriented, technically precise | High-level platitudes, marketing superlatives |\n\n## Asset Templates\n\n### One-Pager Template\n\n```\n# [Solution Name] for [Industry \u002F Use Case]\n\n## The Challenge\n[1-2 sentences describing the specific problem this prospect faces — use their language, not yours]\n\n## How [Solution] Helps\n[3-4 bullet points — each structured as: Outcome → How it works → Proof]\n- **[Outcome]**: [Brief mechanism] — [Proof point with metric]\n- **[Outcome]**: [Brief mechanism] — [Proof point with metric]\n- **[Outcome]**: [Brief mechanism] — [Proof point with metric]\n\n## Why [Company Name] Specifically\n[2-3 sentences connecting your differentiation to their stated evaluation criteria or competitive situation]\n\n## Customer Proof\n\"[Quote from a reference customer in their industry or similar use case]\"\n— [Name, Title, Company]   |   [Key metric achieved]\n\n## Next Step\n[Specific CTA relevant to where they are in the deal cycle]\n```\n\n### Executive Summary Template\n\n```\n# Executive Summary: [Solution] for [Prospect Company]\n\n**Prepared for**: [Name, Title]\n**Date**: [Date]\n\n## Strategic Context\n[2-3 sentences on the business challenge, framed in terms of their strategic priorities — reference annual report, earnings call, or stated goals if available]\n\n## Recommended Approach\n[Brief description of the proposed solution — outcomes first, then how — never feature-first]\n\n## Expected Business Impact\n| Outcome Area          | Current State        | Projected Improvement | Basis               |\n| --------------------- | -------------------- | --------------------- | ------------------- |\n| [Area]                | [Metric if known]    | [Projected change]    | [Source\u002Fcomparables]|\n\n## Risk Mitigation\n[Address the top 2-3 concerns this executive likely has — security, integration, change management, vendor stability]\n\n## Investment Overview\n[High-level framing — not detailed pricing. Position as investment with expected return, not a cost]\n\n## Recommended Next Step\n[Specific, executive-appropriate ask]\n```\n\n### Case Study Draft Template\n\n```\n# [Customer Name]: [Headline Result]\n\n## Company Profile\n- **Industry**: [Sector]  |  **Size**: [Employees \u002F Revenue]\n- **Use Case**: [What they were trying to accomplish]\n\n## The Challenge\n[3-4 sentences — the specific problem, its business impact, and why previous approaches fell short]\n\n## The Solution\n[How they implemented your solution — timeline, scope, approach. Focus on decisions, not features]\n\n## Results\n| Metric              | Before           | After            | Improvement         |\n| ------------------- | ---------------- | ---------------- | ------------------- |\n| [KPI]               | [Value]          | [Value]          | [% or absolute]     |\n\n## Key Quote\n\"[Customer quote that captures the transformation]\"\n— [Name, Title]\n\n## Relevance to [Prospect]\n[2-3 sentences explaining why this case study is specifically relevant to the prospect's situation]\n```\n\n### Demo Narrative Template\n\n```\n# Demo Narrative: [Prospect Company]\n\n**Audience**: [Names, roles]\n**Duration**: [Scheduled time]\n**Objective**: [What success looks like for this demo]\n\n## Opening Context (2 min)\n[Connect their stated challenge to what they are about to see. Reference a specific conversation or discovery finding.]\n\n## Scene 1: [Pain Point → Capability] (X min)\n- **Setup**: \"[Describe the scenario in their terms]\"\n- **Show**: [Specific feature\u002Fworkflow to demonstrate]\n- **Outcome**: \"[What this means for their team]\"\n- **Check-in question**: \"[Gauge reaction and relevance]\"\n\n## Scene 2: [Pain Point → Capability] (X min)\n[Same structure]\n\n## Scene 3: [Differentiator Moment] (X min)\n- **Setup**: \"[This is where we are different from alternatives]\"\n- **Show**: [Unique capability mapped to their evaluation criteria]\n- **Bridge**: \"[Tie back to their decision criteria]\"\n\n## Closing (3 min)\n- Recap: [3 key takeaways mapped to their priorities]\n- Ask: \"[Next-step proposal]\"\n- Leave-behind: [What you will send after — one-pager, trial, proposal]\n\n## Backup Scenes\n[2-3 additional features ready if specific questions arise or time allows — do not show unless prompted]\n```\n\n### Messaging Matrix Template\n\n```\n# Messaging Matrix: [Deal Name]\n\n| Stakeholder         | Title          | Primary Pain         | Value Prop                   | Proof Point               | Key Objection           | Talk Track                      |\n| ------------------- | -------------- | -------------------- | ---------------------------- | ------------------------- | ----------------------- | ------------------------------- |\n| [Name]              | [Role]         | [Their top concern]  | [Tailored value statement]   | [Relevant case\u002Fmetric]    | [Likely pushback]       | [How to frame the conversation] |\n```\n\n## Asset Review Checklist\n\nBefore delivering any asset, verify:\n\n| Criterion | Check |\n| --- | --- |\n| **Audience alignment** | Does the language, depth, and emphasis match the intended reader? |\n| **Claim substantiation** | Is every claim backed by a sourced proof point or flagged? |\n| **Prospect specificity** | Could this asset only apply to this prospect, or is it generic? |\n| **Competitive awareness** | Does it address known alternatives without naming competitors negatively? |\n| **CTA appropriateness** | Is the call-to-action matched to the deal stage? |\n| **Length appropriateness** | One-pager: 1 page. Exec summary: 1-2 pages. Case study: 1-2 pages. |\n| **Brand consistency** | Does it match the customer's brand voice guidelines (if provided)? |\n| **Formatting** | Professional, clean, no markdown artifacts in customer-facing copy |\n| **Legal\u002Fcompliance** | No unapproved claims, accurate case study data, no NDA violations |\n\n## Guardrails\n\n1. Never fabricate case studies or customer quotes. All customer names, results, and testimonials must come from the user or companyRAG collections. Use \"[Insert customer reference for this industry]\" when none are provided.\n2. Never generate product capabilities not provided by the user. If product details are not in companyRAG collections or user input, flag as \"[Verify with product team]\" rather than assuming features.\n3. Never invent metrics or ROI figures. Business-impact projections must be based on provided case data or flagged as \"[Placeholder — needs validation with customer success team]\".\n4. Source labeling. Tag content origin — [From companyRAG collection], [From user input], [From CRM], [From deal context], [AI draft — verify].\n\n> **Tip:** Ask for PPTX output via companyFILES to get a formatted slide deck, or DOCX for a one-pager ready for distribution. PDF and Markdown are also available for longer collateral.\n","# Sales Asset Skill\n\nProduce deal-specific sales collateral — one-pagers, case study drafts, executive summaries, demo narratives, and proposal inserts — personalised to the buyer's industry, role, and stated priorities. All product information, case studies, pricing, and deal context comes from you, companyRAG collections, or a connected CRM.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CRM via MCP** (e.g. HubSpot, Salesforce) | Deal stage, deal value, stakeholders, competitive situation, closed-won notes |\n| **companyRAG collections** | Product specs, case studies, proof points, industry references |\n| **File upload** | Discovery notes, battlecards, account research, call summaries |\n\n> **No connected source?** Provide the data in chat or upload the relevant files — the skill works the same way.\n\n## Asset-Type Routing\n\nIdentify the right asset format based on the sales situation:\n\n| Situation | Recommended Asset | Purpose |\n| --- | --- | --- |\n| First meeting — leave-behind for champion | **One-Pager** | Concise overview the champion can forward internally |\n| Executive sponsor engagement | **Executive Summary** | Business-outcome focused, minimal technical detail |\n| Technical evaluation underway | **Solution Brief** | Architecture, integration, security, compliance focus |\n| Prospect asked \"who else uses this?\" | **Case Study Draft** | Social proof mapped to their industry\u002Fuse case |\n| Demo scheduled — need a narrative arc | **Demo Narrative** | Storyline tying demo flow to their specific pain |\n| Proposal or RFP response section | **Proposal Insert** | Tailored section addressing specific evaluation criteria |\n| Multi-stakeholder deal — different needs | **Messaging Matrix** | Stakeholder-specific value props in one reference doc |\n\nWhen the user's request does not clearly map to one type, ask clarifying questions about audience, timing, and intended use before drafting.\n\n## Asset Creation Workflow\n\n```\n1. IDENTIFY asset type and audience\n   |\n   +--> Route to asset type (table above)\n   +--> Identify primary audience: role, seniority, technical depth\n   +--> Identify secondary audience: who else will see this?\n   +--> Determine context: where in the deal cycle, what prompted the request\n   |\n2. GATHER deal context\n   |\n   +--> From CRM: deal stage, value, stakeholders, competitive situation\n   +--> From user: specific pain points, evaluation criteria, buyer language\n   +--> From companyRAG collections: product specs, case studies, proof points\n   +--> From prior skills: account research, call summaries, battlecard intel\n   |\n3. MAP messaging to persona\n   |\n   +--> Apply the Persona-Message Matrix (see below)\n   +--> Select value propositions ranked by relevance to this buyer\n   +--> Choose proof points that match their industry and company size\n   +--> Adapt language register to audience seniority and function\n   |\n4. GENERATE draft\n   |\n   +--> Apply the asset-specific template (see Asset Templates below)\n   +--> Ensure every claim is backed by a source or flagged as needing one\n   +--> Check against quality criteria before presenting\n   |\n5. REVIEW and refine\n   |\n   +--> Run the Asset Review Checklist (see below)\n   +--> Flag sections that need user input or approval\n   +--> Suggest alternative framings for key messages\n```\n\n## Persona-Message Matrix\n\nMatch messaging emphasis to the buyer's role and priorities:\n\n| Persona | Primary Concerns | Message Emphasis | Proof-Point Type |\n| --- | --- | --- | --- |\n| **C-Suite \u002F Executive** | Revenue impact, risk, strategic alignment | Business outcomes, ROI, competitive advantage | Revenue metrics, market position |\n| **VP \u002F Director** | Team productivity, budget justification | Operational efficiency, time-to-value, TCO | Productivity gains, cost savings |\n| **Manager \u002F Team Lead** | Day-to-day impact, adoption, workflow fit | Ease of use, integration, support quality | User satisfaction, adoption rates |\n| **Technical Evaluator** | Architecture, security, scalability | Technical specs, compliance, API coverage | Technical benchmarks, certifications |\n| **Procurement** | Cost, contract terms, vendor risk | Pricing transparency, vendor stability, SLAs | Financial health, customer count |\n| **End User \u002F Practitioner** | Daily workflow, learning curve, reliability | Usability, speed, reliability, support | User testimonials, ease-of-use metrics |\n\n### Language Register by Seniority\n\n| Audience Level | Register | Avoid |\n| --- | --- | --- |\n| **Executive** | Concise, outcome-first, strategic framing, minimal jargon | Feature lists, technical specifications, acronyms |\n| **Management** | Balanced — outcomes with supporting detail, metric-driven | Vague claims without numbers, excessive length |\n| **Practitioner** | Specific, practical, workflow-oriented, technically precise | High-level platitudes, marketing superlatives |\n\n## Asset Templates\n\n### One-Pager Template\n\n```\n# [Solution Name] for [Industry \u002F Use Case]\n\n## The Challenge\n[1-2 sentences describing the specific problem this prospect faces — use their language, not yours]\n\n## How [Solution] Helps\n[3-4 bullet points — each structured as: Outcome → How it works → Proof]\n- **[Outcome]**: [Brief mechanism] — [Proof point with metric]\n- **[Outcome]**: [Brief mechanism] — [Proof point with metric]\n- **[Outcome]**: [Brief mechanism] — [Proof point with metric]\n\n## Why [Company Name] Specifically\n[2-3 sentences connecting your differentiation to their stated evaluation criteria or competitive situation]\n\n## Customer Proof\n\"[Quote from a reference customer in their industry or similar use case]\"\n— [Name, Title, Company]   |   [Key metric achieved]\n\n## Next Step\n[Specific CTA relevant to where they are in the deal cycle]\n```\n\n### Executive Summary Template\n\n```\n# Executive Summary: [Solution] for [Prospect Company]\n\n**Prepared for**: [Name, Title]\n**Date**: [Date]\n\n## Strategic Context\n[2-3 sentences on the business challenge, framed in terms of their strategic priorities — reference annual report, earnings call, or stated goals if available]\n\n## Recommended Approach\n[Brief description of the proposed solution — outcomes first, then how — never feature-first]\n\n## Expected Business Impact\n| Outcome Area          | Current State        | Projected Improvement | Basis               |\n| --------------------- | -------------------- | --------------------- | ------------------- |\n| [Area]                | [Metric if known]    | [Projected change]    | [Source\u002Fcomparables]|\n\n## Risk Mitigation\n[Address the top 2-3 concerns this executive likely has — security, integration, change management, vendor stability]\n\n## Investment Overview\n[High-level framing — not detailed pricing. Position as investment with expected return, not a cost]\n\n## Recommended Next Step\n[Specific, executive-appropriate ask]\n```\n\n### Case Study Draft Template\n\n```\n# [Customer Name]: [Headline Result]\n\n## Company Profile\n- **Industry**: [Sector]  |  **Size**: [Employees \u002F Revenue]\n- **Use Case**: [What they were trying to accomplish]\n\n## The Challenge\n[3-4 sentences — the specific problem, its business impact, and why previous approaches fell short]\n\n## The Solution\n[How they implemented your solution — timeline, scope, approach. Focus on decisions, not features]\n\n## Results\n| Metric              | Before           | After            | Improvement         |\n| ------------------- | ---------------- | ---------------- | ------------------- |\n| [KPI]               | [Value]          | [Value]          | [% or absolute]     |\n\n## Key Quote\n\"[Customer quote that captures the transformation]\"\n— [Name, Title]\n\n## Relevance to [Prospect]\n[2-3 sentences explaining why this case study is specifically relevant to the prospect's situation]\n```\n\n### Demo Narrative Template\n\n```\n# Demo Narrative: [Prospect Company]\n\n**Audience**: [Names, roles]\n**Duration**: [Scheduled time]\n**Objective**: [What success looks like for this demo]\n\n## Opening Context (2 min)\n[Connect their stated challenge to what they are about to see. Reference a specific conversation or discovery finding.]\n\n## Scene 1: [Pain Point → Capability] (X min)\n- **Setup**: \"[Describe the scenario in their terms]\"\n- **Show**: [Specific feature\u002Fworkflow to demonstrate]\n- **Outcome**: \"[What this means for their team]\"\n- **Check-in question**: \"[Gauge reaction and relevance]\"\n\n## Scene 2: [Pain Point → Capability] (X min)\n[Same structure]\n\n## Scene 3: [Differentiator Moment] (X min)\n- **Setup**: \"[This is where we are different from alternatives]\"\n- **Show**: [Unique capability mapped to their evaluation criteria]\n- **Bridge**: \"[Tie back to their decision criteria]\"\n\n## Closing (3 min)\n- Recap: [3 key takeaways mapped to their priorities]\n- Ask: \"[Next-step proposal]\"\n- Leave-behind: [What you will send after — one-pager, trial, proposal]\n\n## Backup Scenes\n[2-3 additional features ready if specific questions arise or time allows — do not show unless prompted]\n```\n\n### Messaging Matrix Template\n\n```\n# Messaging Matrix: [Deal Name]\n\n| Stakeholder         | Title          | Primary Pain         | Value Prop                   | Proof Point               | Key Objection           | Talk Track                      |\n| ------------------- | -------------- | -------------------- | ---------------------------- | ------------------------- | ----------------------- | ------------------------------- |\n| [Name]              | [Role]         | [Their top concern]  | [Tailored value statement]   | [Relevant case\u002Fmetric]    | [Likely pushback]       | [How to frame the conversation] |\n```\n\n## Asset Review Checklist\n\nBefore delivering any asset, verify:\n\n| Criterion | Check |\n| --- | --- |\n| **Audience alignment** | Does the language, depth, and emphasis match the intended reader? |\n| **Claim substantiation** | Is every claim backed by a sourced proof point or flagged? |\n| **Prospect specificity** | Could this asset only apply to this prospect, or is it generic? |\n| **Competitive awareness** | Does it address known alternatives without naming competitors negatively? |\n| **CTA appropriateness** | Is the call-to-action matched to the deal stage? |\n| **Length appropriateness** | One-pager: 1 page. Exec summary: 1-2 pages. Case study: 1-2 pages. |\n| **Brand consistency** | Does it match the customer's brand voice guidelines (if provided)? |\n| **Formatting** | Professional, clean, no markdown artifacts in customer-facing copy |\n| **Legal\u002Fcompliance** | No unapproved claims, accurate case study data, no NDA violations |\n\n## Guardrails\n\n1. Never fabricate case studies or customer quotes. All customer names, results, and testimonials must come from the user or companyRAG collections. Use \"[Insert customer reference for this industry]\" when none are provided.\n2. Never generate product capabilities not provided by the user. If product details are not in companyRAG collections or user input, flag as \"[Verify with product team]\" rather than assuming features.\n3. Never invent metrics or ROI figures. Business-impact projections must be based on provided case data or flagged as \"[Placeholder — needs validation with customer success team]\".\n4. Source labeling. Tag content origin — [From companyRAG collection], [From user input], [From CRM], [From deal context], [AI draft — verify].\n\n> **Tip:** Ask for PPTX output via companyFILES to get a formatted slide deck, or DOCX for a one-pager ready for distribution. PDF and Markdown are also available for longer collateral.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fsales\u002Fsales-asset-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 sales-asset-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill sales-asset-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill sales-asset-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fsales\u002Fsales-asset-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},"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":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},"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":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",[],[]]