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
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 extremely minimal and essentially just restates the skill name without providing any useful information about capabilities, use cases, or trigger conditions. It reads as auto-generated boilerplate rather than a crafted description. It would be nearly impossible for Claude to make an informed decision about when to select this skill over others.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates dbt schema tests, creates custom data quality checks, writes test YAML configurations for dbt models'.
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about dbt tests, data validation, schema testing, model quality checks, or generating .yml test files'.
Remove the duplicate trigger term 'dbt test creator' and replace with varied natural language terms users would actually say, such as 'dbt testing', 'data quality tests', 'schema.yml', 'test coverage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It says 'Dbt Test Creator' but never explains what it actually does—no mention of creating tests, validating schemas, generating YAML, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'dbt test creator' repeated twice. It lacks natural keywords users would say like 'dbt tests', 'schema tests', 'data quality', 'dbt YAML', 'model testing', or 'data validation'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'dbt' and 'test creator' provides some domain specificity that distinguishes it from generic data skills, but the lack of detail about what kind of tests or how it differs from other dbt-related skills creates potential overlap. | 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 is an empty placeholder with no actionable content. It repeatedly names 'dbt test creator' without ever explaining what dbt tests are, how to write them, or providing any code, YAML examples, or workflows. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable examples of dbt test YAML (e.g., schema.yml with `not_null`, `unique`, `accepted_values`, and custom tests) so Claude knows exactly what to generate.
Provide a clear multi-step workflow: 1) identify model to test, 2) write schema tests in YAML, 3) run `dbt test` to validate, 4) review failures and iterate.
Remove all boilerplate sections ('Purpose', 'When to Use', 'Example Triggers', 'Capabilities') that contain no substantive information and replace with actual dbt test creation guidance.
Include examples of custom singular tests and generic tests with Jinja, and reference any advanced patterns in separate bundle files for progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'dbt test creator' excessively, and provides zero substantive information about how to actually create dbt tests. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no examples of dbt test YAML, no schema test patterns, no specific instructions. It only describes what the skill would do in abstract terms without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow steps are provided. There is no sequence, no validation, and no process for creating dbt tests. The bullet 'Validates outputs against common standards' is a vague claim with no supporting detail. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to supporting files, no structured navigation, and no bundle files to support it. There is nothing to progressively disclose. | 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
ba8561d
- 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.