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.

97

1.00x
Quality

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

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, actionable SQL reference with executable examples and no unnecessary explanation. Its only real weakness is that the two referenced deeper-dive files are absent, leaving the progressive-disclosure pointers broken.

Suggestions

Create the missing ./references/window-functions.md and ./references/indexing-strategies.md files the body points to, or remove those references if the inline content is intended to stand alone.

Confirm referenced paths match actual bundle filenames exactly so the Additional Resources links resolve.

Consider noting one-line scope hints under each reference link so Claude can decide whether the deeper file is worth loading.

DimensionReasoningScore

Conciseness

Lean, table-driven reference with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides complete, executable SQL snippets for CTEs, chained CTEs, window functions, pagination, and keyset pagination, plus function-to-use tables that are copy-paste ready.

3 / 3

Workflow Clarity

As a single-purpose reference skill with unambiguous, well-organized sections and no destructive or batch operations, it meets the simple-skill allowance for a top score.

3 / 3

Progressive Disclosure

Sections are well organized and an "Additional Resources" section signals deeper references, but the cited files (./references/window-functions.md and ./references/indexing-strategies.md) do not exist, so the disclosure points to missing material.

2 / 3

Total

11

/

12

Passed

Description

100%

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 is concise, third-person, and names concrete capabilities with an explicit trigger clause covering both 'what' and 'when'. It is a strong example of a well-formed skill description with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities—"common SQL patterns, CTEs, window functions, and indexing strategies"—mirroring the level-3 example of enumerating specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers what ("Quick reference for common SQL patterns, CTEs, window functions, and indexing strategies") and when via the explicit "Triggers on:" clause, satisfying both requirements.

3 / 3

Trigger Term Quality

"Triggers on: sql patterns, cte example, window functions, sql join, index strategy, pagination sql" covers natural phrasings a user would say, including common variations.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear SQL-reference niche with distinct trigger terms, making it unlikely to fire for unrelated skills.

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.

Validation16 / 16 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.