CtrlK

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.

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill sql-transform-helper

What are skills?

Overall
score

17%

Review — 0%

Does it follow best practices?

Validation — 11 / 16 Passed

Validation for skill structure

SKILL.md

Review

Evals

Activation

This description is severely lacking across all dimensions. It provides only a skill name, a redundant trigger phrase, and a category label without any explanation of what the skill does, what specific capabilities it offers, or when it should be used. This would be nearly impossible for Claude to correctly select from a pool of skills.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Generates SQL transformation queries, converts data between formats, creates ETL pipeline scripts')

Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs help with SQL transformations, data pipeline queries, ETL logic, or converting data formats')

Add natural keywords users might mention such as 'SQL', 'query', 'transform', 'ETL', 'data conversion', 'pipeline', 'database'

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions - only the name 'Sql Transform Helper' and category 'Data Pipelines'. There is no explanation of what the skill actually does.	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 usage guidance beyond the redundant trigger phrase.	1 / 3
Trigger Term Quality	The only trigger terms listed are 'sql transform helper' repeated twice, which is the skill name itself. No natural user keywords like 'SQL query', 'data transformation', 'ETL', or 'database' are included.	1 / 3
Distinctiveness Conflict Risk	The generic 'Data Pipelines' category and lack of specific capabilities make this highly prone to conflicts. Without concrete actions or distinct triggers, it's indistinguishable from other data-related skills.	1 / 3
	Total	4 / 12 Passed

Implementation

This skill content is essentially a placeholder template with no substantive guidance. It contains only meta-descriptions of what a skill should do without any actual SQL transformation instructions, code examples, or concrete workflows. The content fails to teach Claude anything actionable about SQL transforms in data pipelines.

Suggestions

Add concrete, executable SQL examples showing common transform patterns (e.g., CTEs, window functions, aggregations) with actual code blocks

Define a clear workflow for SQL transform tasks: analyze source schema → write transform → validate output → handle errors

Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific techniques for ETL/Spark/Airflow SQL transforms

Include specific tool integration examples (e.g., how to use SQL transforms in Airflow DAGs or Spark SQL) with copy-paste ready code

Dimension	Reasoning	Score
Conciseness	The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need.	1 / 3
Actionability	There is zero concrete guidance - no SQL examples, no code, no specific commands, no actual instructions on how to perform any SQL transform task. The content only describes what the skill claims to do without showing how.	1 / 3
Workflow Clarity	No workflow is defined at all. Despite claiming to provide 'step-by-step guidance,' there are no actual steps, sequences, or validation checkpoints for any SQL transformation process.	1 / 3
Progressive Disclosure	The content is a monolithic block of vague descriptions with no structure for discovery. No references to detailed documentation, examples, or related resources are provided despite mentioning 'Related Skills.'	1 / 3
	Total	4 / 12 Passed

Validation

69%

Warnings & errors only

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: 23 days ago

Table of Contents

Activation Implementation Validation

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.