sql-transform-helper
Sql Transform Helper - Auto-activating skill for Data Pipelines. Triggers on: sql transform helper, sql transform helper Part of the Data Pipelines skill category.
33
0%
Does it follow best practices?
Impact
94%
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/sql-transform-helper/SKILL.mdQuality
Discovery
0%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 restates the skill name and category without providing any substantive information about what the skill does or when it should be used. It fails on all dimensions: no concrete actions, no natural trigger terms, no explicit usage guidance, and no distinguishing characteristics.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates SQL transformation queries for data pipelines, including CTEs, window functions, aggregations, and joins across staging tables.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs help writing SQL transforms, building dbt models, creating data pipeline queries, or working with ETL/ELT SQL logic.'
Remove the duplicate trigger term and replace with varied natural keywords users would actually say, such as 'SQL query', 'data transformation', 'dbt model', 'staging table', 'ETL', 'pipeline SQL'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. It only states it is an 'Auto-activating skill for Data Pipelines' without describing what it actually does — no mention of specific SQL operations, transformations, or outputs. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explicit 'Use when...' clause and no description of capabilities beyond the skill name and category. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sql transform helper' repeated twice, which is the skill's own name rather than natural keywords a user would say. Missing terms like 'SQL query', 'data transformation', 'ETL', 'pipeline', 'SELECT', 'JOIN', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic — 'Data Pipelines' and 'sql transform helper' provide almost no distinguishing information. It could easily conflict with any other SQL or data pipeline skill. | 1 / 3 |
Total | 4 / 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 template/placeholder with no actual content. It repeats the phrase 'sql transform helper' without ever defining what it means, providing SQL examples, or giving any actionable guidance. Every section is generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable SQL transform examples (e.g., CTEs for staging transforms, incremental load patterns, SCD Type 2 implementations) with actual SQL code blocks.
Define a clear workflow for building SQL transforms in a pipeline context, such as: write transform → validate with dry run → test with sample data → deploy, with explicit validation steps.
Replace all generic placeholder text ('Provides step-by-step guidance for sql transform helper') with specific, actionable instructions about SQL transform patterns in ETL/ELT pipelines.
Add references to related files or sections for advanced topics like Airflow DAG integration, Spark SQL specifics, or streaming SQL patterns rather than listing them only as tags.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'sql transform helper' excessively, and contains zero domain-specific information or actionable content. | 1 / 3 |
Actionability | There are no concrete code examples, SQL snippets, commands, or specific instructions. Every section is vague and abstract—'Provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined at all. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no validation checkpoints or sequences. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to external files, no structured sections with real content, and no navigation to deeper resources. | 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
c8a915c
- 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.