cte-query-builder
Cte Query Builder - Auto-activating skill for Data Analytics. Triggers on: cte query builder, cte query builder Part of the Data Analytics skill category.
36
Quality
3%
Does it follow best practices?
Impact
98%
1.05xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/cte-query-builder/SKILL.mdQuality
Discovery
7%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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or usage triggers. It provides no actionable information for Claude to determine when to select this skill over others. The repeated trigger term and lack of natural language variations make it unlikely to match user requests effectively.
Suggestions
Add specific actions the skill performs, e.g., 'Builds Common Table Expressions (CTEs) for complex SQL queries, structures recursive queries, and organizes multi-step data transformations.'
Add a 'Use when...' clause with explicit triggers like 'Use when the user needs help with CTEs, WITH clauses, recursive queries, or structuring complex SQL statements.'
Include natural trigger term variations users would say: 'CTE', 'common table expression', 'WITH clause', 'recursive SQL', 'nested queries', 'SQL subqueries'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool 'Cte Query Builder' and mentions 'Data Analytics' but provides no concrete actions. It doesn't explain what the skill actually does (e.g., 'builds CTEs', 'generates SQL queries', 'structures complex queries'). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'cte query builder' repeated twice. Missing natural variations users would say like 'CTE', 'common table expression', 'SQL query', 'recursive query', 'WITH clause', or 'subquery'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'CTE Query Builder' is somewhat specific to a SQL concept, the lack of detail about what it does and the generic 'Data Analytics' category could cause overlap with other SQL or analytics skills. | 2 / 3 |
Total | 5 / 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 entirely meta-content describing what the skill should do rather than actually teaching CTE query building. It contains no SQL syntax, no CTE examples, no patterns, and no actionable guidance. The content is a placeholder template that would provide zero value to Claude when attempting to help users with CTE queries.
Suggestions
Add concrete CTE query examples with executable SQL code showing basic, recursive, and chained CTE patterns
Include a workflow for building CTEs: identify subqueries, extract to CTEs, validate query equivalence
Remove all meta-description content (triggers, capabilities, example triggers) and replace with actual CTE syntax and best practices
Add common CTE use cases with before/after examples showing how to refactor complex queries into readable CTEs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. It explains what triggers the skill and describes capabilities in vague terms without any concrete CTE query building information. | 1 / 3 |
Actionability | No concrete code, SQL examples, or executable guidance is provided. The skill describes rather than instructs - there are no actual CTE query patterns, syntax examples, or copy-paste ready SQL. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for building CTE queries. No validation or process is described. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed materials, examples, or related documentation. | 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.