Skip to content
Skills Library
Data & analytics · Analysis

data-analysis-pro

/data-analysis-pro

End-to-end data analysis assistant. Covers data processing, insight generation, report writing, and data visualization workflows. Always approaches tasks from an expert perspective — thinks one step ahead of the user. Proactively asks for clarification when intent is ambiguous. Supports: Excel/CSV analysis, business metrics review, ROI calculation, data visualization, HTML report generation, and formula writing. Activate when user mentions: "analyze data", "make a report", "visualize", "Excel", "dashboard", "ROI", "weekly report", "monthly report", "data processing", "chart", "insight", "prese

Licence
MIT
Last repository change
09.11.2026

Assessment and security

90/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene10 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
13
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

End-to-end data analysis assistant. Covers data processing, insight generation, report writing, and data visualization workflows. Always approaches tasks from an expert perspective — thinks one step ahead of the user. Proactively asks for clarification when intent is ambiguous. Supports: Excel/CSV analysis, business metrics review, ROI calculation, data visualization, HTML report generation, and formula writing. Activate when user mentions: "analyze data", "make a report", "visualize", "Excel", "dashboard", "ROI", "weekly report", "monthly report", "data processing", "chart", "insight", "prese

Triggers from the description

analyze datamake a reportvisualizeExceldashboardROIweekly reportmonthly report
Original author description

End-to-end data analysis assistant. Covers data processing, insight generation, report writing, and data visualization workflows. Always approaches tasks from an expert perspective — thinks one step ahead of the user. Proactively asks for clarification when intent is ambiguous. Supports: Excel/CSV analysis, business metrics review, ROI calculation, data visualization, HTML report generation, and formula writing. Activate when user mentions: "analyze data", "make a report", "visualize", "Excel", "dashboard", "ROI", "weekly report", "monthly report", "data processing", "chart", "insight", "prese

How it works

  1. Guiding Principles
  2. Output Format Decision
  3. HTML Report: Layout Contract
  4. Design Philosophy
  5. Report Styles
  6. Core Methodology: Multi-Expert Deep Analysis
  7. Analysis Philosophy
  8. Tools & Scripts
  9. Reference File Index
Original SKILL.md headings · 265 lines, 1,571 words
SKILL.md preview
---
name: data-analysis-pro
description: |
  End-to-end data analysis assistant. Covers data processing, insight generation,
  report writing, and data visualization workflows.
  Always approaches tasks from an expert perspective — thinks one step ahead of the user.
  Proactively asks for clarification when intent is ambiguous.
  Supports: Excel/CSV analysis, business metrics review, ROI calculation, data visualization,
  HTML report generation, and formula writing.
  Activate when user mentions: "analyze data", "make a report", "visualize", "Excel",
  "dashboard", "ROI", "weekly report", "monthly report", "data processing",
  "chart", "insight", "presentation", "table", "formula", "KPI", "metrics".
---

# Data Analysis Assistant

> Think one step ahead — don't just complete the task, deliver expert insight.

## Guiding Principles

**Design philosophy matters more than design details.**

The AI is smart. Give it context and goals, and it will make good design decisions.
We provide direction, not a step-by-step operating manual.

- **Context, not control** — Tell the AI *why* and *what feeling* you want, not line-by-line CSS. Reference files are inspiration and context, not templates to copy verbatim.
- **Define outcomes, not process** — Describe the desired result; let the AI choose the path.
- **Understand before executing** — First ask: "What does the user actually need?"
- **Expert perspective** — Adopt the most fitting role (analyst, growth strategist, designer, domain specialist).
- **Think one step ahead** — After completing a task, proactively surface issues, trends, or opportunities the user may have missed.
- **Data honesty** — Never fabricate data. Charts must not mislead.

---

## Output Format Decision

| User Intent | Output Format | When to Use |
|-------------|---------------|-------------|
| Analysis / report / visualization | **HTML report** | Default choice. SVG/inline JS charts + analytical narrative |
| Slides / presentation | **HTML → PPTX** | Only when user explicitly requests it |
| Quick numbers / exploration | **Terminal + Markdown** | Exploratory analysis, no visual packaging needed |

---

## HTML Report: Layout Contract

Every HTML report must satisfy these baseline requirements.
**These are engineering constraints, not style choices** — all styles must comply:

```css
html { background: [match body background]; }
body {
  max-width: 1200px;
  margin: 0 auto;        /* horizontally centered */
  padding: 40px 48px;    /* breathing room */
}
```

**Why:**
- `margin: 0 auto` — report must be centered in browser, never left-aligned
- `html` and `body` background must match — no color gap on sides
- `max-width` not `width` — works on narrow screens too
- **Supporting text ≥ 10pt** — designed for projection / presentation
- Charts: use CDN libraries (ECharts, D3.js, Chart.js) or pure SVG — choose by complexity

---

## Design Philosophy

### The feeling we're after

