dbt-transformation-patterns

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/dbt-transformation-patterns/SKILL.md

The canonical home for this skill is dbt-transformation-patterns in rmyndharis/antigravity-skills

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is exceptionally concise and well-structured with appropriate progressive disclosure intent, but its actionability and workflow clarity are limited by directive-only guidance lacking executable detail and validation steps, and its lone resource reference points to a missing file.

Suggestions

Add the missing 'resources/implementation-playbook.md' file (or fix the path) so the referenced detailed patterns are actually reachable.

Include a concrete, executable example for at least one instruction (e.g., a sample dbt model YAML with tests, or a `dbt run --select` selector command) to lift actionability.

Add an explicit validation/checkpoint step for incremental and CI workflows (e.g., 'Run `dbt test` before promoting') to satisfy the workflow-clarity validation requirement.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no over-explanation of concepts Claude already knows; every section earns its place and it assumes Claude's competence.	5 / 5
Actionability	The instructions are concrete in topic ('Define model layers, naming, and ownership', 'Choose materializations and incremental strategies') but stop at directive bullets without executable code or specific commands, leaving guidance incomplete.	3 / 5
Workflow Clarity	A five-step directive sequence is present and ordered, but there are no validation checkpoints; given batch/destructive-adjacent contexts (incremental runs, CI workflows) the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Structure is clean with a clearly signaled one-level-deep reference, but the referenced 'resources/implementation-playbook.md' does not exist in the bundle, so the navigation target is broken.	3 / 5
	Total	14 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, naming the dbt domain and four concrete capability areas with natural trigger terms. It is held back by the absence of an explicit 'Use when' trigger clause in the description field itself.

Suggestions

Append a 'Use when...' trigger clause to the description field (e.g., 'Use when building or refactoring dbt projects, organizing models into layers, or setting up incremental processing') to raise completeness.

Add common synonyms like 'data warehouse' or '.sql model files' to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Quotes "model organization, testing strategies, documentation, and incremental processing" — names the dbt domain and lists several specific action areas, but stops short of fully enumerating concrete actions per area.	4 / 5
Completeness	The description gives a clear "what" but no "Use when..." trigger clause; per the rubric, a missing explicit trigger guidance caps completeness at 3 even though the body later supplies 'Use this skill when'.	3 / 5
Trigger Term Quality	Includes natural dbt-specific terms like "dbt (data build tool)", "staging, intermediate, and marts layers", and "incremental models"; good coverage but missing common synonyms such as "data warehouse" or file extensions.	4 / 5
Distinctiveness Conflict Risk	The dbt-specific niche with distinct triggers ("dbt", "marts layers", "incremental models") is clearly distinguishable from other skills with minimal conflict risk.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/dbt-transformation-patterns/SKILL.md
Commit: 57c135b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.