[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AEST9A1F043HBERJPX4GZ2":3,"skill-same:01M7AEST9A1F043HBERJPX4GZ2":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},"01M7AEST9A1F043HBERJPX4GZ2","onboarding-plan-skill",null,"Build a structured customer onboarding plan with milestones, owner assignments, and 30\u002F60\u002F90-day success checkpoints. Use when kicking off a new customer, redesigning an onboarding process, or scaling CSM capacity. Trigger with \"create onboarding plan for\", \"new customer setup\", \"30\u002F60\u002F90 plan for [customer]\".","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\u002Fcustomer-success\u002Fonboarding-plan-skill\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: onboarding-plan-skill\ndescription: Build a structured customer onboarding plan with milestones, owner assignments, and 30\u002F60\u002F90-day success checkpoints. Use when kicking off a new customer, redesigning an onboarding process, or scaling CSM capacity. Trigger with \"create onboarding plan for\", \"new customer setup\", \"30\u002F60\u002F90 plan for [customer]\".\n---\n\n# Onboarding Plan Skill\n\nBuild milestone-driven onboarding plans that move a new customer from signed contract to first realised value. Customer-specific data comes from you, a connected MCP source, or companyRAG collections.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CRM via MCP** (e.g. HubSpot, Salesforce) | Account details, contract scope, ARR, key contacts, closed-won notes |\n| **Project tracker via MCP** (e.g. Asana, Monday, Jira, Notion) | Task tracking, milestone status, owner assignments |\n| **companyRAG \u002F file upload** | Sales-handoff notes, discovery-call summaries, technical assessments |\n\n> **No connected source?** Provide the inputs in chat or upload the relevant files — the plan works as a standalone document.\n\n## Onboarding Planning Workflow\n\nRun these steps in order for every new onboarding plan.\n\n### Step 1: Gather Requirements\n\nBefore building the plan, collect these inputs. Flag any gaps — incomplete requirements cause rework later.\n\n| Input | Source | Why It Matters |\n| --- | --- | --- |\n| **Contract scope** | CRM \u002F sales handoff | Defines what the customer purchased and what must be delivered |\n| **Customer business goals** | Sales notes, discovery calls | Anchors milestones to outcomes the customer actually cares about |\n| **Technical environment** | Pre-sales technical assessment | Determines integration complexity and technical milestones |\n| **Customer team** | Sales handoff, CRM contacts | Identifies stakeholders, decision-makers, and day-to-day contacts |\n| **Timeline constraints** | Contract, customer request | Hard deadlines (e.g. go-live before fiscal year end) shape the plan |\n| **Known risks** | Sales handoff notes | Concerns flagged during the sales process (e.g. limited IT resources) |\n| **Success criteria** | Customer-stated or jointly defined | What \"done\" looks like from the customer's perspective |\n\n### Step 2: Define Onboarding Phases\n\nStructure the plan into three phases with clear entry and exit criteria.\n\n**Phase 1 — Foundation (Days 1–30)**\n\n| Element | Detail |\n| --- | --- |\n| **Goal** | Technical setup complete, key stakeholders onboarded, first value demonstrated |\n| **Entry criteria** | Contract signed, sales-to-CS handoff completed |\n| **Key milestones** | Kickoff call, technical setup, admin training, initial configuration, first use case live |\n| **Exit criteria** | Core platform configured, admin users trained, at least one use case operational |\n\n**Phase 2 — Adoption (Days 31–60)**\n\n| Element | Detail |\n| --- | --- |\n| **Goal** | Broader team adoption, workflows established, early ROI evidence |\n| **Entry criteria** | Phase 1 exit criteria met |\n| **Key milestones** | End-user training, workflow configuration, adoption check-in, usage review |\n| **Exit criteria** | Target activation rate achieved, core workflows running, initial success metrics captured |\n\n**Phase 3 — Optimisation (Days 61–90)**\n\n| Element | Detail |\n| --- | --- |\n| **Goal** | Full deployment, value confirmed, transition to steady-state relationship |\n| **Entry criteria** | Phase 2 exit criteria met |\n| **Key milestones** | Advanced feature enablement, success-metric review, executive sponsor check-in, formal handoff to ongoing CS |\n| **Exit criteria** | Success criteria from Step 1 achieved, ongoing cadence established, success plan drafted |\n\n### Step 3: Assign Ownership\n\nEvery milestone needs a clear owner on both sides — your team and the customer's.\n\n| Role | Responsibilities | Typical Owner |\n| --- | --- | --- |\n| **CSM** | Overall plan ownership, relationship management, milestone tracking, escalation | Your team |\n| **Implementation \u002F Solutions** | Technical setup, configuration, integrations, data migration | Your team |\n| **Trainer** | Admin and end-user training delivery | Your team |\n| **Customer Project Lead** | Internal coordination, resource availability, decision-making | Customer team |\n| **Customer IT \u002F Admin** | Technical access, environment setup, security review | Customer team |\n| **Executive Sponsor** (both sides) | Strategic alignment, unblocking escalations, success validation | Both teams |\n\nFor smaller accounts, one person may fill several roles. For enterprise accounts, expand roles as needed (e.g. a dedicated data-migration lead or change-management lead).\n\n### Step 4: Set Success Checkpoints\n\nSchedule formal checkpoints at each phase boundary and at the 90-day mark.\n\n| Checkpoint | Timing | Attendees | Agenda |\n| --- | --- | --- | --- |\n| **Kickoff** | Day 1–5 | All stakeholders | Introductions, plan review, goal confirmation, timeline alignment |\n| **30-day review** | Day 28–32 | CSM, customer project lead, sponsors (optional) | Phase 1 milestone review, issue resolution, Phase 2 readiness |\n| **60-day review** | Day 58–62 | CSM, customer project lead | Adoption metrics review, workflow effectiveness, Phase 3 planning |\n| **90-day review** | Day 88–92 | CSM, customer project lead, executive sponsors | Success-criteria assessment, value summary, transition to ongoing cadence |\n\nEach checkpoint produces a documented outcome: milestones achieved, milestones delayed (with new dates), open issues, and agreed next steps.\n\n### Step 5: Create a Communication Cadence\n\nDefine how and when you communicate throughout onboarding.\n\n| Communication | Frequency | Channel | Owner |\n| --- | --- | --- | --- |\n| **Status update** | Weekly | Email or shared document | CSM |\n| **Working sessions** | As needed per milestones | Video call | Implementation lead |\n| **Escalation** | As needed | Direct message + email | CSM or customer project lead |\n| **Checkpoint review** | At phase boundaries | Video call with agenda | CSM |\n\nAdapt the cadence to the customer — some prefer async updates, others want weekly syncs. Ask at kickoff.\n\n## Output Template — Onboarding Plan\n\n```\nCUSTOMER ONBOARDING PLAN\nAccount: [name]\nCSM: [name]\nStart date: [date]\nTarget completion: [date — typically 90 days from start]\nContract scope: [brief summary of what was purchased]\nSuccess criteria: [customer-stated definition of success]\n\nPHASE 1 — FOUNDATION (Days 1–30)\nGoal: [specific to this customer]\n  Milestone 1: [description]\n    Owner: [name\u002Frole] | Due: [date] | Status: [Not started \u002F In progress \u002F Complete]\n  Milestone 2: [description]\n    Owner: [name\u002Frole] | Due: [date] | Status: [...]\n  ...\n  Exit criteria: [what must be true to move to Phase 2]\n  30-day checkpoint: [date]\n\nPHASE 2 — ADOPTION (Days 31–60)\nGoal: [specific to this customer]\n  Milestone 1: [description]\n    Owner: [name\u002Frole] | Due: [date] | Status: [...]\n  ...\n  Exit criteria: [what must be true to move to Phase 3]\n  60-day checkpoint: [date]\n\nPHASE 3 — OPTIMISATION (Days 61–90)\nGoal: [specific to this customer]\n  Milestone 1: [description]\n    Owner: [name\u002Frole] | Due: [date] | Status: [...]\n  ...\n  Exit criteria: [what must be true to consider onboarding complete]\n  90-day checkpoint: [date]\n\nRISKS & MITIGATIONS:\n  1. [risk] → [mitigation plan] → Owner: [name]\n  2. ...\n\nCOMMUNICATION CADENCE:\n  [as defined in Step 5]\n\nSTAKEHOLDER MAP:\n  Your team:     [name — role, name — role, ...]\n  Customer team: [name — role, name — role, ...]\n```\n\n## Adapt to Your Business\n\nThe 30\u002F60\u002F90 framework is a default. Adjust it for your product and customer profile:\n\n- **Simple product, SMB customer:** compress to 14\u002F30\u002F45 days, fewer milestones, lighter checkpoints.\n- **Complex platform, enterprise customer:** extend to 30\u002F60\u002F90\u002F120 days; add a Phase 0 (pre-kickoff prep) and a Phase 4 (advanced enablement).\n- **Usage-based product:** replace time-based phase gates with usage-based triggers (e.g. Phase 2 starts at X active users, not at day 31).\n- **Multi-product deployment:** create parallel tracks per product with a shared timeline and consolidated checkpoints.\n- **High-touch vs. tech-touch:** for pooled onboarding, replace individual milestones with automated triggers (welcome sequence, in-app guides, self-serve training) and scheduled group check-ins.\n\n## Guardrails\n\n- Never fabricate customer requirements, technical environments, or business goals. All customer-specific details must come from the user or connected data. When data is missing, generate clearly marked placeholder fields.\n- Never assume the customer's team structure or resource availability. Ask; do not infer.\n- Never generate specific adoption metrics or usage targets without customer data.\n- Source-label every element: `[From account data]`, `[From onboarding framework]`, or `[CSM input needed]`.\n\n> **Tip:** Ask for DOCX or XLSX output via companyFILES to get a formatted plan ready to share.\n","# Onboarding Plan Skill\n\nBuild milestone-driven onboarding plans that move a new customer from signed contract to first realised value. Customer-specific data comes from you, a connected MCP source, or companyRAG collections.\n\n## Where the Data Comes From\n\n| Source | What It Adds |\n| --- | --- |\n| **CRM via MCP** (e.g. HubSpot, Salesforce) | Account details, contract scope, ARR, key contacts, closed-won notes |\n| **Project tracker via MCP** (e.g. Asana, Monday, Jira, Notion) | Task tracking, milestone status, owner assignments |\n| **companyRAG \u002F file upload** | Sales-handoff notes, discovery-call summaries, technical assessments |\n\n> **No connected source?** Provide the inputs in chat or upload the relevant files — the plan works as a standalone document.\n\n## Onboarding Planning Workflow\n\nRun these steps in order for every new onboarding plan.\n\n### Step 1: Gather Requirements\n\nBefore building the plan, collect these inputs. Flag any gaps — incomplete requirements cause rework later.\n\n| Input | Source | Why It Matters |\n| --- | --- | --- |\n| **Contract scope** | CRM \u002F sales handoff | Defines what the customer purchased and what must be delivered |\n| **Customer business goals** | Sales notes, discovery calls | Anchors milestones to outcomes the customer actually cares about |\n| **Technical environment** | Pre-sales technical assessment | Determines integration complexity and technical milestones |\n| **Customer team** | Sales handoff, CRM contacts | Identifies stakeholders, decision-makers, and day-to-day contacts |\n| **Timeline constraints** | Contract, customer request | Hard deadlines (e.g. go-live before fiscal year end) shape the plan |\n| **Known risks** | Sales handoff notes | Concerns flagged during the sales process (e.g. limited IT resources) |\n| **Success criteria** | Customer-stated or jointly defined | What \"done\" looks like from the customer's perspective |\n\n### Step 2: Define Onboarding Phases\n\nStructure the plan into three phases with clear entry and exit criteria.\n\n**Phase 1 — Foundation (Days 1–30)**\n\n| Element | Detail |\n| --- | --- |\n| **Goal** | Technical setup complete, key stakeholders onboarded, first value demonstrated |\n| **Entry criteria** | Contract signed, sales-to-CS handoff completed |\n| **Key milestones** | Kickoff call, technical setup, admin training, initial configuration, first use case live |\n| **Exit criteria** | Core platform configured, admin users trained, at least one use case operational |\n\n**Phase 2 — Adoption (Days 31–60)**\n\n| Element | Detail |\n| --- | --- |\n| **Goal** | Broader team adoption, workflows established, early ROI evidence |\n| **Entry criteria** | Phase 1 exit criteria met |\n| **Key milestones** | End-user training, workflow configuration, adoption check-in, usage review |\n| **Exit criteria** | Target activation rate achieved, core workflows running, initial success metrics captured |\n\n**Phase 3 — Optimisation (Days 61–90)**\n\n| Element | Detail |\n| --- | --- |\n| **Goal** | Full deployment, value confirmed, transition to steady-state relationship |\n| **Entry criteria** | Phase 2 exit criteria met |\n| **Key milestones** | Advanced feature enablement, success-metric review, executive sponsor check-in, formal handoff to ongoing CS |\n| **Exit criteria** | Success criteria from Step 1 achieved, ongoing cadence established, success plan drafted |\n\n### Step 3: Assign Ownership\n\nEvery milestone needs a clear owner on both sides — your team and the customer's.\n\n| Role | Responsibilities | Typical Owner |\n| --- | --- | --- |\n| **CSM** | Overall plan ownership, relationship management, milestone tracking, escalation | Your team |\n| **Implementation \u002F Solutions** | Technical setup, configuration, integrations, data migration | Your team |\n| **Trainer** | Admin and end-user training delivery | Your team |\n| **Customer Project Lead** | Internal coordination, resource availability, decision-making | Customer team |\n| **Customer IT \u002F Admin** | Technical access, environment setup, security review | Customer team |\n| **Executive Sponsor** (both sides) | Strategic alignment, unblocking escalations, success validation | Both teams |\n\nFor smaller accounts, one person may fill several roles. For enterprise accounts, expand roles as needed (e.g. a dedicated data-migration lead or change-management lead).\n\n### Step 4: Set Success Checkpoints\n\nSchedule formal checkpoints at each phase boundary and at the 90-day mark.\n\n| Checkpoint | Timing | Attendees | Agenda |\n| --- | --- | --- | --- |\n| **Kickoff** | Day 1–5 | All stakeholders | Introductions, plan review, goal confirmation, timeline alignment |\n| **30-day review** | Day 28–32 | CSM, customer project lead, sponsors (optional) | Phase 1 milestone review, issue resolution, Phase 2 readiness |\n| **60-day review** | Day 58–62 | CSM, customer project lead | Adoption metrics review, workflow effectiveness, Phase 3 planning |\n| **90-day review** | Day 88–92 | CSM, customer project lead, executive sponsors | Success-criteria assessment, value summary, transition to ongoing cadence |\n\nEach checkpoint produces a documented outcome: milestones achieved, milestones delayed (with new dates), open issues, and agreed next steps.\n\n### Step 5: Create a Communication Cadence\n\nDefine how and when you communicate throughout onboarding.\n\n| Communication | Frequency | Channel | Owner |\n| --- | --- | --- | --- |\n| **Status update** | Weekly | Email or shared document | CSM |\n| **Working sessions** | As needed per milestones | Video call | Implementation lead |\n| **Escalation** | As needed | Direct message + email | CSM or customer project lead |\n| **Checkpoint review** | At phase boundaries | Video call with agenda | CSM |\n\nAdapt the cadence to the customer — some prefer async updates, others want weekly syncs. Ask at kickoff.\n\n## Output Template — Onboarding Plan\n\n```\nCUSTOMER ONBOARDING PLAN\nAccount: [name]\nCSM: [name]\nStart date: [date]\nTarget completion: [date — typically 90 days from start]\nContract scope: [brief summary of what was purchased]\nSuccess criteria: [customer-stated definition of success]\n\nPHASE 1 — FOUNDATION (Days 1–30)\nGoal: [specific to this customer]\n  Milestone 1: [description]\n    Owner: [name\u002Frole] | Due: [date] | Status: [Not started \u002F In progress \u002F Complete]\n  Milestone 2: [description]\n    Owner: [name\u002Frole] | Due: [date] | Status: [...]\n  ...\n  Exit criteria: [what must be true to move to Phase 2]\n  30-day checkpoint: [date]\n\nPHASE 2 — ADOPTION (Days 31–60)\nGoal: [specific to this customer]\n  Milestone 1: [description]\n    Owner: [name\u002Frole] | Due: [date] | Status: [...]\n  ...\n  Exit criteria: [what must be true to move to Phase 3]\n  60-day checkpoint: [date]\n\nPHASE 3 — OPTIMISATION (Days 61–90)\nGoal: [specific to this customer]\n  Milestone 1: [description]\n    Owner: [name\u002Frole] | Due: [date] | Status: [...]\n  ...\n  Exit criteria: [what must be true to consider onboarding complete]\n  90-day checkpoint: [date]\n\nRISKS & MITIGATIONS:\n  1. [risk] → [mitigation plan] → Owner: [name]\n  2. ...\n\nCOMMUNICATION CADENCE:\n  [as defined in Step 5]\n\nSTAKEHOLDER MAP:\n  Your team:     [name — role, name — role, ...]\n  Customer team: [name — role, name — role, ...]\n```\n\n## Adapt to Your Business\n\nThe 30\u002F60\u002F90 framework is a default. Adjust it for your product and customer profile:\n\n- **Simple product, SMB customer:** compress to 14\u002F30\u002F45 days, fewer milestones, lighter checkpoints.\n- **Complex platform, enterprise customer:** extend to 30\u002F60\u002F90\u002F120 days; add a Phase 0 (pre-kickoff prep) and a Phase 4 (advanced enablement).\n- **Usage-based product:** replace time-based phase gates with usage-based triggers (e.g. Phase 2 starts at X active users, not at day 31).\n- **Multi-product deployment:** create parallel tracks per product with a shared timeline and consolidated checkpoints.\n- **High-touch vs. tech-touch:** for pooled onboarding, replace individual milestones with automated triggers (welcome sequence, in-app guides, self-serve training) and scheduled group check-ins.\n\n## Guardrails\n\n- Never fabricate customer requirements, technical environments, or business goals. All customer-specific details must come from the user or connected data. When data is missing, generate clearly marked placeholder fields.\n- Never assume the customer's team structure or resource availability. Ask; do not infer.\n- Never generate specific adoption metrics or usage targets without customer data.\n- Source-label every element: `[From account data]`, `[From onboarding framework]`, or `[CSM input needed]`.\n\n> **Tip:** Ask for DOCX or XLSX output via companyFILES to get a formatted plan ready to share.\n",{"name":5,"description":7},"main","39e0752000720de2d20917bd46c1c5149c4a0221","en\u002Fskills\u002Fcustomer-success\u002Fonboarding-plan-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 onboarding-plan-skill",{"tool":38,"command":39},"bunx","bunx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill onboarding-plan-skill",{"tool":41,"command":42},"pnpm","pnpm dlx skills add innFactory-AI\u002Fcompany-ai-stack-skills --skill onboarding-plan-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FinnFactory-AI\u002Fcompany-ai-stack-skills\u002Fblob\u002Fmain\u002Fen\u002Fskills\u002Fcustomer-success\u002Fonboarding-plan-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",[],[]]