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 natural trigger terms beyond the skill name repeated, no 'when to use' guidance, and nothing to distinguish it from other data or SQL skills. It reads as an auto-generated stub rather than a functional 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'.
Add an explicit 'Use when...' clause with natural trigger terms like 'CTE', 'common table expression', 'WITH clause', 'recursive query', 'SQL subquery refactoring', '.sql files'.
Remove the duplicated trigger term and expand with varied natural language terms users would actually say when needing CTE help, such as 'complex SQL query', 'temporary result set', or 'chained queries'.
| 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 or equivalent 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 text that could apply to any skill, with zero SQL examples, CTE patterns, or actionable guidance. It provides no value beyond what Claude already knows about CTEs.
Suggestions
Add concrete, executable SQL examples showing CTE syntax (basic CTE, recursive CTE, chained CTEs) that Claude can reference and adapt.
Include a workflow for building complex CTE queries step-by-step, such as: identify base query → extract repeated subqueries → convert to CTEs → validate with EXPLAIN.
Replace the generic 'Capabilities' and 'Example Triggers' sections with actual CTE patterns, common pitfalls (e.g., recursive CTE termination), and database-specific syntax differences.
Add references to advanced topics like recursive CTEs, materialized CTEs, or CTE performance considerations in separate linked files if needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'cte query builder' excessively, and provides zero actual technical content about CTEs or SQL query building. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no SQL examples, no CTE syntax, no executable code, no specific commands. The content only describes what the skill claims to do without actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill mentions 'step-by-step guidance' as a capability but provides none. There are no validation checkpoints or sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat list of generic sections with no references to detailed materials, no examples, and no navigation to deeper content. The structure exists but contains no meaningful information to organize. | 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
c8a915c
- 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.