CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

90

1.00x
Quality

86%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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.

The description effectively identifies its SQL-focused niche with good trigger terms that cover common user queries. However, it reads more as a topic list than an action-oriented description—it says what it covers but not what it concretely does (e.g., provides examples, generates queries, explains syntax). Adding a 'Use when...' clause and more action-oriented language would strengthen it.

Suggestions

Replace 'Quick reference for' with concrete actions like 'Provides examples and explains common SQL patterns, generates CTEs, demonstrates window functions, and recommends indexing strategies.'

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for SQL examples, needs help writing queries with joins, CTEs, or window functions, or wants indexing/pagination advice.'

DimensionReasoningScore

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

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 is maximally concise while remaining highly actionable. It uses tables effectively for compact reference, provides executable SQL examples for key patterns, and appropriately defers detailed content to referenced files. A model example of a well-crafted reference skill.

DimensionReasoningScore

Conciseness

Extremely lean and efficient. Uses tables for quick reference, minimal prose, no unnecessary explanations of what SQL is or how databases work. Every token serves a purpose as a reference card.

3 / 3

Actionability

All SQL examples are fully executable and copy-paste ready. The CTE, window function, and pagination examples are concrete and complete. The anti-patterns table provides specific fixes alongside each mistake.

3 / 3

Workflow Clarity

This is a reference/pattern skill rather than a multi-step workflow skill. The single-purpose patterns are each unambiguous and clearly presented. No destructive or batch operations require validation checkpoints.

3 / 3

Progressive Disclosure

Clean overview with well-organized sections covering the essentials, then clearly signaled one-level-deep references to detailed materials (window-functions.md, indexing-strategies.md) for deeper dives.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
NeverSight/skills_feed
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.