dbt-transformation-patterns

Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.

Quality

75%

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 ./skills/dbt-transformation-patterns/SKILL.md

Quality

Content

50%

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

The body is well-organized and token-efficient but offers only abstract directives with no executable code or concrete examples, and its single detailed reference points to a file that is absent from the bundle. The most impactful fixes target actionability and the broken reference.

Suggestions

Add concrete, executable guidance — e.g. a minimal staging/marts model SQL snippet, a `dbt build --select` selector example, and an incremental model config block — so the instructions are copy-paste ready rather than abstract directives.

Create the referenced `resources/implementation-playbook.md` (or correct the path to an existing file) so the progressive-disclosure link resolves.

Turn the instruction bullets into an explicit sequenced dbt workflow with validation checkpoints (e.g. `dbt test` after model definition, re-run on failure before promoting to marts).

Dimension	Reasoning	Score
Conciseness	The body is lean — short bulleted sections with no padding or re-explanation of what dbt is — so every token earns its place and it assumes Claude's competence, matching the lean-and-efficient anchor.	3 / 3
Actionability	Instructions are abstract directives ("Define model layers, naming, and ownership", "Choose materializations and incremental strategies") with no concrete code, commands, SQL, or copy-paste examples, matching the describes-rather-than-instructs anchor; it is not merely incomplete pseudocode, so it does not reach 2.	1 / 3
Workflow Clarity	The bullets list dbt concerns in a rough order (layers → tests → materializations → optimize) but they are parallel categories rather than a sequenced process, and there are no validation checkpoints or feedback loops for risky operations like incremental materializations, capping it at the listed-but-gaps anchor.	2 / 3
Progressive Disclosure	A clearly signaled one-level reference to `resources/implementation-playbook.md` is present, but that file does not exist in the bundle, so navigation to the detailed material is broken — structure and signaling are good but the referenced path is missing, which stops it reaching the clear-navigation anchor.	2 / 3
	Total	8 / 12 Passed

Description

100%

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 concise and strong: it names concrete capabilities, gives natural use-when triggers, and occupies a clear, distinctive niche. Third-person imperative voice is used correctly throughout.

Dimension	Reasoning	Score
Specificity	The description enumerates concrete capability areas — "model organization, testing, documentation, and incremental strategies" — naming multiple specific actions rather than vague abstraction, matching the score-3 anchor that lists several concrete capabilities.	3 / 3
Completeness	It states both what the skill does ("Master dbt ... with model organization, testing, documentation, and incremental strategies") and when to use it via an explicit "Use when ..." trigger, satisfying the both what-and-when anchor.	3 / 3
Trigger Term Quality	The "Use when building data transformations, creating data models, or implementing analytics engineering best practices" clause supplies natural phrases a user would actually say, giving good coverage of common dbt/analytics-engineering vocabulary.	3 / 3
Distinctiveness Conflict Risk	The dbt/analytics-engineering niche with distinctive triggers (dbt, data models, analytics engineering) is unlikely to collide with other skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/dbt-transformation-patterns/SKILL.md
Commit: e63f7dd

Reviewed: about 4 hours 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.