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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill dbt-test-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially just restating the skill name without providing any meaningful information about capabilities or usage triggers. It lacks concrete actions, natural trigger terms, and explicit guidance on when to use the skill. The redundant trigger terms and boilerplate category information provide no value for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates dbt schema tests, generates data quality assertions, writes test YAML configurations for sources and models'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user needs to create dbt tests, add data quality checks, validate schema constraints, or generate test YAML files'
Expand trigger terms to include variations users would naturally say: 'dbt tests', 'schema tests', 'data validation', 'test.yml', 'data quality', 'unique tests', '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 there is no 'Use when...' clause or explicit guidance on when Claude should select this skill. The 'Triggers on' field just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'dbt test creator' repeated twice, which is redundant and doesn't include natural variations users might say like 'dbt tests', 'data tests', 'schema tests', 'test yaml', or 'data quality checks'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'dbt' is a specific tool which provides some distinctiveness, the lack of detail about what kind of tests or what actions are performed could cause confusion with other dbt-related skills or general testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains no concrete information about dbt tests - no syntax, no examples, no commands, no best practices. Every section describes what the skill 'does' in abstract terms without actually doing it.
Suggestions
Add concrete dbt test examples showing schema.yml syntax for generic tests (unique, not_null, accepted_values, relationships)
Include executable code for creating custom singular tests and custom generic tests with actual SQL examples
Provide a clear workflow: 1) identify columns to test, 2) add tests to schema.yml, 3) run `dbt test`, 4) interpret results
Add specific guidance on test selection strategies (which tests for which column types) and common patterns like testing foreign key relationships
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about dbt tests. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific commands, no actual instructions on how to create dbt tests. The content describes what the skill supposedly does without providing any executable or actionable information. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for discovery. There are no references to detailed materials, no links to examples, and no organization beyond generic section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 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.