Skip to content
Skills Library
Data & analytics · Building & coding

data

/data

(forwward) Designs analytics systems, writes SQL queries, plans event tracking, and builds dashboards for product and user metrics. Triggers on SQL, analytics, dashboards, tracking, data pipelines, or user behavior analysis.

Licence
MIT
Last repository change
30.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

(forwward) Designs analytics systems, writes SQL queries, plans event tracking, and builds dashboards for product and user metrics. Triggers on SQL, analytics, dashboards, tracking, data pipelines, or user behavior analysis.

Original author description

(forwward) Designs analytics systems, writes SQL queries, plans event tracking, and builds dashboards for product and user metrics. Triggers on SQL, analytics, dashboards, tracking, data pipelines, or user behavior analysis.

How it works

  1. Metric Hierarchy
  2. SQL Patterns
  3. Event Tracking Design
  4. Dashboard Rules
  5. Data Pipeline Defaults
Original SKILL.md headings · 98 lines, 449 words
SKILL.md preview
---
name: data
description: (forwward) Designs analytics systems, writes SQL queries, plans event tracking, and builds dashboards for product and user metrics. Triggers on SQL, analytics, dashboards, tracking, data pipelines, or user behavior analysis.
---

# Data — Analytics & Intelligence

Measure what matters. Every metric should drive a decision. If it doesn't, stop tracking it.

## Metric Hierarchy

| Level | Metric | Cadence |
|-------|--------|---------|
| North Star | 1 metric that defines success (e.g., WAU, MRR) | Weekly |
| Health | 3-5 metrics that predict north star (retention, activation, NPS) | Weekly |
| Feature | Per-feature usage, conversion, time-to-value | Per release |
| Debug | Granular events for troubleshooting | On-demand |

**Rules:**
- North star is singular. Two north stars = zero north stars.
- Vanity metrics (page views, total signups) are not health metrics.
- Every feature ships with tracking. No "we'll add analytics later."

## SQL Patterns

### Cohort Retention
```sql
SELECT
  DATE_TRUNC('week', u.created_at) AS cohort_week,
  DATE_TRUNC('week', e.created_at) AS activity_week,
  COUNT(DISTINCT e.user_id) AS active_users
FROM users u
JOIN events e ON e.user_id = u.id
GROUP BY 1, 2
ORDER BY 1, 2;
```

### Funnel Analysis
```sql
WITH steps AS (
  SELECT user_id,
    MAX(CASE WHEN event = 'signup' THEN 1 END) AS step_1,
    MAX(CASE WHEN event = 'onboard_complete' THEN 1 END) AS step_2,
    MAX(CASE WHEN event = 'first_action' THEN 1 END) AS step_3,
    MAX(CASE WHEN event = 'paid' THEN 1 END) AS step_4
  FROM events
  WHERE created_at > NOW() - INTERVAL '30 days'
  GROUP BY user_id
)
SELECT
  COUNT(*) AS total,
  SUM(step_1) AS signup,
  SUM(step_2) AS onboarded,
  SUM(step_3) AS activated,
  SUM(step_4) AS converted
FROM steps;
```

### Rolling Averages
```sql
SELECT
  date,
  value,
  AVG(value) OVER (ORDER BY date ROWS BETWEEN 6 PRECEDING AND CURRENT ROW) AS rolling_7d
FROM daily_metrics;
```

## Event Tracking Design

Every event needs:

| Field | Example |
|-------|---------|
| `event_name` | `button_clicked`, `page_viewed`, `feature_used` |
| `user_id` | Authenticated user |
| `anonymous_id` | Pre-auth (cookie/device) |
| `timestamp` | ISO 8601, UTC always |
| `properties` | `{ page: "/pricing", plan: "pro" }` |

**Naming convention:** `noun_verb` — `form_submitted`, `file_uploaded`, `subscription_cancelled`

**Never:** `click`, `event1`, `trackThis`, `misc`

## Dashboard Rules

- **One question per dashboard.** "How is acquisition?" not "Everything."
- **Top-left = most important metric.** Eye lands there first.
- **Comparison always.** This week vs last week. This month vs last month.
- **No pie charts.** Use bar charts. Humans can't compare angles.
- **Annotate changes.** "Launched feature X" on the timeline.

## Data Pipeline Defaults

| Layer | Tool | Purpose |
|-------|------|---------|
| Collection | PostHog, Segment, or custom | Event ingestion |
| Storage | Postgres or BigQuery | Queryable warehouse |
| Transform | dbt or SQL views | Business logic layer |
| Visualization | Metabase, Grafana, or PostHog | Dashboards |

Keep it simple. You don't need Kafka until you have 10M events/day.

Versions

RepositoryScoreLicence
This page · iankiku/forwward-teams100MIT
stellar/stellar-dev-skill100Apache-2.0
pawangai/pawang-agents100MIT
asmn-96/ai-agents-skills-toolkit100MIT
Kiran-980/1ml95MIT
danielchukuma-dev/cougr95MIT
rainmanjam/poka-yoke90MIT

Database snapshot: 13.11.2026 · package version 4c5648395fb4 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100ph-analytics-setup
    Set up analytics tracking for your Product Hunt launch. Use this skill to configure tracking tools, create dashboards, and ensure you capture all important launch metrics.
  • 100lumen-recon
    Analytics reconnaissance — scan existing event tracking, metric definitions, dashboards, and analytics configuration to understand what is currently being measured. Use when asked to "what are we tracking", "audit our analytics", "what metrics exist", "analytics inventory", or…
  • 100sql-query-optimizer
    Optimize sql query optimizer operations. Auto-activating skill for Data Analytics. Triggers on: sql query optimizer, sql query optimizer Part of the Data Analytics skill category. Use when working with sql query optimizer functionality. Trigger with phrases like "sql query…
  • 100api-analytics-posthog-analytics
    PostHog event tracking, user identification, group analytics for B2B, GDPR consent patterns. Use when implementing product analytics, tracking user behavior, setting up funnels, or configuring privacy-compliant tracking.
  • 85data-analytics
    Data analysis, visualization, machine learning, business intelligence, and data engineering skills. SQL, dashboards, statistical analysis, predictive models, data pipelines. Triggers on: data analysis, dashboard, BI, SQL, machine learning, statistics, data pipeline, ETL, predictive analytics.
  • 100data-analyst
    Use when analysing data files (CSV, JSON, Excel), writing SQL queries, identifying trends and patterns, building dashboards or charts, summarising metrics, validating data quality, or turning raw data into actionable insights for decision-making.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.