skills/data/analysis/SKILL.md
Use when exploring a dataset for patterns, trends, and business insights — EDA, segmentation, anomaly detection, and visualization guidance. Generates the Observation → Insight → Action chain. NOT for schema validation or data quality scoring (use the data/data skill) or SQL queries (use data:analyze).
npx skillsauth add mikeparcewski/wicked-garden analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Explore datasets, identify patterns, and generate actionable insights.
/wicked-garden:data:analyze explore data/sales.csv
This will:
After exploration, ask specific questions:
/wicked-garden:data:analyze sales.csv
Key questions:
Basic explorations:
Common segmentations:
Detection methods:
Bad (just observations):
Good (insights with actions):
### 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)
| 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) |
wicked-garden:data:analyze - Primary tool for data queries via DuckDB:
/wicked-garden:data:analyze data.csv
Native tasks - Document insights via TaskCreate with metadata.event_type="task"
wicked-brain:memory - Store analysis patterns for reuse
For detailed content:
development
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
testing
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
tools
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or when one of the per-archetype slash commands resolves to this skill.
development
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".