Individual skill
transform
Use this to author and change a dbt project or a semantic layer: bootstrap a project (`transform init`), write or refactor models from staging to marts, add tests and docs, and define semantic models, entities, dimensions, and metrics in MetricFlow, Apache Ossie or SLayer YAML. Reach for it instead of editing model files by hand whenever a change spans more than one file or must stay consistent with the project: it validates the edit against the real schema, returns a reviewable diff with a plan id, and catches what otherwise fails at `dbt run`, such as wrong columns or broken refs. Bug-fix tickets count: "this model returns wrong numbers, fix it" is a transform task. Also for "build a staging model for this table", "define a revenue metric", "add a dimension to this entity". Warehouse builds are dev-target only, gated, and cost-surfaced first. If you have not verified the source tables' columns or grain, use explore first. For a project that drifted from the warehouse, use maintain.
plugins/exmergo/dex/skills/transform/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,532
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
- writing Derived category
- docs Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 34,802 bytesSKILL.mdcore · 34,802 bytesSKILL.mdcore · 34,802 bytesSKILL.mdcore · 34,802 bytesSKILL.mdcore · 34,802 bytesSKILL.mdcore · 34,802 bytesSKILL.mdcore · 34,802 bytesSKILL.mdcore · 34,802 bytesevals/evals.jsonasset · 13,139 bytesreferences/commands.mddoc · 39,795 bytesreferences/declarations.mddoc · 50,644 bytesreferences/edit-kinds.mddoc · 4,971 bytesreferences/feature-retirement.mddoc · 6,982 bytesreferences/init-and-dev-target.mddoc · 5,511 bytesreferences/macros.mddoc · 2,142 bytesreferences/prerequisite-repairs.mddoc · 5,694 bytesreferences/semantic-layer.mddoc · 16,755 bytesscripts/run.pyruns · 28,333 bytes
Read excerpt
# Transform
Author and refactor the dbt project, both the SQL (staging to marts, tests,
docs) and the semantic layer on top. You write the file content; the engine
validates it, computes the diffs, and stores a plan. Nothing reaches the project
until `transform apply`, and any build runs against a dev target only.
<!-- dex:procedure:begin -->
## Procedure
Dex works in one loop: explore, transform, maintain. `dex <command>` below is
the `dex` CLI; where it is not installed, run the same command through the
skill's `scripts/run.py` wrapper. Each command prints one JSON envelope: read
it and decide the next step from it. Step 1 only reads. Steps 2 to 5 change the