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 with no substantive content. It fails to describe any concrete capabilities, lacks natural trigger terms users would use, provides no 'when to use' guidance, and is indistinguishable from any other SQL or data-related skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates SQL transformation queries for data pipelines, creates staging table definitions, writes incremental load logic, and builds dbt-style models.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about SQL transformations, data pipeline queries, ETL logic, staging tables, dbt models, or data warehouse transformations.'
Remove the duplicate trigger term and replace with varied natural keywords users would actually say, such as 'SQL query', 'data transformation', 'ETL', 'pipeline SQL', 'transform query', '.sql files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it is an 'Auto-activating skill for Data Pipelines' without describing what it actually does — no verbs like 'transforms', 'generates', 'validates', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause with trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sql transform helper' repeated twice. These are not natural keywords a user would say; users would more likely say 'SQL query', 'data transformation', 'ETL', 'SQL pipeline', 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 a hollow template with no actual content. It contains no SQL examples, no transformation patterns, no ETL guidance, no tool-specific instructions, and no actionable information of any kind. It merely restates the skill name in various phrasings without teaching Claude anything useful.
Suggestions
Add concrete, executable SQL transform examples (e.g., CTE patterns, window functions for data pipelines, incremental load queries) with specific input/output illustrations.
Include a clear multi-step workflow for a typical SQL transform task, such as: define source query → apply transformations → validate row counts → write to target, with explicit validation checkpoints.
Provide tool-specific guidance for at least one pipeline framework (e.g., Airflow SQLOperator, dbt model patterns, or Spark SQL) with copy-paste-ready code.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that contain no substantive information and replace them with actual technical content.
| 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 or actionable information. Every token is wasted. | 1 / 3 |
Actionability | There are no concrete code examples, SQL snippets, commands, configurations, or specific instructions. The content is entirely abstract and descriptive, offering no executable guidance whatsoever. | 1 / 3 |
Workflow Clarity | No workflow steps, sequences, or validation checkpoints are provided. The skill claims to provide 'step-by-step guidance' but contains none. There is no process to follow. | 1 / 3 |
Progressive Disclosure | No references to external files, no structured navigation, and no meaningful content organization. The sections are superficial headers over empty platitudes with no bundle files to support them. | 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
3a2d27d
- 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.