Initial commit
This commit is contained in:
31
skills/cohort-analysis/SKILL.md
Normal file
31
skills/cohort-analysis/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: cohort-analysis
|
||||
description: Standard method for slicing bookings, pipeline, and retention cohorts
|
||||
for diagnostics.
|
||||
---
|
||||
|
||||
# Cohort Analysis Framework Skill
|
||||
|
||||
## When to Use
|
||||
- Comparing performance across acquisition channels, segments, or product lines.
|
||||
- Diagnosing conversion drop-offs within specific booking/vintage cohorts.
|
||||
- Stress-testing forecast assumptions with historical baseline behavior.
|
||||
|
||||
## Framework
|
||||
1. **Cohort Definition** – choose cohort key (signup month, lead source, product tier, segment).
|
||||
2. **Metric Stack** – select KPIs (coverage, win rate, ACV, NRR, payback) per cohort.
|
||||
3. **Normalization** – adjust for seasonality, deal size mix, or currency.
|
||||
4. **Visualization** – waterfall tables, heatmaps, or overlapping curves to highlight divergence.
|
||||
5. **Narrative Layer** – annotate drivers, anomalies, and recommended actions.
|
||||
|
||||
## Templates
|
||||
- Cohort definition worksheet (keys, filters, inclusion/exclusion rules).
|
||||
- Standardized chart pack for leadership readouts.
|
||||
- Diagnostic checklist for follow-up analyses.
|
||||
|
||||
## Tips
|
||||
- Keep cohorts mutually exclusive to avoid double-counting.
|
||||
- Pair with `inspect-pipeline-levers` to link cohort insights to pipeline stages.
|
||||
- Rebaseline quarterly so assumptions stay current.
|
||||
|
||||
---
|
||||
31
skills/deal-quality-model/SKILL.md
Normal file
31
skills/deal-quality-model/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: deal-quality-model
|
||||
description: Scoring system for opportunity hygiene, win likelihood, and inspection
|
||||
prioritization.
|
||||
---
|
||||
|
||||
# Deal Quality Model Skill
|
||||
|
||||
## When to Use
|
||||
- Prioritizing inspection focus during forecast and pipeline reviews.
|
||||
- Flagging opportunities with incomplete data or low win signals.
|
||||
- Creating alerts when critical hygiene steps (MEDDIC, next steps) are missing.
|
||||
|
||||
## Framework
|
||||
1. **Input Signals** – discovery notes, exec sponsor, mutual plan, activity recency, budget proof.
|
||||
2. **Weighting** – assign weights per signal (required, strong, nice-to-have) per segment.
|
||||
3. **Score Bands** – define thresholds for healthy, watch, and critical opportunities.
|
||||
4. **Automation Hooks** – integrate with CRM validation rules, Slack alerts, and dashboards.
|
||||
5. **Governance** – review scoring monthly, capture overrides, and document rationale.
|
||||
|
||||
## Templates
|
||||
- Signal scoring matrix with thresholds + automation IDs.
|
||||
- Inspection checklist for reps/managers.
|
||||
- Alert message template for Slack/email.
|
||||
|
||||
## Tips
|
||||
- Align scoring with enablement frameworks (MEDDIC, SPICED) to drive adoption.
|
||||
- Expose scores in forecasts so execs can challenge risky commits.
|
||||
- Pair with `guardrail-scorecard` or pipeline commands to operationalize.
|
||||
|
||||
---
|
||||
30
skills/exec-briefing-kit/SKILL.md
Normal file
30
skills/exec-briefing-kit/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: exec-briefing-kit
|
||||
description: Template for packaging revenue analytics into concise exec/board narratives.
|
||||
---
|
||||
|
||||
# Executive Briefing Kit Skill
|
||||
|
||||
## When to Use
|
||||
- Preparing weekly/monthly revenue readouts for ELT/board.
|
||||
- Translating dense analytics into concise decisions, asks, and risks.
|
||||
- Coordinating cross-functional follow-ups post-briefing.
|
||||
|
||||
## Framework
|
||||
1. **Story Spine** – headline, context, signal, implication, action.
|
||||
2. **Metric Snapshot** – top KPIs with delta vs target, YoY, and confidence band.
|
||||
3. **Focus Risks/Opps** – highlight 3 blockers/opportunities with owners.
|
||||
4. **Decision Log** – capture exec decisions, escalations, and follow-ups.
|
||||
5. **Comms Pack** – create slides/memo + Slack/email summary for broader teams.
|
||||
|
||||
## Templates
|
||||
- 3-slide deck outline (headline, KPI spine, action plan).
|
||||
- Memo template with summary → insights → actions.
|
||||
- Decision/action log sheet with owner, due date, status.
|
||||
|
||||
## Tips
|
||||
- Lead with actions/asks; park methodology in appendix.
|
||||
- Include guardrail status inline so execs can quickly assess risk.
|
||||
- Pair with `revenue-health-dashboard` for visuals and command outputs for deep dives.
|
||||
|
||||
---
|
||||
30
skills/revenue-health-dashboard/SKILL.md
Normal file
30
skills/revenue-health-dashboard/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: revenue-health-dashboard
|
||||
description: Visualization blueprint for revenue KPIs, guardrails, and action callouts.
|
||||
---
|
||||
|
||||
# Revenue Health Dashboard Skill
|
||||
|
||||
## When to Use
|
||||
- Summarizing bookings, pipeline, retention, and efficiency metrics in one place.
|
||||
- Creating weekly/monthly revenue review packs with consistent layout.
|
||||
- Highlighting guardrail breaches and ownership for remediation.
|
||||
|
||||
## Framework
|
||||
1. **KPI Stack** – bookings, pipeline coverage, win rate, retention/NRR, CAC/payback.
|
||||
2. **Segmentation Layer** – tabs for region, segment, product, channel.
|
||||
3. **Guardrail Banner** – visual cues for breached vs healthy thresholds.
|
||||
4. **Insight Tiles** – annotate root cause, owner, and next action per issue.
|
||||
5. **Drill Links** – tie charts to deeper dashboards or command outputs.
|
||||
|
||||
## Templates
|
||||
- Executive summary slide with KPI dials + traffic lights.
|
||||
- Detail view for pipeline vs target, retention cohorts, and efficiency metrics.
|
||||
- Action tracker table embedded in the dashboard.
|
||||
|
||||
## Tips
|
||||
- Keep traffic-light rules aligned with `guardrail-scorecard` to avoid confusion.
|
||||
- Embed command links (monitor, inspect, build) so reviewers can dive deeper.
|
||||
- Snapshot dashboards before/after remediation to track improvement.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user