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
Quality
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 is a minimally viable skill description that provides almost no useful information for skill selection. It consists only of boilerplate metadata (name, category, repeated trigger term) without any actual description of capabilities, use cases, or natural trigger terms. Claude would have no basis to select this skill appropriately from a collection of data-related skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Converts SQL queries between dialects, optimizes transform logic, generates dbt models from raw SQL'
Include a 'Use when...' clause with natural trigger terms like 'SQL transformation', 'convert query', 'dbt', 'data pipeline SQL', 'ETL query'
Specify the distinct niche this skill fills compared to general SQL or data pipeline skills, such as specific frameworks (dbt, Airflow) or transformation types it handles
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Sql Transform Helper' and category 'Data Pipelines'. There are no specific capabilities listed like 'converts queries', 'optimizes joins', or 'transforms schemas'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sql transform helper' repeated twice, which is the skill name itself rather than natural user language. Users would more likely say 'convert SQL', 'transform query', 'data pipeline', or 'ETL'. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'Data Pipelines' could overlap with many skills involving databases, ETL, data processing, or SQL. Without specific triggers or capabilities, it would be impossible to distinguish from other data-related skills. | 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 with no actual content. It contains only generic boilerplate text that describes what a skill should do without providing any concrete SQL transform guidance, code examples, or actionable instructions. The skill fails on all dimensions as it teaches Claude nothing about SQL transforms.
Suggestions
Add concrete SQL transform examples with executable code (e.g., CTEs, window functions, data type conversions, aggregations)
Include specific patterns for common transform scenarios like deduplication, pivoting, or incremental loads
Provide a clear workflow for building and validating SQL transforms (e.g., test with sample data -> validate output schema -> deploy)
Remove all generic boilerplate text and replace with actual technical content that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are empty filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no SQL patterns, no actual instructions for SQL transforms. The entire content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for SQL transform tasks. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, examples, or related files. The content is a shallow placeholder with no depth or navigation to actual 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
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.