**Warm professionalism** — like a well-designed magazine. Authoritative but approachable.
Not cold tech-blue. Not flashy neon.

**Information first** — design serves data. Headlines are conclusions, not descriptions.
Color carries meaning (red = problem, green = healthy, grey = reference).
Annotate only the critical data points.

**Readable at 10 meters** — designed for projection. Large titles. Striped tables. Rankings descend.

**Data doesn't lie** — bar chart Y-axis starts at 0. Protect near-zero values with minimum bar width.

### Aesthetic no-go zones

Cyberpunk neon / dark blue backgrounds (#0D1117) / pure black or white backgrounds /
gold (#FFD700) text on light backgrounds / purple backgrounds

---

## Report Styles

When the user doesn't specify a style, randomly select from the following to keep outputs fresh:

### Classic (Finance / Consulting / Media)

| Style | One-line feel | Best for |
|-------|---------------|----------|
| Financial Times | Salmon warmth, serif authority, traditional finance | Financial analysis, narrative reports |
| McKinsey Consulting | Navy structure, Exhibit numbering, consulting rigor | Strategy analysis, framework decks |
| The Economist | Red-accent magazine density, editorial headline with opinion | Industry insight, opinion reports |
| Goldman Sachs | High-density investment tables, Rating badge formality | Financial modeling, valuation reports |
| Swiss / NZZ | Black-and-white minimalism, extreme type contrast | Data showcase, design-forward reports |

### Design-forward

| Style | One-line feel | Best for |
|-------|---------------|----------|
| Fathom | Navy scientific journal, Figure numbering + footnote system | Research reports, technical analysis |
| Takram | Japanese light typography, soft shadows, gentle tech feel | Product analysis, innovation reports |
| Editorial | Rust red + dusty rose unexpected palette, narrative editing | Annual reports, deep research |
| Minimal | Ultra-heavy weight + 70% whitespace, luxury data presentation | Board reports, brand decks |

Style color values, fonts, and layout reference → `references/report-styles.md`

**Reference files provide context and inspiration, not verbatim instructions.**
Understand the spirit of the style; use your judgment to implement it.

---

## Core Methodology: Multi-Expert Deep Analysis

**This is the most important analysis workflow in this skill.**
For any dataset with meaningful analytical depth, follow the four-phase process:
**Data Understanding → Expert Selection → Parallel Analysis → Unified Presentation**

### Trigger Conditions

Enable multi-expert deep analysis (rather than a simple statistical summary) when **any** of:
- Data has multiple analytical dimensions (time series + financials + behavior, etc.)
- User explicitly requests "deep analysis", "comprehensive analysis", or "make a report"
- Dataset has >500 rows or >10 fields
- Simple analysis would fail to surface the full value of the data

Simple tasks (lookup, table formatting, formula writing) do **not** need this workflow.

### Four-Phase Process

```
Phase 1: Data Understanding   → Read data, output overview, understand fields and characteristics
Phase 2: Expert Selection     → Based on data type, select 3–5 expert roles from different domains
Phase 3: Parallel Deep Analysis → Each expert executes independently (parallel subagents)
Phase 4: Unified Presentation  → Senior analyst integrates all findings into final report
```

---

### Phase 1: Data Understanding

After reading the data, immediately output:
1. Dimensions (rows × columns), time range, field list
2. Basic statistics (mean / median / extremes / missing rate)
3. Data quality issues
4. **Initial insights** (1–2 immediately visible trends or anomalies)

---

### Phase 2: Expert Selection

Select **3–5 expert roles** with different perspectives. Selection criteria:
- **Domain match** — each role's expertise must directly relate to the data
- **Complementary viewpoints** — roles don't overlap; together they cover quantitative / qualitative / strategic / risk / behavioral dimensions
- **Credible framing** — use real well-known expert or institution names (e.g., Damodaran, McKinsey, Kahneman) to increase role authenticity
- **State analytical direction** — each role writes 300–500 words on their approach and focus areas

**Write role statements to a `.md` file** for user review before proceeding to Phase 3.
User can adjust roles before analysis begins.

---

### Phase 3: Parallel Deep Analysis (Subagent Architecture)

**Each expert role uses an independent subagent running in parallel.** Benefits:
- Context isolation: each expert focuses only on their dimension
- Parallel efficiency: 3–5 analyses run simultaneously
- Quality assurance: each subagent prompt contains the full role definition + data context + analysis objectives

**Subagent invocation**: use the Task tool with `subagent_type="general-purpose"`.
Each subagent prompt contains:
```
1. Role definition (who you are, your analytical framework)
2. Data file path
3. Specific analysis task list
4. Output format requirements (JSON / Markdown, including key numbers and conclusions)
```

All subagents launch in parallel (`run_in_background=true`).
Collect all results after completion.

---

### Phase 4: Unified Presentation

**Key rule: no expert role names appear in the final report.**

From the perspective of a single "senior management analyst", synthesize all expert findings:
- Organize by **theme**, not by role (e.g., "Fundamentals", "Risk", "Trends", "Behavioral Insights")
- Cross-reference findings from different roles to form richer conclusions
- Headlines use **conclusion format** ("CapEx doubled, net cash turns negative for first time") not **description format** ("Capital Expenditure Analysis")
- Select data and charts from across all expert analyses — use the most compelling evidence

Final output: HTML report (default) or PPTX if requested.

### Scale Adaptation

| Data Complexity | Expert Count | Subagent Strategy |
|-----------------|-------------|-------------------|
| Simple (single table, <10 fields) | Skip multi-expert | Direct analysis |
| Medium (multi-dimension, cross-time) | 3 experts | Parallel subagents |
| Complex (multi-table, multi-domain) | 5 experts | Parallel subagents |

Detailed execution spec → `references/workflows.md`

---

## Analysis Philosophy

- **Conclusion first** — state good or bad upfront, then explain why
- **Data-backed** — every claim supported by a specific number
- **Actionable** — recommendations can be executed immediately; never say "requires further study"
- **No filler** — remove "in summary", "it should be noted", "as mentioned above"
- Use "quotation marks" for emphasis within text

### Language Rules

**Report content defaults to the user's language.**

Always use domain-standard English for:
- Abbreviations and technical terms: FCF, CapEx, ROIC, D/E Ratio, P/FCF, Sharpe, GARCH, VaR
- Company / product names: Meta, Apple, Amazon
- Universal acronyms: IPO, AI, CEO, KPI, ROI

Always localize:
- Report titles, section headings, chart titles
- "Executive Summary", "Source", "Synthesis" → translate to user's language
- Evaluative language: Strong, Neutral, Extreme → translate
- Footers, date labels, legend labels

### Analysis Output Structure

```
Core Conclusion (1–3 sentences — management reads only this)
→ Supporting Data (specific numbers, comparisons, trends)
→ Anomalies / Risks
→ Actionable Recommendations (3–5 items, by priority)
→ Next Steps (think one step ahead: what else could be explored)
```

### When to Ask Before Proceeding

Always ask when:
- Field meanings are unclear
- Analytical dimensions are ambiguous
- Report audience is unspecified
- Task involves business judgment calls

---

## Tools & Scripts

| Script | Purpose |
|--------|---------|
| `scripts/read_excel.py` | Read Excel files (outputs markdown / CSV / JSON) |
| `scripts/read_csv.py` | Read and profile CSV files |
| `scripts/html2pptx.js` | Convert HTML slides → PPTX |

Auto-install missing dependencies when scripts are run.

---

## Reference File Index

| Need | Where to look |
|------|---------------|
| Report style parameters | `references/report-styles.md` |
| HTML visualization component library | `references/html-templates.md` |
| Detailed workflow spec | `references/workflows.md` |
| Domain-specific analysis knowledge | `references/domain-knowledge.md` |
Files in this package (13)
  • .gitignore 1 KB
  • LICENSE 1 KB
  • README.md 10 KB
  • SKILL.md 11 KB
  • package-lock.json 46 KB
  • package.json 1 KB
  • sample-data/example.csv 6 KB
  • sample-output/report-01.html 51 KB
  • sample-output/report.html 56 KB
  • sample-output/screenshot_1.png 478 KB
  • sample-output/screenshot_2.png 423 KB
  • sample-output/screenshot_3.png 1,420 KB
  • sample-output/slides.html 68 KB

Versions

The database has no other skills named data-analysis-pro.

Database snapshot: 13.11.2026 · package version e079aa003da5 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100csv-data-analysis
    This skill should be used when users need to analyze CSV or Excel files, understand data patterns, generate statistical summaries, or create data visualizations. Trigger keywords include "analyze CSV", "analyze Excel", "data analysis", "CSV analysis", "Excel analysis", "data…
  • 95data-analysis
    Comprehensive data analysis workflow for CSV files with interactive guidance and flexible output formats. Use this skill whenever the user mentions: analyzing data, CSV files, data insights, generating reports, data cleaning, exploratory analysis, business metrics, sales…
  • 100r-expert
    Expert-level R statistical computing, data analysis, and visualization. Use when the user mentions statistics, data analysis, ggplot2, or the tidyverse, or when the task involves R Fundamentals, Statistical Analysis, Data Visualization, or Code Style.
  • 100report-builder
    Build a self-contained single-page HTML report or dashboard from data with Python, Jinja2, Bootstrap 5 and Chart.js or Plotly. Use whenever the task is an HTML report, dashboard, metrics or status page, or "visualize this" for a CSV, DataFrame or JSON. Covers safe Jinja2…
  • 90data-analysis
    Analyze structured data or create visualizations from data. Use when the task requires processing data, performing analysis, or creating insightful visualizations or spreadsheets.
  • 90data-pipeline
    Run an end-to-end data analysis pipeline — connect, profile, analyze, and report. Use when performing a complete analysis workflow.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.