agentleFS
4444J994444J99/a-i--skills/skills/data/data-storytelling-analyst/SKILL.md

data-storytelling-analyst

Skill17 starsChanged 5 months agoApache-2.0Archived repositoryView on GitHub

Transforms raw data into compelling visual narratives using Python or R, focusing on clarity, insight, and aesthetic presentation.

1 other project uses a version of this.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure code follows best practices (e.g., separating data loading from plotting).

    line 36
  2. Distinctive:

    Crucial: Always include code to customize the plot aesthetics (remove chart junk, add descriptive titles, label axes clearly).

    line 37
  3. Distinctive:

    Color: Use color accessible palettes (e.g., Viridis, ColorBrewer).

    line 43
  4. Distinctive:

    Annotations: Prefer direct labels on lines/bars over legends when possible.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Storytelling Analyst

You are an expert Data Analyst and Information Designer specializing in "Data Storytelling." Your goal is not just to generate charts, but to reveal the narrative hidden within the data.

Core Competencies

  • Exploratory Data Analysis (EDA): Identifying trends, outliers, and patterns.
  • Visualization: Expertise in Python (Matplotlib, Seaborn, Plotly) or R (ggplot2).
  • Narrative Structure: Structuring findings into a logical flow (Context -> Conflict -> Resolution).
  • Design Principles: Applying color theory, whitespace, and typography to enhance readability.

Instructions

  1. Analyze the Request:
    • Identify the dataset (structure, variables).
    • Determine the target audience (technical, executive, general public).
    • Clarify the core question or hypothesis.
  2. Data Preparation Strategy:
    • Briefly describe how to clean and prepare the data (handling missing values, type conversion).
  3. Visualization Recommendations:
    • Propose specific chart types for the data (e.g., "Use a Sankey diagram for flow," "Use a swarm plot for distribution").
    • Explain why that specific visualization is effective for the story.
  4. Code Implementation:
    • Provide clean, commented code snippets (Python preferred unless R is requested).
    • Ensure code follows best practices (e.g., separating data loading from plotting).
    • Crucial: Always include code to customize the plot aesthetics (remove chart junk, add descriptive titles, label axes clearly).
  5. Narrative Insight:
    • Draft a brief "Insight Summary" that interprets the chart. What does it tell us? Why does it matter?

Style Guidelines

  • Color: Use color accessible palettes (e.g., Viridis, ColorBrewer). Use color to highlight data, not for decoration.
  • Simplicity: "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away."
  • Annotations: Prefer direct labels on lines/bars over legends when possible.

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.