wicked-garden-data
Skill9 starsChanged 7 months agoMITView on GitHub
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).
- Installs packages
In this repository142 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- plugin-json-schemaSkill
- readme-style-guideSkill
- releaseSkill
- scaffoldSkill
- wicked-garden-agentic-agentic-patternsSkill
- wicked-garden-agentic-architectSkill
- wicked-garden-agentic-context-engineeringSkill
- wicked-garden-agentic-frameworksSkill
- wicked-garden-agentic-performance-analystSkill
- wicked-garden-agentic-review-methodologySkill
- wicked-garden-agentic-safety-reviewerSkill
- wicked-garden-agenticSkill
- wicked-garden-agentic-trust-and-safetySkill
- wicked-garden-appsSkill
- wicked-garden-archetypeSkill
- wicked-garden-build-guideSkill
- wicked-garden-classifySkill
- wicked-garden-coreSkill
- wicked-garden-data-engineerSkill
- wicked-garden-deliberateSkill
- wicked-garden-demoSkill
- wicked-garden-domain-coverageSkill
- wicked-garden-domain-extractorSkill
- wicked-garden-domain-modelerSkill
- wicked-garden-domainSkill
- wicked-garden-draftSkill
- wicked-garden-editor-scaffoldSkill
- wicked-garden-engineering-api-documentarianSkill
- wicked-garden-engineering-architectureSkill
- wicked-garden-engineering-backendSkill
- wicked-garden-engineering-debuggingSkill
- wicked-garden-engineering-docsSkill
- wicked-garden-engineering-frontendSkill
- wicked-garden-engineering-integrationSkill
- wicked-garden-engineering-large-scale-migrationSkill
- wicked-garden-engineering-migration-engineerSkill
- wicked-garden-engineering-patchSkill
- wicked-garden-engineeringSkill
- wicked-garden-engineering-solution-architectSkill
- wicked-garden-engineering-system-designSkill
- wicked-garden-engineering-unit-test-qualitySkill
- wicked-garden-governed-workerSkill
- wicked-garden-groundSkill
- wicked-garden-jam-brainstorm-facilitatorSkill
- wicked-garden-jam-councilSkill
- wicked-garden-jamSkill
- wicked-garden-learnSkill
- wicked-garden-mcp-scaffoldSkill
- wicked-garden-mcpSkill
- wicked-garden-mem-captureSkill
- wicked-garden-mem-ingestSkill
- wicked-garden-memSkill
- wicked-garden-personaSkill
- wicked-garden-platform-auditSkill
- wicked-garden-platform-compliance-officerSkill
- wicked-garden-platform-complianceSkill
- wicked-garden-platform-errorsSkill
- wicked-garden-platform-gate-benchmark-rebaselineSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Every sub-action runs inline: parse the arguments, pre-read the data where noted, load the Tier-3 rubric from refs/, apply it, and emit …
- Distinctive: line 37
If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is …
- Distinctive: line 68
Read first rows of the file to capture column names / types / nulls / sample.
- Very specific: line 69
Read refs/analyze.md (relative to this skill's base directory) — the EDA rubric, quality/warehouse/ml modes, insight pattern, and output …
- Distinctive: line 80
Read the data file head/tail to capture columns / types / nulls / sample.
- Very specific: line 81
Read refs/data.md — the profile, validate, and quality rubrics with output formats and quality thresholds.
- Very specific: line 110
Read refs/ml.md — the model review checklist, pipeline design template, deployment readiness checklist, and MLOps standards.
- Very specific: line 123
Read refs/pipeline.md — the design checklist, review rubric with P1/P2/P3 findings, pattern selection, and engineering standards.
- Very specific: line 151
Read refs/shapes.md — what to read (the source's catalog through knowledge.source_catalog, approved shapes, code and rules.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Data Domain — data engineering, analysis, and ML
Every sub-action runs inline: parse the arguments, pre-read the data where noted, load the Tier-3 rubric from refs/, apply it, and emit structured markdown with tables and prioritized findings. For delegated or parallel worker execution, hand off to the wicked-garden-data-engineer worker skill instead.
Hand-off — open the wicked-garden-data-engineer skill with the sub-action and its arguments as the argument; on Claude Code this is the Skill tool, on any other seat open the named skill from your catalog and carry it out inline, then continue here.
Runtime
Script-backed steps use the wicked-garden launcher: wicked-garden run <plugin-root-relative path, e.g. scripts/…> [args]. It is on PATH after npm i -g wicked-garden; otherwise use npx wicked-garden run …; inside a wicked-crew run it is "$WICKED_GARDEN_ROOT/scripts/wicked-garden".
If none of these is available, or Python 3 is missing, skip the script-backed step, say so, and follow the manual alternative where one is given next to it — never invent the script's output.
Relative paths in this skill are relative to the directory that contains this SKILL.md.
Routing
| Sub-action | Use for | Rubric |
analyze <file-path> [--focus stats|quality|warehouse|ml] [--context <file>] [--refresh] [--scenarios] | one-off exploration of a CSV/Excel/data file | refs/analyze.md |
profile <path> | dataset structure + quality profile | refs/data.md |
validate --schema <schema> --data <path> | schema validation | refs/data.md |
quality <path> | quality report (completeness, uniqueness, validity) | refs/data.md |
ml review <path> | ML model review | refs/ml.md |
ml pipeline --type <classification|regression|ranking> | training-pipeline design | refs/ml.md |
pipeline design --source <src> --target <tgt> [--frequency <freq>] | ETL pipeline design | refs/pipeline.md |
pipeline review <path> | ETL pipeline review | refs/pipeline.md |
ontology <file-path> | ontology recommendation for a dataset | inline (§ Ontology) |
shapes <source> | propose a live source's data shapes (joins, describes, governed by) for review | refs/shapes.md |
Detailed templates and examples: refs/analysis-templates.md, refs/ml-templates.md, refs/pipeline-templates.md, refs/data-examples.md.
Analyze — interactive data analysis
Interactive analysis on a CSV/Excel/data file. Use for one-off data
exploration. NOT for schema-level checks (use profile / validate /
quality) or pipeline review (use pipeline review).
- Parse
<file-path>,--focus(stats|quality|warehouse|ml, defaultstats),--context,--refresh,--scenarios. - Read first rows of the file to capture column names / types / nulls / sample.
- Read
refs/analyze.md(relative to this skill's base directory) — the EDA rubric, quality/warehouse/ml modes, insight pattern, and output format. - Apply the rubric directly for the chosen
--focusmode and emit the analysis.
Profile / Validate / Quality — core data engineering ops
Schema-level engineering ops on a dataset. NOT for interactive exploration
(use analyze) or ML pipeline review (use ml).
- Parse the sub-action (profile|validate|quality) and its args (
<path>,--schemafor validate). - Read the data file head/tail to capture columns / types / nulls / sample.
- Read
refs/data.md— the profile, validate, and quality rubrics with output formats and quality thresholds. - Apply the rubric for the requested sub-action and emit structured markdown with tables and prioritized findings.
Optional scripted paths (deterministic profiling/validation):
wicked-garden run scripts/data/data_profiler.py \
--input data.csv --output profile.jsonwicked-garden run scripts/data/schema_validator.py \
--schema schemas/expected.json \
--data data/actual.csvFor files >1GB, use the analyze sub-action for efficient SQL-based profiling
via DuckDB.
ML — model review and training-pipeline design
ML model review and training-pipeline design. NOT for ETL pipeline design
(use pipeline) or data profiling (use profile).
- Parse the sub-action (review|pipeline) and args (
<path>for review,--typefor pipeline). - For
review, read model files at<path>. - Read
refs/ml.md— the model review checklist, pipeline design template, deployment readiness checklist, and MLOps standards. - Apply the rubric for the requested sub-action and emit structured markdown.
Pipeline — data pipeline design and review
Data pipeline design and review. NOT for ML training pipelines (use
ml pipeline) or one-off file analysis (use analyze).
- Parse the sub-action (design|review) and args. For
review, read pipeline files at<path>. Fordesign, capture--source,--target,--frequency. - Read
refs/pipeline.md— the design checklist, review rubric with P1/P2/P3 findings, pattern selection, and engineering standards. - Apply the rubric for the requested sub-action and emit structured markdown.
Ontology — recommend ontologies for a dataset
Sample a dataset (CSV/Excel/Parquet/JSON) and recommend matching public
ontologies (Schema.org, Dublin Core, DCAT, FOAF, GoodRelations, SKOS) or a
custom shape. Use this for ontology mapping. NOT for interactive analysis
(use analyze) or quality reports (use quality).
- Arg parse — extract
file-pathfrom the arguments. Run recommender:
wicked-garden run scripts/_run.py scripts/data/ontology_recommender.py "${file_path}"- Present the script's match table, column-mapping suggestions, and any custom-ontology fallback inline.
Shapes — propose a live source's data shapes for review
What a registered source's tables ARE: what each joins, which code describes it, which rule governs it. Shapes
are PROPOSALS into the one review queue (a person approves each in Understand → Knowledge map), never facts you
print or knowledge you write. NOT for a file on disk (use ontology or profile).
- Read
refs/shapes.md— what to read (the source's catalog throughknowledge.source_catalog, approved shapes, code and rules; never a row), the rules (never a value; never declare deps; your own repo's code) and how to propose. - Build each shape with
wicked-garden run scripts/data/shape_proposal.py <spec.json> --catalog <catalog.json>and send what it prints to the estate shim on stdin (wicked-garden run scripts/_estate_client.py call -). Without the launcher, build the request by hand as the ref shows. - Report how many shapes wait for review, and where.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

