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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill dbt-model-generatorOverall
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 explaining capabilities or providing meaningful trigger guidance. It lacks concrete actions (what dbt models it can create, what transformations it supports), natural user keywords, and explicit 'Use when' scenarios that would help Claude select this skill appropriately.
Suggestions
Add specific capabilities like 'Creates dbt staging models, intermediate models, and mart models with proper naming conventions, documentation blocks, and tests'
Include a 'Use when...' clause with natural trigger terms: 'Use when user asks to create dbt models, write data transformations, build staging layers, or mentions dbt, data warehouse modeling, or ELT pipelines'
Add file type and technology keywords users might mention: '.sql files', 'Snowflake', 'BigQuery', 'data warehouse', 'source tables', 'ref() function'
| 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 or what specific capabilities are provided. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a repetition of the skill name rather than meaningful trigger scenarios. No 'Use when...' clause with explicit triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('dbt model generator' listed twice) and overly specific. Missing natural variations users might say like 'create dbt model', 'dbt sql', 'data transformation', 'staging model', or 'mart model'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'dbt' and 'Data Pipelines' provides some specificity to distinguish from general code or document skills, but without concrete actions described, it could still conflict with other data engineering or SQL-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual instructional content. It describes what a dbt model generator skill would do without providing any concrete guidance, code examples, or workflows. The entire content is meta-description about the skill rather than actionable instructions for generating dbt models.
Suggestions
Add concrete dbt model code examples showing staging, intermediate, and mart model patterns with actual SQL and YAML configuration
Include a step-by-step workflow for generating models: source definition → staging model → transformations → tests → documentation
Provide executable dbt commands (dbt run, dbt test, dbt docs generate) with validation checkpoints
Remove all meta-description sections ('Purpose', 'When to Use', 'Capabilities', 'Example Triggers') and replace with actual technical content
| 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 model generation. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no SQL/YAML snippets, no actual dbt commands, no model patterns. The skill describes what it claims to do rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps for generating dbt models, no validation checkpoints, and no sequence of operations. The 'step-by-step guidance' mentioned is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual content to organize. There are no references to detailed materials, no links to examples or templates, and no structured navigation to deeper resources. | 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.