Initial commit

skills/advocacy-roster-system/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: advocacy-roster-system
+description: Scoring and governance framework for managing reference customers and
+  advocacy cohorts.
+---
+
+# Advocacy Roster System Skill
+
+## When to Use
+- Building or refreshing reference customer pools and advisory boards.
+- Evaluating which customers are ready for public storytelling or beta participation.
+- Monitoring engagement health and risk signals for active advocates.
+
+## Framework
+1. **Scoring Model** – satisfaction, product breadth, results achieved, relationship strength, legal clearance.
+2. **Engagement Calendar** – cadence for check-ins, stories, events, and feedback loops.
+3. **Risk Monitoring** – signals for overuse, upcoming renewals, competitive threats.
+4. **Compliance Layer** – NDAs, consent tracking, brand guidelines, incentive policies.
+5. **Reporting** – dashboards for advocate pipeline, coverage by persona/industry, and influence on revenue.
+
+## Templates
+- Roster spreadsheet/Notion DB with scoring, health, assignments.
+- Advocate briefing doc with key facts, proof points, and guardrails.
+- Quarterly council recap + next-step template.
+
+## Tips
+- Limit outreach frequency and segment advocates to avoid fatigue.
+- Align with CS/AM owners before committing customers to references.
+- Pair with `activate-advocacy-program` command for turnkey campaign launch.
+
+---

skills/closed-loop-playbook/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: closed-loop-playbook
+description: Governance system for routing VoC insights to owners and tracking follow-through.
+---
+
+# Closed-Loop Playbook Skill
+
+## When to Use
+- After synthesizing VoC insights that require cross-functional action.
+- During QBRs or ELT reviews to show status of customer commitments.
+- Whenever audit trails are required for compliance or customer councils.
+
+## Framework
+1. **Intake** – capture insight ID, driver, severity, customer(s), and evidence link.
+2. **Routing** – assign accountable owner, supporting squad, and due date.
+3. **Action Plan** – define mitigation plan, success criteria, and measurement method.
+4. **Communication** – schedule updates to customers, exec sponsors, and internal stakeholders.
+5. **Retrospective** – log outcomes, lessons, and whether additional listening is needed.
+
+## Templates
+- Action register (spreadsheet/Notion/Jira) with status automation.
+- Customer commitment digest template for AM/CS teams.
+- SLA matrix by issue severity and customer tier.
+
+## Tips
+- Integrate with ticketing/project systems to avoid duplicate tracking.
+- Highlight blockers early; exec sponsors can unblock resources fast.
+- Close the loop with customers even when timelines slip—transparency builds trust.
+
+---

skills/customer-feedback-taxonomy/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: customer-feedback-taxonomy
+description: Standardized tagging schema for personas, lifecycle stages, drivers,
+  and sentiment.
+---
+
+# Customer Feedback Taxonomy Skill
+
+## When to Use
+- Normalizing surveys, interviews, support logs, or community chatter before synthesis.
+- Auditing existing VoC datasets for drift or inconsistencies.
+- Onboarding new teams to shared tagging standards.
+
+## Framework
+1. **Persona Layer** – map ICP, role, and influence level.
+2. **Lifecycle Layer** – awareness, onboarding, adoption, expansion, renewal, advocacy.
+3. **Driver Layer** – product, service, pricing, experience, relationship, outcomes.
+4. **Sentiment Layer** – strength, urgency, confidence, sample size.
+5. **Metadata Layer** – ARR, region, industry, channel, last touch.
+
+## Templates
+- CSV/Sheet taxonomy with dropdowns and validation rules.
+- JSON schema for tagging automation or webhook ingestion.
+- Governance checklist for quarterly taxonomy refresh.
+
+## Tips
+- Keep taxonomy lean (<30 drivers) to encourage adoption.
+- Version every change so historical analyses remain comparable.
+- Pair with `run-voc-listening-tour` to auto-tag new signals.
+
+---

skills/signal-correlation-workbench/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: signal-correlation-workbench
+description: Toolkit for linking VoC feedback with telemetry, revenue, and operational
+  data.
+---
+
+# Signal Correlation Workbench Skill
+
+## When to Use
+- Quantifying the impact of qualitative feedback on churn, expansion, and adoption.
+- Connecting support data, product usage, and survey responses into a unified narrative.
+- Testing hypotheses about leading indicators for customer health.
+
+## Framework
+1. **Data Inventory** – list all relevant sources (surveys, NPS, CSAT, telemetry, CRM, finance).
+2. **Join Strategy** – map IDs/keys, sampling windows, and normalization rules.
+3. **Correlation Analysis** – evaluate relationships (Pearson/Spearman), cohort comparisons, regression snippets.
+4. **Signal Strength Scoring** – combine volume, recency, severity, and revenue exposure.
+5. **Insight Packaging** – translate stats into plain language, visuals, and actionable levers.
+
+## Templates
+- SQL/notebook snippets for merging VoC tags with product/CRM tables.
+- Dashboard layout showing signal volume vs impact.
+- Experiment tracker linking hypotheses to validated outcomes.
+
+## Tips
+- Watch for survivor bias; include lost customers when possible.
+- Flag data quality caveats prominently to maintain trust.
+- Pair with `synthesize-voc-insights` to auto-embed correlations into narratives.
+
+---