dbt-model-generator
Dbt Model Generator - Auto-activating skill for Data Pipelines. Triggers on: dbt model generator, dbt model generator Part of the Data Pipelines skill category.
36
Quality
3%
Does it follow best practices?
Impact
97%
0.98xAverage 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-model-generator/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 essentially a placeholder that relies entirely on the skill name rather than providing actionable guidance. It lacks concrete capability descriptions, meaningful trigger terms, and explicit usage scenarios. Claude would struggle to confidently select this skill over others in a large skill library.
Suggestions
Add specific capabilities: 'Generates dbt SQL models including staging, intermediate, and mart layers. Creates schema.yml files with column descriptions and tests.'
Include a 'Use when...' clause with natural triggers: 'Use when the user asks to create dbt models, write data transformations, set up staging tables, or work with dbt projects.'
Add file type and keyword variations: 'dbt, data build tool, SQL models, .sql, schema.yml, sources, refs, data transformation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Dbt Model Generator' without describing any concrete actions. It doesn't explain what generating a dbt model entails - no mention of SQL transformations, schema definitions, YAML configs, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' guidance is just a category label ('Data Pipelines') rather than explicit trigger scenarios. No 'Use when...' clause is present. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('dbt model generator' listed twice) and overly narrow. Missing natural variations users might say like 'create dbt model', 'dbt transformation', 'data modeling', 'staging model', 'mart', or 'dbt SQL'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'dbt' provides some specificity that distinguishes it from generic data skills, but 'Data Pipelines' category is broad and could overlap with ETL, Airflow, or other pipeline-related skills. | 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 essentially a placeholder template with no substantive content. It describes what a dbt model generator skill would do without providing any actual guidance, code, or instructions. The content fails on all dimensions by being verbose about nothing while providing zero actionable information.
Suggestions
Add concrete dbt model code examples showing staging, intermediate, and mart model patterns with actual SQL/Jinja2 syntax
Include a step-by-step workflow for generating models: source definition → staging model → transformations → testing → documentation
Provide specific dbt commands (e.g., `dbt run --select model_name`, `dbt test`) and schema.yml configuration examples
Remove all generic boilerplate sections ('Purpose', 'When to Use', 'Example Triggers') and replace with actionable content
| 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. The entire skill explains what it does without actually doing anything. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no commands, and no actual instructions for generating dbt models. The content only describes capabilities abstractly without providing any executable or actionable information. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains no actual steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples or documentation, and no organization beyond generic section headers. | 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.