Skip to content

mikeparcewski/wicked-garden / skills/data

wicked-garden-data

Verified

Data engineering, analysis, and ML toolkit. One skill, routed sub-actions: analyze (interactive EDA on a CSV/Excel/data file), profile / validate / quality (schema-level data engineering ops), ml review / ml pipeline (model review + training-pipeline design), pipeline design / pipeline review (ETL architecture), ontology (recommend Schema.org, Dublin Core, DCAT, FOAF, GoodRelations, SKOS, or a custom shape for a dataset), shapes (a live source's data shapes, proposed for review). Use when: "analyze this CSV/Excel/data file" / "explore this dataset" / one-off data exploration; "profile this dataset" / "validate data against a schema" / "generate a data quality report"; "review this ML model" / "design an ML training pipeline"; "design a data pipeline" / "review this ETL"; "recommend an ontology for this data" / "map columns to a public ontology"; "propose data shapes for <source>"; or any former /wicked-garden:data:* invocation. Delegated deep passes: the `wicked-garden-data-engineer` worker skill.

FileKindSize
SKILL.mdskill md8.0 KB
refs/analysis-templates.mdmarkdown3.3 KB
refs/analyze.mdmarkdown5.1 KB
refs/data-examples.mdmarkdown4.9 KB
refs/data.mdmarkdown3.8 KB
refs/ml-templates.mdmarkdown4.0 KB
refs/ml.mdmarkdown5.7 KB
refs/pipeline-templates.mdmarkdown4.6 KB
refs/pipeline.mdmarkdown4.8 KB
refs/shapes.mdmarkdown6.1 KB

refs/analyze.md

View on GitHub
# Data Analysis Rubric

Apply this inline. Route by `--focus` to the right analysis mode. File has been
pre-profiled (columns / types / nulls / sample rows) by the caller.

## EDA output format (default / --focus stats)

```markdown
## Data Analysis Report

**Dataset**: {name}
**Analysis Date**: {date}

### Executive Summary
{2-3 key takeaways}

### Quick Stats
- **Rows**: {count}  **Columns**: {count}  **Date Range**: {start–end}

### Initial Findings
1. {Observable pattern or anomaly}
2. {Interesting correlation or trend}

### Visualization Recommendations
- {Chart type}: {What it shows}

### Next Steps / Questions Raised
- {Follow-up analyses or data needs}

**Confidence**: {HIGH|MEDIUM|LOW}
```

## Statistical analysis patterns

**Distributions**: MIN / Q1 / MEDIAN / Q3 / MAX; histogram or box-plot.
**Categorical**: frequency + percentage breakdown; bar chart.
**Time series**: DATE_TRUNC day/week aggregation; line chart.
**Correlations**: CORR(a, b) spot-check.
**Cohort/RFM**: group by signup month; recency/frequency/monetary.

## Insight pattern

- **Observation**: What the data shows (fact).
- **Insight**: Why it matters (interpretation).
- **Action**: What to do (recommendation).
- **Confidence**: HIGH | MEDIUM | LOW (state sample size + caveats).

**Bad** (just observations): "Average order value is $45", "60% of customers
are in the US".

**Good** (insight with action):
```
### Insight: Weekend Shopping Behavior
**Observation**: Sales peak on Friday (+40% vs weekday avg)
**Insight**: Customers shop for weekend needs on Friday.
**Action**: Launch "Friday Flash Sale" campaign (+15% expected)
**Confidence**: HIGH (consistent over 6 months)
```

## Segmentation methods

- **RFM**: Recency, Frequency, Monetary value.
- **Cohorts**: group by signup / first-purchase month.
- **Geographic**: by region, country, city.
- **Behavioral**: by usage patterns.

## Anomaly detection methods

- Statistical outliers (>3 standard deviations).
- Unusual patterns (volume spikes/drops).
- Temporal anomalies (day-of-week deviations).

## Visualization guidance

| Data Type | Comparison | Best Chart |
|-----------|------------|------------|
| Time series | Trend over time | Line chart |
| Categorical | Compare values | Bar chart |
| Distribution | Show spread | Histogram, Box plot |
| Relationship | Correlation | Scatter plot |
| Composition | Part of whole | Stacked bar, Pie |
| Geographic | Location data | Map (choropleth) |

## Best practices

- **Start simple**: begin with basic aggregations before complex models.
- **Validate assumptions**: check data quality, verify calculations.
- **Tell a story**: lead with the "so what?" and make it actionable.
- **Be honest about uncertainty**: note limitations, quantify confidence.

## Common pitfalls

- **Correlation ≠ Causation**: ice cream and drownings both increase in summer.
- **Simpson's Paradox**: aggregate trend may reverse when segmented.
- **Survivorship Bias**: include failed cases for balanced view.
- **Cherry-picking**: report all patterns, not just favorable ones.

## Detailed templates

See [analysis-templates.md](analysis-templates.md) for full report templates:
exploratory analysis report, insight report, segment analysis, A/B test
results, and anomaly report.

## --focus quality (data-quality mode)

| Dimension | Check |
|-----------|-------|
| Completeness | Null rates per column |
| Uniqueness | Duplicate detection |
| Validity | Type conformance + constraints |
| Consistency | Cross-field validation |
| Timeliness | Freshness metrics |

```markdown
## Data Quality Report

**Dataset**: {name}  **Rows**: {count}  **Columns**: {count}

### Quality Metrics
| Dimension | Score | Issues |
|-----------|-------|--------|
| Completeness | {%} | {null columns} |
| Uniqueness  | {%} | {duplicate rate} |
| Validity    | {%} | {constraint violations} |

### Critical Issues
- {Issue with severity and impact}

### Recommendations
1. {Prioritized action items}
```

## --focus warehouse (warehouse/lakehouse mode)

Evaluate dimensional model fit: Star vs Snowflake vs Data Vault vs Wide Table.
Cover partitioning / clustering / materialization strategy and cost plan.

```markdown
## Warehouse Analysis: {domain}

### Approach
Pattern: {Star|Snowflake|Data Vault|Wide Table}
Justification: {why}

### Schema
#### Fact: {fact_table}
| Column | Type | Description | Source |

#### Dimension: {dim_table}
| Column | Type | SCD Type | Description |

### Performance
- Partitioning: {strategy}   Clustering: {columns}   Materialization: {views vs tables}

### Cost Plan
{Storage tier, compute, optimization levers}
```

## --focus ml (ML-readiness mode)

Assess training data quality for ML: leakage, imbalance, feature distributions,
label quality. See refs/ml.md for full ML pipeline rubric.

## Scenarios block (--scenarios)

When `--scenarios` is set, append:
```yaml
scenarios:
  api:
    - name: "{dataset}_baseline"
      given: "data file at {path}"
      when: "analyze --focus {focus}"
      then: "key finding X observed"
  perf:
    - name: "{dataset}_large_file"
      given: "file with {N} rows"
      when: "profiling runs"
      then: "completes within threshold"
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall