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.
34
0%
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
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 extremely weak across all dimensions. It provides no concrete actions, no meaningful trigger terms beyond the skill name repeated, no 'Use when' guidance, and nothing to distinguish it from other data or SQL-related skills. It reads as an auto-generated stub rather than a useful skill description.
Suggestions
Add specific concrete actions such as 'Builds SQL Common Table Expressions (CTEs), constructs recursive queries, refactors nested subqueries into readable WITH clauses, and optimizes multi-step SQL logic.'
Add an explicit 'Use when...' clause with natural trigger terms: 'Use when the user asks about CTEs, common table expressions, WITH clauses, recursive queries, SQL refactoring, or breaking complex queries into steps.'
Remove the duplicate trigger term and expand with natural variations users would actually say, such as 'CTE', 'common table expression', 'WITH query', 'recursive SQL', 'subquery refactor', '.sql'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Cte Query Builder') and its category ('Data Analytics') but provides no concrete actions like 'builds common table expressions', 'constructs recursive queries', or 'generates SQL CTEs'. It is entirely vague about 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 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'cte query builder' repeated twice. It misses natural user terms like 'CTE', 'common table expression', 'WITH clause', 'recursive query', 'SQL subquery', or 'nested query'. Users rarely say 'cte query builder' verbatim. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic ('Data Analytics' category, no specific actions) that it could easily conflict with any SQL, database, or analytics skill. Nothing distinguishes it clearly from other query-building or data analytics 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 about CTE query building. It contains only generic boilerplate descriptions and trigger phrases but provides zero actionable guidance, no SQL examples, no CTE patterns, and no domain-specific knowledge. It fails on every dimension because it teaches Claude nothing it doesn't already know.
Suggestions
Add concrete, executable SQL examples showing CTE syntax (WITH clauses), including recursive CTEs, chained CTEs, and common patterns like hierarchical queries or running totals.
Provide a clear workflow for building CTEs step-by-step: identify the subqueries, structure the WITH clause, chain multiple CTEs, validate the output, and optimize performance.
Remove all generic boilerplate sections (When to Use, Example Triggers, Capabilities) and replace with actual CTE-specific content such as syntax patterns, common pitfalls, and performance considerations.
Add concrete examples with input data and expected output to illustrate different CTE use cases (e.g., recursive hierarchy traversal, deduplication, window function alternatives).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, contains no domain-specific information about CTE queries, and every section is generic placeholder text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no SQL examples, no CTE syntax, no executable code, no specific commands. The content only describes what the skill supposedly does in vague, abstract terms without actually teaching anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no instructions for building CTE queries, no validation checkpoints, and no sequenced operations. The 'step-by-step guidance' mentioned in Capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful organization of CTE-related content. There are no bundle files to support it either. | 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.