Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill sql-query-optimizerSql Query Optimizer - Auto-activating skill for Data Analytics. Triggers on: sql query optimizer, sql query optimizer Part of the Data Analytics skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with minimal useful content. It only provides the skill name, a duplicate trigger term, and a category label without explaining what the skill does or when it should be used. Claude would have difficulty knowing when to select this skill over others.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes SQL query execution plans, identifies performance bottlenecks, suggests index optimizations, and rewrites inefficient queries.'
Add a 'Use when...' clause with natural trigger terms like 'slow query', 'optimize SQL', 'query performance', 'database is slow', 'improve query speed', 'execution plan'.
Include file types or contexts where this applies, e.g., 'Use when working with PostgreSQL, MySQL, or SQL Server queries that need performance improvements.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the skill name 'Sql Query Optimizer' and category 'Data Analytics'. There's no explanation of what the skill actually does (e.g., analyze query plans, suggest indexes, rewrite queries). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'sql query optimizer' repeated twice, which is the exact skill name rather than natural user language. Missing common variations like 'slow query', 'optimize SQL', 'query performance', 'database tuning', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'SQL Query Optimizer' is a specific domain, the lack of detail means it could overlap with general database skills or data analytics skills. The category mention 'Data Analytics' is too broad to provide clear differentiation. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely meta-description with no actual instructional value. It describes what a SQL query optimizer skill should do without providing any concrete optimization techniques, SQL examples, or actionable guidance. The content is essentially a placeholder template that teaches Claude nothing about SQL query optimization.
Suggestions
Add concrete SQL optimization examples showing before/after queries with EXPLAIN ANALYZE output
Include specific optimization techniques: indexing strategies, query rewriting patterns, JOIN optimization, avoiding SELECT *
Provide a workflow for analyzing slow queries: identify -> EXPLAIN -> optimize -> validate performance improvement
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual optimization guidance
| 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 optimization techniques, no commands, no code. The entire content describes what the skill supposedly does without actually teaching anything actionable. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains no actual steps. There are no validation checkpoints or processes for SQL query optimization. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual resources. No references to detailed materials, examples, or related documentation. | 1 / 3 |
Total | 4 / 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
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.