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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cte-query-builderActivation
7%This is a minimal, auto-generated description that provides almost no useful information for skill selection. It lacks any explanation of what CTE queries are, what the skill does with them, or when Claude should use it. The repeated trigger term and boilerplate format suggest this was not manually crafted.
Suggestions
Add specific actions the skill performs, e.g., 'Builds Common Table Expression (CTE) queries for complex SQL operations, including recursive queries, data transformation chains, and hierarchical data traversal.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about CTEs, WITH clauses, recursive SQL, chaining queries, or building complex multi-step SQL queries.'
Add variations of terminology users might use: 'common table expression', 'WITH clause', 'recursive query', 'SQL subquery organization', 'query refactoring'.
| 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 explicit 'when to use' guidance. The auto-generated format provides no meaningful information about capabilities or use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'cte query builder' repeated twice. Missing natural variations users would say like 'common table expression', 'WITH clause', 'recursive query', 'SQL CTE', or 'nested query'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'CTE' is somewhat specific to SQL query building, the vague 'Data Analytics' category and lack of detail could cause overlap with other SQL or query-related skills. The specific term 'CTE' provides some distinction. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is a hollow template with no actual instructional content. It describes capabilities in abstract terms but provides zero concrete guidance on CTE query building - no SQL syntax, no examples, no patterns, no common use cases. The content fails to teach Claude anything it doesn't already know about CTEs.
Suggestions
Add concrete CTE syntax examples with executable SQL code (e.g., recursive vs non-recursive CTEs, chaining multiple CTEs)
Include specific use case patterns like hierarchical data queries, running totals, or deduplication with row_number()
Provide a workflow for building complex CTE queries: start simple, validate intermediate results, then compose
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual technical content
| 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 vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance - no SQL examples, no CTE syntax, no actual code or commands. The skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or validation checkpoints for building CTE queries. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there are no references to detailed materials, examples, or advanced documentation. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%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
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.