dbt-test-creator
Dbt Test Creator - Auto-activating skill for Data Pipelines. Triggers on: dbt test creator, dbt test creator Part of the Data Pipelines skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/11-data-pipelines/dbt-test-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is severely underdeveloped, essentially just restating the skill name without explaining what it actually does or when to use it. It lacks concrete actions, meaningful trigger terms, and any guidance for skill selection. The duplicate trigger term suggests this may be auto-generated boilerplate that was never properly filled in.
Suggestions
Add specific capabilities: 'Creates dbt schema tests, generates data quality assertions, writes test YAML configurations for models'
Add a 'Use when...' clause: 'Use when the user needs to create dbt tests, add data quality checks, validate model outputs, or mentions schema.yml testing'
Include natural trigger term variations: 'dbt tests', 'schema tests', 'data quality', 'test yaml', 'model validation', 'unique/not_null tests'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Dbt Test Creator' without describing any concrete actions. There are no specific capabilities listed like 'creates schema tests', 'generates data quality checks', or 'writes test YAML files'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('dbt test creator, dbt test creator') and miss natural variations users would say like 'dbt tests', 'data tests', 'schema tests', 'test yaml', or 'data quality checks'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'dbt' provides some specificity to the data engineering domain, but 'Data Pipelines' category is broad and could overlap with other dbt-related skills or general data pipeline tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is essentially a placeholder template with no substantive guidance. It describes capabilities in abstract terms but provides zero actionable information about dbt tests - no syntax, no examples, no actual test patterns, and no workflow for creating tests. The content fails on all dimensions by being verbose yet empty of useful instruction.
Suggestions
Add concrete dbt test examples showing schema.yml test definitions (e.g., unique, not_null, accepted_values, relationships tests)
Include executable code snippets for custom generic tests and singular tests with actual SQL
Define a clear workflow: 1) identify column to test, 2) add test to schema.yml, 3) run `dbt test --select model_name`, 4) interpret results
Remove all generic boilerplate text and replace with specific dbt testing patterns and anti-patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'automated assistance' and 'industry best practices' are vague filler that Claude already understands conceptually. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual dbt test syntax or patterns. The skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps. There are no validation checkpoints or sequences for creating dbt tests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of marketing-style text with no structure for actual learning. No references to detailed materials, examples, or related documentation are provided. | 1 / 3 |
Total | 4 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.