adding-dbt-unit-test
Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt
Install with Tessl CLI
npx tessl i github:dbt-labs/dbt-agent-skills --skill adding-dbt-unit-test79
Quality
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/adding-dbt-unit-test/SKILL.mdQuality
Discovery
62%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 excels at trigger terms and distinctiveness by clearly targeting dbt unit testing and TDD workflows. However, it fails to specify what concrete actions the skill performs - it only states when to use it, not what capabilities it provides. The description would benefit from listing specific actions like generating test YAML, mocking dependencies, or validating model outputs.
Suggestions
Add specific capabilities before the 'Use when' clause, e.g., 'Generates dbt unit test YAML files, creates mock data for upstream models, validates model output expectations.'
Include concrete actions the skill performs such as 'create test fixtures', 'define expected outputs', or 'configure test schemas' to improve specificity.
| 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 | The description starts with 'Use when' which addresses the 'when' question well, but the 'what' is weak - it only implies the skill adds tests without explaining what specific capabilities it provides (e.g., generating test YAML, creating mock data, validating outputs). | 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 users would naturally use when seeking this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'dbt', 'unit tests', and 'TDD' creates a clear niche that is unlikely to conflict with general testing skills or other dbt skills focused on different aspects like documentation or deployment. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent progressive disclosure and actionable examples. The main weakness is some verbosity in explaining basic concepts (what unit tests are, the comparison table at the end) that Claude already understands. The workflow is clear and the reference structure 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 adds little practical value for executing the skill
| 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 'Similar testing concepts' table at the end adds little value). However, the core content is reasonably efficient with good examples. | 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 covering special cases, warehouse-specific details, and examples. Main content stays focused on core concepts while deferring complexity appropriately. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| 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 | |
- 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.