csv-analyzer

casper-studios/casper-marketplace · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/casper-studios/casper-marketplace --skill csv-analyzer
0 commentsdiscussion
summary

Comprehensive CSV data analysis and visualization engine. Run the script, then use this guide to interpret results and provide insights to users.

skill.md

CSV Analyzer

Overview

Comprehensive CSV data analysis and visualization engine. Run the script, then use this guide to interpret results and provide insights to users.

Quick Start

cd ~/.claude/skills/csv-analyzer/scripts
export $(grep -v '^#' /path/to/project/.env | xargs 2>/dev/null)
python3 analyze_csv.py /path/to/data.csv

Chart Selection Decision Tree

IMPORTANT: Choose charts based on what the user needs to understand:

What is the user trying to understand?
├── "What does my data look like?" (Overview)
│   └── Run with defaults → overview_dashboard.png
├── "Is my data clean?" (Quality)
│   └── Check: quality_score, missing_values, duplicates
│   └── Show: missing_values.png if problems exist
├── "What's the distribution?" (Single Variable)
│   ├── Numeric → numeric_distributions.png (histogram + KDE)
│   ├── Categorical → categorical_distributions.png (bar chart)
│   └── Time-based → time_series.png
├── "Are there outliers?" (Anomalies)
│   └── box_plots.png → points beyond whiskers are outliers
├── "How are variables related?" (Relationships)
│   ├── 2 numeric vars → correlation_heatmap.png
│   ├── 2-6 numeric vars → pairplot.png (scatter matrix)
│   ├── Numeric vs Categorical → violin_plot.png
│   └── All numeric → correlation_heatmap.png
└── "Can I predict X from Y?" (Predictive)
    └── correlation_heatmap.png → |r| > 0.5 suggests predictive power

How to Interpret Results (For Claude)

Quality Score Interpretation

Score Grade What to Tell User
90-100 A "Your data is excellent quality - ready for analysis"
80-89 B "Good quality data with minor issues worth noting"
70-79 C "Moderate quality - address missing values before critical analysis"
60-69 D "Significant quality issues - recommend data cleaning first"
<60 F "Critical issues - data needs substantial cleaning"

Correlation Interpretation

|r| Value Strength What to Say
0.9 - 1.0 Very Strong "X and Y are very strongly related - almost deterministic"
0.7 - 0.9 Strong "X and Y have a strong relationship - X could help predict Y"
0.5 - 0.7 Moderate "X and Y are moderately correlated - some predictive value"
0.3 - 0.5 Weak "X and Y have a weak relationship - limited predictive power"
0.0 - 0.3 Negligible "X and Y appear unrelated"

Sign matters:

  • Positive: "As X increases, Y tends to increase"
  • Negative: "As X increases, Y tends to decrease"

Skewness Interpretation

Skewness Distribution Shape Recommendation
< -1 Heavy left tail "Most values are high, with some very low outliers"
-1 to -0.5 Mild left skew "Slightly more low outliers than high"
-0.5 to 0.5 Symmetric "Nicely balanced distribution - good for most analyses"
0.5 to 1 Mild right skew "Slightly more high outliers than low"
> 1 Heavy right tail "Most values are low, with some very high outliers. Consider log transform for modeling."

Outlier Assessment

When reporting outliers:

  • Few outliers (<1%): "A few extreme values that may warrant investigation"
  • Moderate outliers (1-5%): "Notable outliers - check if they're errors or genuine extremes"
  • Many outliers (>5%): "High outlier rate suggests either data issues or a non-normal distribution"

Insight Generation Framework

After running analysis, provide insights in this order:

1. Data Overview (Always)

"Your dataset has [rows] records and [cols] columns:
- [n] numeric columns: [list top 3]
- [n] categorical columns: [list top 3]
- Data quality score: [score]/100 ([grade])"

2. Key Findings (Pick most relevant)

If quality issues exist:

"I noticed some data quality concerns:
- [X]% missing values in [column] - [recommend: drop/impute/investigate]
- [N] duplicate rows detected - [recommend: keep first/remove all/investigate]"

If strong correlations found:

"Interesting relationships I found:
- [col1] and [col2] are strongly correlated (r=[value]) - [interpretation]
- This suggests [actionable insight]"

If outliers detected:

"I detected outliers in [columns]:
- [column]: [n] values beyond normal range ([min outlier] to [max outlier])
- These could be [data errors / genuine extremes / worth investigating]"

If skewed distributions:

"[Column] has a [right/left]-skewed distribution:
- Most values cluster around [median]
- But there are extreme values up to [max]
- For modeling, consider [log transform / robust methods]"

3. Recommendations (Based on findings)

