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.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill sql-patterns96
Does it follow best practices?
Validation for skill structure
Discovery
89%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 solid skill description with excellent trigger term coverage and clear completeness. The main weakness is that it frames itself as a 'reference' without specifying concrete actions (does it generate code? explain concepts? optimize queries?). The explicit 'Triggers on:' clause effectively communicates when to use this skill.
Suggestions
Replace 'Quick reference for' with specific action verbs describing what the skill does, e.g., 'Generates and explains common SQL patterns, CTEs, window functions, and indexing strategies.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SQL) and lists several specific topics (CTEs, window functions, indexing strategies), but doesn't describe concrete actions - it's framed as a 'reference' rather than listing what it actually does (e.g., 'generates CTEs', 'explains window functions'). | 2 / 3 |
Completeness | Answers both what ('Quick reference for common SQL patterns, CTEs, window functions, and indexing strategies') and when ('Triggers on:' followed by explicit trigger terms). The 'Triggers on:' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'sql patterns', 'cte example', 'window functions', 'sql join', 'index strategy', 'pagination sql'. These are realistic phrases developers would use when seeking SQL help. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly focused on SQL-specific patterns with distinct triggers like 'cte example', 'window functions', 'index strategy'. Unlikely to conflict with general coding skills or database administration skills due to the specific SQL pattern focus. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent quick reference skill that maximizes information density while maintaining clarity. It uses tables effectively for comparisons, provides executable code examples, and appropriately defers detailed content to referenced files. The anti-patterns section adds practical value by highlighting common mistakes with fixes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what SQL is or how databases work. Every section is a quick reference table or executable example with no padding. | 3 / 3 |
Actionability | Provides fully executable SQL code examples that are copy-paste ready. The CTE examples, window function queries, and pagination patterns are all concrete and immediately usable. | 3 / 3 |
Workflow Clarity | As a reference skill (not a multi-step process), workflow clarity is appropriately handled. Each pattern is self-contained and unambiguous. The anti-patterns table provides clear problem/solution pairs. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear sections. Appropriately references external files for detailed content (window-functions.md, indexing-strategies.md) with one-level-deep navigation. | 3 / 3 |
Total | 12 / 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.
- 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.