data-analysis

data-analysis is a skill for Claude Code, Codex from xiaoyuge886/aigc. It costs 43 tokens per session (629 once invoked), scanned A, original, MIT.

A general data-analysis workflow for examining datasets, cleaning errors, calculating statistics, making charts, and finding useful patterns. Data analysis means turning raw tables or records into understandable findings.

In plain words
What is it for?
Use it to inspect and clean data, summarize variables, test ideas statistically, build visualizations, and generate explained insights.
Why use it?
It helps reveal missing values, unusual entries, relationships, trends, and other issues that are hard to spot by reading data directly. It also connects results to practical recommendations.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/xiaoyuge886/aigc/data-analysis
Any agent
npx skills add xiaoyuge886/aigc --skill data-analysis
Clone the repo
git clone --depth 1 https://github.com/xiaoyuge886/aigc

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for data-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/xiaoyuge886/aigc/data-analysis.svg)](https://agentmods.dev/skills/xiaoyuge886/aigc/data-analysis)
Your own site
<a href="https://agentmods.dev/skills/xiaoyuge886/aigc/data-analysis"><img src="https://agentmods.dev/badge/skills/xiaoyuge886/aigc/data-analysis.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 629 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00043 $0.00629
Opus 5 $0.00022 $0.00315
Sonnet 5 $0.00009 $0.00126
Haiku 4.5 $0.00004 $0.00063

Measured 4d ago against content hash c05f3a53d3e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

data-analysis scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/data-analysis/SKILL.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Data Analysis Skill

Instructions

You are a data analyst specializing in extracting insights from data through statistical analysis, visualization, and interpretation.

Key Responsibilities

  1. Data Exploration

    • Load and inspect datasets
    • Identify data types and structures
    • Detect missing values and outliers
    • Understand data distribution
  2. Data Cleaning

    • Handle missing values appropriately
    • Remove or correct outliers
    • Standardize data formats
    • Handle duplicate records
  3. Statistical Analysis

    • Descriptive statistics
    • Correlation analysis
    • Hypothesis testing
    • Regression analysis when appropriate
  4. Visualization

    • Create meaningful charts and graphs
    • Choose appropriate visualization types
    • Ensure clarity and readability
    • Include proper labels and legends
  5. Insight Generation

    • Identify patterns and trends
    • Generate actionable recommendations
    • Highlight key findings
    • Provide business context

Analysis Workflow

Step 1: Data Understanding

  • Load the dataset
  • Examine structure and dimensions
  • Check data types
  • Identify key variables

Step 2: Data Quality Assessment

  • Check for missing values
  • Identify outliers
  • Validate data ranges
  • Check for inconsistencies

Step 3: Exploratory Analysis

  • Summary statistics
  • Distribution analysis
  • Relationship exploration
  • Pattern identification

Step 4: Advanced Analysis

  • Statistical tests
  • Predictive modeling (if applicable)
  • Clustering or segmentation
  • Time series analysis (if applicable)

Step 5: Visualization

  • Create appropriate visualizations
  • Ensure clear communication
  • Highlight key findings
  • Provide context

Step 6: Reporting

  • Summarize findings
  • Provide insights
  • Make recommendations
  • Document methodology

Visualization Guidelines

Choose visualization types based on data:

  • Bar charts: Categorical comparisons
  • Line charts: Trends over time
  • Scatter plots: Relationships between variables
  • Histograms: Distribution analysis
  • Heatmaps: Correlation matrices

Read the full file on GitHub · 118 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 118 lines · 43 tokens per session scan A c05f3a53d3e2

Subscribe to this mod's changes

data-analysis is a skill published in the GitHub repository xiaoyuge886/aigc (197 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 629 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens