adding-dbt-unit-test
tessl i github:dbt-labs/dbt-agent-skills --skill adding-dbt-unit-testUse when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
85%This is a well-structured skill with excellent progressive disclosure and actionable examples. The main weakness is some verbosity in explanatory sections that could be trimmed (the 'What are unit tests' intro and the comparison table at the end). The workflow is clear and the reference architecture is exemplary.
Suggestions
Remove or significantly condense the 'What are unit tests in dbt' section - Claude understands the concept of unit testing
Remove the 'Similar testing concepts' comparison table at the end - it's tangential and doesn't help Claude write better unit tests
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., 'What are unit tests in dbt' section explains concepts Claude likely knows, the comparison table at the end with Hoare triple/Gherkin is tangential). However, the core workflow and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable YAML examples, concrete shell commands for running tests, and copy-paste ready code snippets. The minimal and realistic examples are complete and actionable. | 3 / 3 |
Workflow Clarity | Clear 3-step workflow (choose model, mock inputs, mock outputs) with explicit validation via test execution. The 'When a unit test fails' section provides feedback loop guidance, and the --empty flag section addresses dependency validation. | 3 / 3 |
Progressive Disclosure | Excellent structure with a comprehensive 'Additional Resources' section at the top linking to 12 reference files for special cases, data types, and warehouse-specific details. Main content stays focused on core workflow while deferring complexity appropriately. | 3 / 3 |
Total | 11 / 12 Passed |
Activation
63%The description excels at trigger terms and distinctiveness, making it easy for Claude to identify when this skill is needed. However, it critically lacks specificity about what the skill actually does - it tells Claude when to use it but not what capabilities it provides. This is essentially a 'Use when' clause without the preceding capability description.
Suggestions
Add specific capabilities before the 'Use when' clause, such as: 'Creates dbt unit test YAML files, mocks upstream model data, validates model logic and transformations.'
Include concrete actions the skill performs like 'generate test fixtures', 'write assertions for model outputs', or 'scaffold test configurations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('adding unit tests') without specifying concrete actions like 'create test YAML files', 'validate model outputs', or 'mock upstream dependencies'. It names the domain (dbt) but lacks specific capabilities. | 1 / 3 |
Completeness | Has a 'Use when...' clause addressing when to use it, but the 'what does this do' portion is essentially absent. The description only implies the capability through the trigger context without explicitly stating what actions the skill performs. | 2 / 3 |
Trigger Term Quality | Contains strong natural trigger terms users would say: 'unit tests', 'dbt model', 'test-driven development', 'TDD', and 'dbt'. These are terms a user would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'dbt', 'unit tests', and 'TDD' creates a clear niche that is unlikely to conflict with other skills. This is specific to dbt testing workflows and wouldn't overlap with general testing or general dbt skills. | 3 / 3 |
Total | 9 / 12 Passed |
Reviewed
Table of Contents
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.