Finding Recommendation
Missing >20% in column "Consider dropping this column or investigating why it's missing"
Missing <5% scattered "Safe to impute with median (numeric) or mode (categorical)"
High correlation (>0.9) "These columns may be redundant - consider keeping only one"
Many outliers "Use robust statistics (median instead of mean) or investigate data collection"
Highly skewed "Apply log transform before linear modeling"
Low quality score "Prioritize data cleaning before analysis"

Multi-Chart Dashboard Requests

When user asks for a "dashboard" or "comprehensive view":

# Generate all visualizations
python3 analyze_csv.py data.csv --format html --max-charts 10

Then present charts in this order:

  1. overview_dashboard.png - "Here's your data at a glance"
  2. correlation_heatmap.png - "Key relationships between variables"
  3. numeric_distributions.png - "How your numeric data is distributed"
  4. box_plots.png - "Outlier analysis"
  5. categorical_distributions.png - "Category breakdowns" (if applicable)

Command Reference

Basic Analysis

python3 analyze_csv.py data.csv

Full Report with All Charts

python3 analyze_csv.py data.csv --format markdown --max-charts 10

Quick Analysis (No Charts)

python3 analyze_csv.py data.csv --no-charts

Large Files (>100MB)

python3 analyze_csv.py huge.csv --sample 50000

Specific Date Columns

python3 analyze_csv.py data.csv --date-columns created_at updated_at

JSON for Programmatic Use

python3 analyze_csv.py data.csv --format json --no-charts

Custom Output Location

python3 analyze_csv.py data.csv --output-dir /path/to/project/.tmp/analysis

Chart Descriptions (For Explaining to Users)

Chart When to Show How to Describe
overview_dashboard.png Always for first look "Here's a bird's eye view of your data"
missing_values.png If missing data exists "This shows where your data has gaps"
numeric_distributions.png When exploring distributions "This shows how your numeric values are spread out"
box_plots.png When checking for outliers "The dots outside the boxes are potential outliers"
correlation_heatmap.png When exploring relationships "Darker colors = stronger relationships"
categorical_distributions.png For category analysis "This shows the breakdown of your categories"
time_series.png For temporal data "Here's how your data changes over time"
pairplot.png For multivariate exploration "Each cell shows how two variables relate"
violin_plot.png Comparing groups "This shows how distributions differ across groups"

Common User Questions → Actions

User Says Action
"Analyze this CSV" Run full analysis, show overview + key insights
"Is my data clean?" Focus on quality_score, missing values, duplicates
"Find patterns" Show correlation_heatmap, highlight strong correlations
"Are there outliers?" Show box_plots, list outlier counts per column
"Compare X across Y" Generate violin_plot for numeric X vs categorical Y
"Show me trends" Generate time_series if datetime column exists
"Create a dashboard" Generate all charts, present organized summary
"What should I clean?" List columns with missing >5%, duplicates, outliers

Output Locations

Charts are saved to:

  • Default: ~/.claude/skills/csv-analyzer/scripts/.tmp/csv_analysis/
  • Custom: Use --output-dir /path/to/project/.tmp/analysis

Always copy charts to user's project .tmp for visibility:

cp ~/.claude/skills/csv-analyzer/scripts/.tmp/csv_analysis/*.png /path/to/project/.tmp/csv_analysis/

Cost

Free - runs entirely locally using pandas, matplotlib, seaborn, scipy.

Dependencies

pip install pandas matplotlib seaborn scipy numpy
how to use csv-analyzer

How to use csv-analyzer on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add csv-analyzer
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/casper-studios/casper-marketplace --skill csv-analyzer

The skills CLI fetches csv-analyzer from GitHub repository casper-studios/casper-marketplace and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/csv-analyzer

Reload or restart Cursor to activate csv-analyzer. Access the skill through slash commands (e.g., /csv-analyzer) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.553 reviews
  • Chaitanya Patil· Dec 28, 2024

    csv-analyzer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Sofia Torres· Dec 28, 2024

    Solid pick for teams standardizing on skills: csv-analyzer is focused, and the summary matches what you get after install.

  • Alexander White· Dec 12, 2024

    Keeps context tight: csv-analyzer is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Jin Singh· Dec 8, 2024

    csv-analyzer has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Pratham Ware· Dec 4, 2024

    We added csv-analyzer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Xiao Menon· Dec 4, 2024

    Registry listing for csv-analyzer matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Xiao Mehta· Nov 27, 2024

    Useful defaults in csv-analyzer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Jin Kapoor· Nov 23, 2024

    csv-analyzer reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Piyush G· Nov 19, 2024

    Keeps context tight: csv-analyzer is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Hassan Jain· Nov 11, 2024

    We added csv-analyzer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 53

1 / 6