This is a structured workflow for turning messy datasets into decision-ready findings without skipping the boring parts like data quality checks and caveat documentation. It pushes you to frame the analysis question first, then pick the cheapest lane that works: spreadsheet triage, SQL slicing, notebook stats, or just writing up what you already know. The instructions cover change explanation, segment comparison, funnels, and telemetry with explicit checklists for each. What stands out is the insistence on separating observation from interpretation and actually documenting trust level before promising conclusions. If you've ever been handed a CSV export with vague instructions or needed to explain an A/B test without overselling the result, this gives you guardrails for the whole process.

skills.sh installs
230
GitHub stars
22
last updated
Jun 3, 2026

Install

$ npx -y skills add akillness/oh-my-skills --skill data-analysis --agent claude-code

Installs into .claude/skills of the current project.

Files

Data Analysis

When to use this skill

  • The user has a dataset, export, report extract, query result, or shaped event / telemetry table and wants evidence-backed conclusions.
  • The task is to understand what changed, compare segments, summarize performance, or explain anomalies in business terms.
  • The request mentions CSV, JSON, SQL tables, retention, cohorts, funnels, conversion, spend, telemetry, event exports, or KPIs.
  • The work needs data-quality checks before conclusions.
  • The user needs a concise analysis narrative, not just raw code snippets.

Do not use this skill as the main workflow when:

  • The main goal is repeated anomaly or code-pattern scanning across code/data assets → use pattern-detection.
  • The main goal is building or tuning a specific BI dashboard / Looker Studio + BigQuery workflow → use looker-studio-bigquery.
  • The task is repository navigation or call-site tracing rather than dataset reasoning → use codebase-search.
  • The problem is raw log triage / incident reconstruction rather than dataset analysis → use log-analysis.

Sponsors

Details

Repository
github.com/akillness/oh-my-skills
First seen
Jun 3, 2026

More from akillness/oh-my-skills

All 81

Recommended

1juliusbrussee avatarcavemanjuliusbrussee/cavemanUltra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels618.3Kskills.sh installs
2mattpocock avatargrill-memattpocock/skillsA relentless interview to sharpen a plan or design.1.5Mskills.sh installs
3shadcn avatarimproveshadcn/improveSurvey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on s40Kskills.sh installs
4obra avatarsystematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes326.7Kskills.sh installs
5forrestchang avatarkarpathy-guidelinesforrestchang/andrej-karpathy-skillsBehavioral guidelines to reduce common LLM coding mistakes through explicit assumptions, simplicity, and verifiable success criteria.17.9Kskills.sh installs
6vercel-labs avatarfind-skillsvercel-labs/skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express int4.3Mskills.sh installs