CtrlK
BlogDocsLog inGet started
Tessl Logo

sqlmesh

SQLMesh patterns for data transformation with column-level lineage and virtual environments. Use when building data pipelines that need advanced features like automatic DAG inference and efficient incremental processing.

81

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/devops-data/skills/sqlmesh/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description effectively identifies when to use the skill and targets a specific tool (SQLMesh), making it distinctive. However, it relies on feature descriptions rather than concrete actions, and could benefit from more natural trigger terms that users might actually say when needing SQLMesh help.

Suggestions

Add concrete actions like 'create SQLMesh models', 'define incremental transformations', 'configure virtual data environments' to improve specificity.

Include additional trigger terms users might naturally say, such as 'SQL models', 'data modeling framework', or mentions of SQLMesh-specific concepts like 'audits' or 'macros'.

DimensionReasoningScore

Specificity

Names the domain (SQLMesh, data transformation) and mentions some features (column-level lineage, virtual environments, DAG inference, incremental processing), but doesn't list concrete actions like 'create models', 'define transformations', or 'configure environments'.

2 / 3

Completeness

Clearly answers both what ('SQLMesh patterns for data transformation with column-level lineage and virtual environments') and when ('Use when building data pipelines that need advanced features like automatic DAG inference and efficient incremental processing').

3 / 3

Trigger Term Quality

Includes relevant technical terms like 'SQLMesh', 'data pipelines', 'DAG', 'incremental processing', but missing common user variations like 'SQL models', 'data modeling', 'dbt alternative', or file extensions that users might naturally mention.

2 / 3

Distinctiveness Conflict Risk

SQLMesh is a specific tool with distinct terminology; the combination of 'SQLMesh', 'column-level lineage', and 'virtual environments' creates a clear niche unlikely to conflict with generic SQL or other data pipeline skills.

3 / 3

Total

10

/

12

Passed

Implementation

79%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, concise skill that provides actionable SQLMesh patterns with executable examples. Its main weakness is the lack of an explicit workflow showing how to build and validate a pipeline step-by-step, and it could benefit from progressive disclosure to separate advanced topics like audits and macros into referenced files.

Suggestions

Add an explicit workflow section showing the sequence: create model → validate → plan dev → run audits → plan prod, with validation checkpoints

Include a feedback loop for handling audit failures (e.g., 'If audit fails: review data, fix source, re-run')

Consider splitting advanced topics (audits, macros, seeds) into separate referenced files for better progressive disclosure

DimensionReasoningScore

Conciseness

The skill is lean and efficient, presenting only essential information without explaining concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context.

3 / 3

Actionability

Provides fully executable SQL model definitions, concrete bash commands, and copy-paste ready examples. The model definition and audit examples are complete and specific.

3 / 3

Workflow Clarity

While individual components are clear, there's no explicit workflow sequence for building a pipeline end-to-end. Missing validation checkpoints between steps (e.g., validate model before plan, verify audit results).

2 / 3

Progressive Disclosure

Content is well-organized with clear sections, but everything is inline in one file. For a skill covering multiple features (models, audits, environments), references to detailed docs for advanced topics would improve navigation.

2 / 3

Total

10

/

12

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
jpoutrin/product-forge
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.