Initial commit

This commit is contained in:
Zhongwei Li
2025-11-29 18:29:43 +08:00
commit d16ebac7ef
12 changed files with 424 additions and 0 deletions

View File

@@ -0,0 +1,30 @@
---
name: instrumentation
description: Use when defining events, fields, and governance for GTM analytics pipelines.
---
# Analytics Instrumentation Standards Skill
## When to Use
- Planning event tracking for product, marketing, or revenue analytics.
- Auditing existing tracking plans before model refreshes.
- Coordinating engineering, product, and RevOps on data contracts.
## Framework
1. **Event Naming & Structure** action-oriented names, consistent casing, required properties.
2. **Identity Management** user/account IDs, anonymous IDs, device IDs, cross-system mapping.
3. **Consent & Privacy** capture consent status, honor suppression, regional storage rules.
4. **Versioning** change logs, backward compatibility, deprecation timelines.
5. **Observability** sampling dashboards, schema change alerts, volume anomaly detection.
## Templates
- Tracking plan sheet (event, description, properties, source, owner, status).
- Data contract checklist (fields, types, validation rules, SLA).
- Observability runbook (metrics, thresholds, notification channels).
## Tips
- Pair each event with QA instructions and sample payloads.
- Store tracking plans in version control to align with code releases.
- Review instrumentation quarterly with stakeholders.
---

View File

@@ -0,0 +1,33 @@
---
name: quality-gates
description: Use when establishing tests, monitoring, and incident response for analytics
models.
---
# Analytics Quality Gates Skill
## When to Use
- Designing validation steps for new models or dashboards.
- Setting up automated data quality monitoring.
- Running incident reviews after data breaks.
## Framework
1. **Test Coverage** schema, freshness, unique, referential, accepted values, volume thresholds.
2. **Alerting** severity tiers, alert channels, on-call rotation, escalation policies.
3. **Incident Response** triage checklist, communication templates, resolution targets.
4. **Change Management** approval workflow, rollback plan, audit logging.
5. **Postmortems** root cause analysis, remediation tasks, knowledge base updates.
## Templates
## Templates
- **QA Checklist**: See `assets/qa_checklist.md` for validation steps.
- **Quality matrix** (model/table → tests → owner → SLA).
- **Incident playbook** (trigger, response steps, communication log).
- **Change request form** with risk assessment.
## Tips
- Tie quality gates to CI/CD or dbt Cloud jobs to block bad deploys.
- Keep alert fatigue low by tuning thresholds.
- Document every incident for future prevention.
---

View File

@@ -0,0 +1,30 @@
---
name: visualization-patterns
description: Use when designing dashboards, reports, and narratives for GTM stakeholders.
---
# Analytics Visualization Patterns Skill
## When to Use
- Planning a new dashboard or updating existing visualizations.
- Coaching teams on self-serve analytics adoption.
- Auditing visual design, accessibility, and narrative clarity.
## Framework
1. **Audience & Story** clarify persona, decision cadence, and key questions.
2. **Layout & Hierarchy** organize tiles by funnel (overview → drill-down → diagnostic), highlight KPIs.
3. **Chart Selection** match metric type to chart (trend, composition, comparison, distribution).
4. **Accessibility** color contrast, labels, tooltips, mobile/responsive considerations.
5. **Narrative & Actions** annotate insights, embed CTA buttons or playbook links.
## Templates
- Dashboard wireframe grid with KPI slots.
- Metric dictionary (definition, source, owner, refresh schedule).
- Adoption checklist (stakeholder review, enablement session, feedback form).
## Tips
- Keep hero KPIs at top-left with trend vs target.
- Use consistent color palettes for good/bad variance.
- Embed documentation or Loom walkthroughs directly in BI tool when possible.
---