Analyzer

by cline26378461e978No license34 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 months ago

Analyze queried data for trends, week-over-week comparisons, distributions, funnels, cohorts, top-N lists, anomalies, sanity checks, and report-ready findings. Use after or alongside ClickHouse queries when the user wants insight rather than raw rows.

Instructions onlyData & Analytics
AI-generated overview

Turns queried data into defensible findings using trends, comparisons, distributions, funnels, cohorts and sanity checks.

What it does
The skill provides analysis patterns for interpreting queried data, including trend, comparison, distribution, funnel, cohort, top-N and sanity-check approaches. It lists pre-conclusion checks such as verifying time window and grain, sample size, nulls, freshness and avoiding causal language. It also defines a finding format with Finding, Evidence, Confidence, Caveats and Recommended next check fields.
When to use it
Use after or alongside ClickHouse queries when the user wants insight rather than raw rows. It suits situations where queried data must be turned into report-ready findings with stated confidence and caveats.
Requirements
No scripts; instructions only. It is intended for use after or alongside ClickHouse queries, so access to query results is implied.

Analyzer

Turn data into defensible findings instead of only returning rows.

Analysis patterns

Choose the smallest pattern that answers the question:

  • Trend: metric over time at the right grain.
  • Comparison: current period vs prior period, release vs baseline, or segment A vs B.
  • Distribution: percentiles, skew, tails, and outliers.
  • Funnel: step counts, conversion rates, and drop-offs.
  • Cohort: behavior grouped by start date, version, source, or first action.
  • Top-N: largest contributors with share of total.
  • Sanity check: row counts, null rates, first/last seen, duplicates, and data freshness.

Before concluding

  • Verify the time window and grain match the user's question.
  • Check sample size, nulls, and whether the metric is dominated by a small tail.
  • Look for freshness, rollout, telemetry opt-in, or version-coverage issues.
  • Avoid causal language unless the query design supports causality.
  • If the result is surprising, run or propose one validation query before presenting it as fact.

Finding format

md
Finding: ...Evidence: ...Confidence: High/Medium/Low because ...Caveats: ...Recommended next check: ...

Source and attribution

Source:cline/skillsinskills/data-analyst/skills/analyzerat commit2637846

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal