Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:29:50 +08:00
commit 4eff758bee
13 changed files with 416 additions and 0 deletions

View File

@@ -0,0 +1,30 @@
---
name: dashboard-playbook
description: Best-practice kit for BI dashboard layout, storytelling, and adoption.
---
# Dashboard Playbook Skill
## When to Use
- Designing new dashboards or refreshing existing ones for GTM stakeholders.
- Auditing dashboards that suffer from low engagement or unclear narratives.
- Training analysts on consistent storytelling and UX patterns.
## Framework
1. **Audience & Decisions** document persona, cadence, and key decisions.
2. **Story Arc** headline metric, supporting evidence, drill-downs, and action prompts.
3. **Layout System** hero tiles, contextual panels, alerts, and annotation space.
4. **Governance Hooks** data freshness indicator, owner info, and SLA links.
5. **Adoption Loop** training plans, feedback capture, and iteration cadence.
## Templates
- **Wireframe Template**: See `templates/dashboard_wireframe.md` for layout structure.
- **Dashboard brief** (goals, KPIs, filters, mockups).
- **Adoption checklist** (enablement, comms, success metrics).
## Tips
- Limit hero metrics to 35; move detailed tables into drill sections.
- Use consistent color semantics for good vs risk states.
- Pair with `build-exec-dashboard` to package specs + rollout plan.
---

View File

@@ -0,0 +1,30 @@
---
name: data-contract-framework
description: Operating model for defining, enforcing, and auditing BI data contracts.
---
# Data Contract Framework Skill
## When to Use
- Establishing ownership and SLAs for mission-critical BI tables.
- Coordinating schema changes between engineering, analytics, and RevOps.
- Auditing data reliability before major launches or executive reporting cycles.
## Framework
1. **Contract Scope** table/view name, business purpose, consumer list.
2. **Owner Matrix** technical owner, business owner, escalation contacts.
3. **SLA Definition** refresh cadence, acceptable latency, data quality thresholds.
4. **Change Workflow** approval steps, testing requirements, communication plan.
5. **Compliance & Audit** logging, version history, and retention requirements.
## Templates
- Data contract one-pager (scope, owners, SLAs, dependencies).
- Change request form with impact assessment.
- Audit checklist for quarterly reviews.
## Tips
- Keep contracts lightweight but enforceable—link to dbt/docs for deeper detail.
- Automate SLA checks via dashboards and alerting.
- Pair with `audit-data-contracts` to prioritize fixes and highlight risk.
---

View File

@@ -0,0 +1,30 @@
---
name: executive-kpi-briefings
description: Template pack for summarizing BI insights for ELT/board stakeholders.
---
# Executive KPI Briefings Skill
## When to Use
- Preparing weekly/monthly ELT updates with BI insights.
- Translating dashboards into succinct decision memos.
- Coordinating follow-up actions after KPI reviews.
## Framework
1. **Headline & Signal** lead with KPI delta, direction, and confidence.
2. **Driver Analysis** highlight top drivers, segments, or anomalies.
3. **Implications** spell out impact on goals, customers, or investments.
4. **Actions & Owners** list next steps, DRIs, due dates, and guardrails.
5. **Appendix** link to dashboard tabs, methodology, and deeper data.
## Templates
- 1-page KPI memo (headline, context, actions).
- Slide template for ELT/board readouts.
- Follow-up tracker with ownership + status fields.
## Tips
- Keep narratives under 200 words unless deeper context is requested.
- Pair with `build-exec-dashboard` and `plan-bi-roadmap` for consistent storytelling.
- Capture questions/decisions in a log to feed future prioritization.
---

View File

@@ -0,0 +1,31 @@
---
name: metric-governance-kit
description: Framework for defining, approving, and auditing GTM metrics and KPIs.
---
# Metric Governance Kit Skill
## When to Use
- Establishing source-of-truth KPIs for revenue, marketing, or CS teams.
- Resolving conflicting definitions or reporting anomalies.
- Preparing for exec/board reviews where metric accuracy is scrutinized.
## Framework
1. **Metric Charter** purpose, formula, filters, owner, review cadence.
2. **Data Lineage** upstream sources, transformations, semantic layer, downstream dashboards.
3. **Quality Controls** tests, alerts, thresholds, backup calculations.
4. **Change Management** approval workflow, communication plan, version history.
5. **Adoption Enablement** cheat sheets, FAQs, and example analyses.
## Templates
- **Metric Dictionary**: See `references/metric_dictionary_template.md` for standard definition format.
- **Metric charter one-pager**.
- **Lineage diagram checklist**.
- **Change log workbook** with approvals + timestamps.
## Tips
- Assign both business and technical owners for each KPI.
- Tag metrics with “tier” (executive, operational, exploratory) to prioritize rigor.
- Pair with `plan-bi-roadmap` to keep initiatives tied to governed metrics.
---