agentleFS
surasakchosurasakcho/claude-skills/data-analyst/SKILL.md

data-analyst

Skill0 starsChanged 5 months agoMITView on GitHub

Guidelines for data analytics tasks — visualization, summary statistics, data scoping, regression analysis, and econometrics. Invoke when starting any analysis, building charts, computing summary stats, fitting regression models, or applying econometric methods.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use web-researcher, tech-lead and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xcrrrSkill

    web-researcher

    Use this skill when you need to research a topic online, gather information from multiple sources, or evaluate source credibility. Trigger phrases: 'research', 'find information about', 'look up', 'investigate'. Not for academic systematic reviews (use literature-reviewer) or fact-checking specific claims (use fact-checker).

    Also in 3 projects that use this

  • lotosbinSkill

    tech-lead

    技术负责人专家,精通技术架构设计、技术选型、代码审查和团队技术管理

    Also in 3 projects that use this

  • JohnJBorenSkill

    ux-researcher

    User research methods, interview guides, usability testing, and persona development

    Also in 3 projects that use this

  • o2alexanderfedinSkill

    solution-architect

    Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.

    Also in 3 projects that use this

  • belokonmSkill

    security-engineer

    Expert in infrastructure security, DevSecOps pipelines, and zero-trust architecture design.

    Also in 3 projects that use this

  • JohnJBorenSkill

    product-manager

    Product development workflows, PRDs, prioritization frameworks, and roadmap planning

    Also in 5 projects that use this

  • +2 more from JohnJBoren

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing any plotting or aggregation code, ask the user:

    line 14
  2. Distinctive:

    If the user says "use defaults" or doesn't answer, proceed with both defaults.

    line 26
  3. Very specific:

    When you clip data (e.g. series.clip(upper=p99)) to set axis limits or bin ranges for a histogram:

    line 32
  4. Very specific:

    Use the clipped variable only for the histogram bins / sns.histplot / axis range

    line 34
  5. Very specific:

    When placing a reference line (axvline) for a stat that falls outside the display range, clip the position to the display cap so the line …

    line 36
  6. Distinctive:

    Every figure annotation (text box, legend, title) must state:

    line 54
  7. Distinctive:

    If outliers were dropped by user request: add "(outliers excluded)" to the annotation

    line 56
  8. Distinctive:

    If the user says "clip the stats too" or "drop outliers for this one", apply only to that specific figure.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data Analyst Guidelines

Apply these rules for every visualization and every summary statistic produced in this session.


1. Before producing any visualization or statistic — ask these two questions explicitly

Before writing any plotting or aggregation code, ask the user:

Q1 — Observation scope:

"Should this include all observations, or do you want to drop outliers first? If dropping, which method — IQR, percentile cap (e.g. p99), or a specific threshold?"

Q2 — Statistic base:

"Should mean/median/std and other statistics be computed on the raw (unclipped) data, or on the clipped/outlier-dropped series?"

Default answers (use these unless the user says otherwise):

  • Q1 default: include all observations — do not drop any rows
  • Q2 default: compute statistics from raw, unclipped data

If the user says "use defaults" or doesn't answer, proceed with both defaults.


2. Clipping is for visualization only

When you clip data (e.g. series.clip(upper=p99)) to set axis limits or bin ranges for a histogram:

  • Use the clipped variable only for the histogram bins / sns.histplot / axis range
  • Compute mean, median, std, and all other statistics from the unclipped original series
  • When placing a reference line (axvline) for a stat that falls outside the display range, clip the position to the display cap so the line stays visible, but the label must show the true unclipped value
# RIGHT
_raw = df['delay_hours']                         # full series, no clip
_vis = _raw.clip(upper=p99)                      # visualization only
ax.hist(_vis, bins=_bins)
ax.axvline(min(_raw.median(), p99), label=f'Median: {_raw.median():.1f}h')

# WRONG — never do this
_vis = _raw.clip(upper=p99)
ax.axvline(_vis.median(), label=f'Median: {_vis.median():.1f}h')  # biased!

3. Always surface the scope clearly in the figure

Every figure annotation (text box, legend, title) must state:

  • n = X,XXX — the number of observations the statistic is based on (always unclipped count)
  • If outliers were dropped by user request: add "(outliers excluded)" to the annotation

4. Stat lines on histograms must use unclipped series

Any axvline or annotation that shows mean or median must be computed from the unclipped source series, even when the histogram itself is trimmed for display.


5. When the user changes defaults mid-session

If the user says "clip the stats too" or "drop outliers for this one", apply only to that specific figure. Ask again for the next one — do not carry the override forward silently.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.