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/analysis-templates.md

View on GitHub
---
phase_relevance: ["design", "build"]
archetype_relevance: ["*"]
---
# Analysis Output Templates

Standard templates for data analysis reports.

## Exploratory Analysis Report

```markdown
## Exploratory Analysis: {dataset}

**Date**: {date}
**Analyst**: {name}
**Rows**: {count}

### Quick Stats
- **Date Range**: {start} to {end}
- **Key Metrics**: {summary}
- **Data Quality**: {score}/100

### Data Profile
| Column | Type | Nulls | Unique | Min | Max |
|--------|------|-------|--------|-----|-----|
| {col}  | {type} | {pct}% | {n} | {min} | {max} |

### Distributions
{Summary of key metric distributions}

### Key Findings
1. {Finding with supporting data}
2. {Finding with supporting data}
3. {Finding with supporting data}

### Data Quality Issues
- {Issue and impact}

### Questions Raised
- {Question needing further investigation}

### Next Steps
- {Recommended follow-up analysis}
```

## Insight Report

```markdown
## Data Insights: {topic}

**Context**: {why this analysis}
**Data**: {source and timeframe}
**Confidence**: {HIGH|MEDIUM|LOW}

### Executive Summary
{Top 3 takeaways in bullet points}

---

### Insight 1: {Title}

**Observation**: {What the data shows - facts only}

**Insight**: {What it means - interpretation}

**Action**:
- Specific action 1
- Expected impact: {quantified if possible}

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

---

### Insight 2: {Title}
{Same structure as above}

---

### Supporting Analysis
{Methodology and data quality notes}

### Assumptions & Limitations
- {Key assumption}
- {Data limitation}

### Next Steps
1. {Immediate action}
2. {Follow-up analysis}
```

## Segment Analysis Report

```markdown
## Segment Analysis: {dimension}

**Segments**: {n segments}
**Method**: {RFM, cohort, behavioral, etc.}

### Segment Overview
| Segment | Size | % Total | Avg Value | Key Trait |
|---------|------|---------|-----------|-----------|
| {name}  | {n}  | {pct}%  | ${avg}    | {trait}   |

### Segment Profiles

#### Segment 1: {Name}
- **Size**: {n} ({pct}%)
- **Characteristics**: {description}
- **Value**: ${total} ({pct}% of revenue)
- **Recommended Action**: {action}

### Cross-Segment Insights
- {Pattern across segments}

### Recommended Actions
1. **{Segment}**: {Action}
```

## A/B Test Results

```markdown
## A/B Test Results: {experiment name}

**Test Period**: {start} to {end}
**Sample Size**: Control: {n}, Treatment: {n}

### Summary
| Metric | Control | Treatment | Lift | Confidence |
|--------|---------|-----------|------|------------|
| {KPI}  | {val}   | {val}     | +{x}%| {pct}%     |

### Statistical Details
- **Test Type**: {t-test, chi-square, etc.}
- **p-value**: {p}
- **Confidence Interval**: [{low}, {high}]

### Recommendation
{SHIP / DO NOT SHIP / NEEDS MORE DATA}

### Caveats
- {Limitation or consideration}
```

## Anomaly Report

```markdown
## Anomaly Detection: {metric}

**Period**: {date range}
**Method**: {statistical, isolation forest, etc.}

### Anomalies Detected
| Date | Value | Expected | Deviation | Severity |
|------|-------|----------|-----------|----------|
| {date} | {val} | {expected} | {+/-x}% | {HIGH/MED/LOW} |

### Investigation

#### Anomaly 1: {Date}
- **Observed**: {value}
- **Expected**: {value} (based on {method})
- **Possible Causes**:
  1. {Hypothesis}
  2. {Hypothesis}
- **Impact**: {business impact}
- **Action**: {recommendation}

### Systemic Issues
- {Pattern in anomalies}
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated 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