mikeparcewski/wicked-garden / skills/data
wicked-garden-data
VerifiedData 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.0 KB |
| refs/analysis-templates.md | markdown | 3.3 KB |
| refs/analyze.md | markdown | 5.1 KB |
| refs/data-examples.md | markdown | 4.9 KB |
| refs/data.md | markdown | 3.8 KB |
| refs/ml-templates.md | markdown | 4.0 KB |
| refs/ml.md | markdown | 5.7 KB |
| refs/pipeline-templates.md | markdown | 4.6 KB |
| refs/pipeline.md | markdown | 4.8 KB |
| refs/shapes.md | markdown | 6.1 KB |
refs/ml-templates.md
View on GitHub---
phase_relevance: ["design", "build"]
archetype_relevance: ["*"]
---
# ML Output Templates
Standard templates for ML model reviews and documentation.
## Model Review Report
```markdown
## ML Model Review: {model_name}
**Type**: {classification/regression/clustering/ranking}
**Status**: {development/staging/production}
**Reviewer**: {name}
**Date**: {date}
### Summary
{2-3 sentence assessment of model readiness}
### Assessment
#### Data Quality: {score}/10
- [ ] Sufficient volume (>1000x features)
- [ ] Label quality verified
- [ ] No data leakage from target
- [ ] Class balance acceptable
- [ ] Train/test split proper
**Notes**: {observations}
#### Feature Engineering: {score}/10
- [ ] Features available at inference time
- [ ] Proper scaling/encoding applied
- [ ] No leakage from target
- [ ] Feature importance analyzed
- [ ] Missing value handling documented
**Notes**: {observations}
#### Model Choice: {score}/10
- [ ] Appropriate for problem type
- [ ] Baseline model established
- [ ] Complexity justified by improvement
- [ ] Alternatives considered and documented
- [ ] Model interpretability assessed
**Notes**: {observations}
#### Evaluation: {score}/10
- [ ] Train/test split strategy proper
- [ ] Metrics aligned with business goal
- [ ] Cross-validation performed
- [ ] Performance acceptable for use case
- [ ] Confidence intervals reported
**Metrics**:
| Metric | Train | Test | Target |
|--------|-------|------|--------|
| {metric} | {val} | {val} | {target} |
**Notes**: {observations}
#### Deployment Readiness: {score}/10
- [ ] Inference latency acceptable (<{X}ms)
- [ ] Model size appropriate
- [ ] Feature pipeline reproducible
- [ ] Monitoring instrumented
- [ ] Rollback plan documented
- [ ] A/B testing framework ready
**Notes**: {observations}
### Recommendations
| Priority | Recommendation | Impact | Effort |
|----------|----------------|--------|--------|
| P1 | {action} | HIGH | {S/M/L} |
| P2 | {action} | MEDIUM | {S/M/L} |
| P3 | {action} | LOW | {S/M/L} |
### Overall Assessment
**Score**: {total}/50
**Decision**: [APPROVE | CONDITIONAL APPROVE | NEEDS REWORK]
**Conditions** (if applicable):
1. {condition that must be met before approval}
**Next Steps**:
1. {immediate action}
2. {follow-up action}
```
## Model Card
```markdown
# Model Card: {model_name}
## Model Details
- **Name**: {model_name}
- **Version**: {version}
- **Type**: {classification/regression/etc}
- **Algorithm**: {RandomForest/XGBoost/NeuralNet/etc}
- **Framework**: {sklearn/pytorch/tensorflow}
- **Created**: {date}
- **Owner**: {team/person}
## Intended Use
- **Primary use**: {description}
- **Users**: {who will use this}
- **Out of scope**: {what this should NOT be used for}
## Training Data
- **Source**: {data source}
- **Size**: {rows} rows, {features} features
- **Date range**: {start} to {end}
- **Preprocessing**: {summary of transformations}
## Evaluation
| Metric | Value | Target |
|--------|-------|--------|
| {metric} | {val} | {target} |
## Ethical Considerations
- **Bias**: {known biases and mitigations}
- **Fairness**: {fairness testing performed}
- **Privacy**: {PII handling}
## Limitations
- {limitation 1}
- {limitation 2}
## Deployment
- **Endpoint**: {URL/service}
- **Latency**: p50={X}ms, p99={Y}ms
- **Throughput**: {requests/sec}
## Monitoring
- **Dashboards**: {links}
- **Alerts**: {configured alerts}
- **Retraining trigger**: {criteria}
```
## Experiment Log
```markdown
## Experiment: {experiment_name}
**Goal**: {what are we trying to achieve}
**Baseline**: {current performance}
**Target**: {goal performance}
### Experiment 1: {description}
**Changes**: {what was changed}
**Results**:
| Metric | Before | After | Change |
|--------|--------|-------|--------|
| {metric} | {val} | {val} | {+/-X%} |
**Conclusion**: {SUCCESS/FAILED/INCONCLUSIVE}
**Notes**: {observations}
### Experiment 2: {description}
...
### Summary
**Best configuration**: {description}
**Final performance**: {metrics}
**Next steps**: {what to try next or ship}
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |