agentleFS
GhostekenGhosteken/agent-harness/skills/dbt-transformation-patterns/SKILL.md

dbt-transformation-patterns

Skill2 starsChanged 42 days agoMITView on GitHub

Production-ready patterns for dbt (data build tool) including model organization, testing strategies, documentation, and incremental processing.

8 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If detailed patterns are required, open resources/implementation-playbook.md.

    line 30
  2. Distinctive:

    Use this skill only when the task clearly matches the scope described above.

    line 37
  3. Distinctive:

    Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

    line 38
  4. Distinctive:

    Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

dbt Transformation Patterns

Production-ready patterns for dbt (data build tool) including model organization, testing strategies, documentation, and incremental processing.

Use this skill when

  • Building data transformation pipelines with dbt
  • Organizing models into staging, intermediate, and marts layers
  • Implementing data quality tests and documentation
  • Creating incremental models for large datasets
  • Setting up dbt project structure and conventions

Do not use this skill when

  • The project is not using dbt or a warehouse-backed workflow
  • You only need ad-hoc SQL queries
  • There is no access to source data or schemas

Instructions

  • Define model layers, naming, and ownership.
  • Implement tests, documentation, and freshness checks.
  • Choose materializations and incremental strategies.
  • Optimize runs with selectors and CI workflows.
  • If detailed patterns are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed dbt patterns and examples.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.