sql-patterns
Quick reference for common SQL patterns, CTEs, window functions, and indexing strategies. Triggers on: sql patterns, cte example, window functions, sql join, index strategy, pagination sql.
88
82%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
72%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 is a decent skill description that clearly identifies its SQL-focused domain and provides useful trigger terms. Its main weaknesses are the lack of concrete action verbs describing what the skill actually does (beyond being a 'quick reference') and the absence of a proper 'Use when...' clause that explains the selection context. The trigger terms are well-chosen and cover natural user language.
Suggestions
Replace 'Quick reference for' with specific actions like 'Generates and explains common SQL patterns, writes CTEs, demonstrates window functions, and recommends indexing strategies.'
Add a 'Use when...' clause such as 'Use when the user asks for SQL examples, needs help writing queries with joins or CTEs, or wants advice on database indexing and pagination.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SQL) and lists several specific topics (CTEs, window functions, indexing strategies), but describes itself as a 'quick reference' rather than listing concrete actions it performs. It doesn't specify what it does with these topics (e.g., 'generates CTEs', 'explains window functions'). | 2 / 3 |
Completeness | The 'what' is partially addressed (quick reference for SQL patterns), and while 'Triggers on:' provides explicit trigger terms, it lacks a proper 'Use when...' clause explaining the circumstances for selection. The trigger list partially compensates but doesn't fully articulate when to use this skill. | 2 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms that users would actually say: 'sql patterns', 'cte example', 'window functions', 'sql join', 'index strategy', 'pagination sql'. These cover common variations of SQL-related queries. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around SQL patterns and specific SQL concepts (CTEs, window functions, joins, indexing, pagination). The trigger terms are specific enough to avoid conflicting with general coding or database administration skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong quick-reference skill that is concise, actionable, and well-structured. The tables and executable SQL examples are excellent for a pattern reference. The main weakness is that the referenced bundle files (window-functions.md, indexing-strategies.md) don't exist, undermining the progressive disclosure strategy.
Suggestions
Create the referenced files `./references/window-functions.md` and `./references/indexing-strategies.md` to support the progressive disclosure structure, or remove the references if they won't be provided.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every section is a quick-reference table or minimal executable SQL example. No unnecessary explanations of what SQL is or how databases work—assumes Claude's competence throughout. | 3 / 3 |
Actionability | All SQL examples are fully executable and copy-paste ready. The CTE examples, window function query, and pagination patterns are concrete and complete. The anti-patterns table provides specific fixes rather than vague advice. | 3 / 3 |
Workflow Clarity | This is a reference/pattern skill rather than a multi-step workflow skill. For its purpose, the content is clearly sequenced from basic CTEs to chained CTEs, and pagination shows progression from simple to scalable approaches. No destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | References to `./references/window-functions.md` and `./references/indexing-strategies.md` are well-signaled and one level deep, but no bundle files were provided, meaning these references are broken. The inline content is well-organized but the referenced files don't exist to support the disclosure structure. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
3ae408c
- 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.