Initial commit

skills/co-marketing-governance/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: co-marketing-governance
+description: Governance playbook for joint marketing programs, MDF, and performance
+  reviews.
+---
+
+# Co-Marketing Governance Skill
+
+## When to Use
+- Planning joint campaigns, launches, or events with partners.
+- Managing MDF budgets, approvals, and performance tracking.
+- Preparing partner QBRs or exec updates focused on demand-generation impact.
+
+## Framework
+1. **Program Intake** – business case, audience, KPIs, required assets, legal/compliance checks.
+2. **Approval Workflow** – decision matrix for marketing, partner, and finance stakeholders.
+3. **Execution Cadence** – sprint plan, shared tracking sheets, and content governance.
+4. **Measurement & Attribution** – agreed metrics (MQLs, pipeline, revenue, influence) + reporting cadence.
+5. **Closeout & Learnings** – retro template, MDF reconciliation, and next-play recommendations.
+
+## Templates
+- Co-marketing brief + approval form.
+- MDF budget tracker with forecast vs actuals.
+- Post-campaign report outline with KPIs and narrative prompts.
+
+## Tips
+- Align messaging with joint solution blueprints to keep storytelling consistent.
+- Attach MDF approval deadlines to campaign calendars to avoid delays.
+- Pair with `run-partner-qbr` to highlight impact and secure additional investment.
+
+---

skills/joint-solution-blueprint/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: joint-solution-blueprint
+description: Template for documenting co-built solutions, integrations, and GTM motions
+  with partners.
+---
+
+# Joint Solution Blueprint Skill
+
+## When to Use
+- Launching or refreshing a co-built integration or packaged service.
+- Equipping field teams with architecture, value props, and proof points.
+- Coordinating enablement across product, marketing, and partner teams.
+
+## Framework
+1. **Use Case Definition** – target persona, pain point, and success metrics.
+2. **Architecture Overview** – system diagram, data flows, dependencies, security notes.
+3. **Value Narrative** – customer outcomes, ROI proof, competitive differentiation.
+4. **Go-To-Market Plays** – positioning, pricing principles, launch checklist, asset library.
+5. **Support & Lifecycle** – roles, escalation paths, roadmap commitments.
+
+## Templates
+- One-page solution brief with messaging + CTA.
+- Architecture diagram checklist.
+- Launch plan with tasks, owners, and deadlines.
+
+## Tips
+- Keep diagrams simple enough for sales decks, with appendix for technical deep dives.
+- Include customer stories or beta insights to increase credibility.
+- Pair with `build-co-sell-playbook` so reps know how to pitch + progress deals.
+
+---

skills/partner-ecosystem-map/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: partner-ecosystem-map
+description: Visualization toolkit for mapping partner landscape, coverage, and priorities.
+---
+
+# Partner Ecosystem Map Skill
+
+## When to Use
+- Planning partner strategy, territorial coverage, or whitespace analysis.
+- Presenting ecosystem status to executives or cross-functional stakeholders.
+- Tracking progress against partner recruitment and ramp goals.
+
+## Framework
+1. **Segmentation Layer** – partner type, region, vertical, solution fit, maturity.
+2. **Value Layer** – pipeline contribution, ARR influenced, co-sell velocity, joint wins.
+3. **Health Layer** – certification status, enablement completion, NPS, engagement cadence.
+4. **Gaps & Targets** – highlight priority segments needing recruits or investment.
+5. **Narrative Hooks** – pair visuals with summary insights, risks, and next plays.
+
+## Templates
+- Ecosystem matrix with rows (partner type) × columns (value/health metrics).
+- Geo overlay map for territory coverage vs whitespace.
+- Executive summary slide linking visuals to investment requests.
+
+## Tips
+- Keep visuals updated monthly so leadership trusts the snapshot.
+- Link each gap to a specific recruiting or enablement initiative.
+- Pair with `design-partner-ecosystem` for streamlined planning packages.
+
+---

skills/partner-revenue-desk/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: partner-revenue-desk
+description: Operating model for tracking, attributing, and accelerating partner-sourced
+  revenue.
+---
+
+# Partner Revenue Desk Skill
+
+## When to Use
+- Forecasting partner-sourced/ influenced revenue for leadership updates.
+- Monitoring incentives, SPIFs, and MDF utilization tied to partner pipeline.
+- Coordinating RevOps, finance, and partner teams on attribution disputes.
+
+## Framework
+1. **Revenue Taxonomy** – sourced vs influenced vs co-sell, stage definitions, SLAs.
+2. **Process Flow** – intake → validation → attribution → approval → reporting.
+3. **Data Stack** – CRM objects, PRM integrations, BI dashboards, alerting.
+4. **Incentive Hooks** – payout rules, MDF governance, exception workflows.
+5. **Escalation Paths** – playbooks for disputes, double counting, or compliance risks.
+
+## Templates
+- Revenue desk runbook with RACI + cadence.
+- Attribution audit checklist.
+- MDF utilization tracker with projected ROI.
+
+## Tips
+- Align definitions with finance early; lock requirements before launching SPIFs.
+- Automate alerts for stalled partner deals to keep velocity high.
+- Pair with `build-co-sell-playbook` and `run-partner-qbr` for closed-loop reporting.
+
+---