alonso-skills/sql-server-performance
Diagnoses and optimizes SQL Server database performance. Use when diagnosing slow T-SQL queries, tuning indexes, reading execution plans, fixing parameter sniffing, optimizing batch operations, reducing transaction log bloat, troubleshooting locking and blocking, configuring tempdb, or when a query that used to be fast is now slow. Also use when writing high-throughput INSERT/UPDATE/DELETE operations, implementing minimal logging, designing covering indexes, or analyzing wait statistics.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that hits all the marks. It provides highly specific concrete actions, uses natural trigger terms that a SQL Server DBA would actually say, explicitly addresses both what the skill does and when to use it, and is clearly distinguishable from other database or general coding skills. The inclusion of the symptom-based trigger 'query that used to be fast is now slow' is particularly effective.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: diagnosing slow T-SQL queries, tuning indexes, reading execution plans, fixing parameter sniffing, optimizing batch operations, reducing transaction log bloat, troubleshooting locking and blocking, configuring tempdb, writing high-throughput DML operations, implementing minimal logging, designing covering indexes, and analyzing wait statistics. | 3 / 3 |
Completeness | Clearly answers both 'what' (diagnoses and optimizes SQL Server database performance) and 'when' with an explicit and detailed 'Use when...' clause covering numerous specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'slow T-SQL queries', 'execution plans', 'parameter sniffing', 'locking and blocking', 'tempdb', 'transaction log bloat', 'wait statistics', 'covering indexes', 'query that used to be fast is now slow'. These are highly natural phrases a DBA or developer would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to SQL Server specifically, with domain-specific terms like 'T-SQL', 'tempdb', 'parameter sniffing', and 'wait statistics' that clearly distinguish it from general database skills or other RDBMS-focused skills. | 3 / 3 |
Total | 12 / 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 exceptionally well-crafted skill that serves as a model for SQL Server performance tuning guidance. It combines a clear diagnostic workflow with concrete, executable examples and precise decision criteria throughout. The progressive disclosure is excellent — the main file is self-contained for common scenarios while cleanly referencing deeper material for specialized topics.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is dense with actionable information and avoids explaining basic concepts Claude already knows. Every section delivers specific technical guidance — no padding about what SQL Server is or how databases work. Comments in SQL are minimal and purposeful. | 3 / 3 |
Actionability | Every section provides executable T-SQL code, specific DMV queries, concrete index creation examples, and precise decision criteria (e.g., '1,000+ rows', '3–5 nonclustered indexes'). The SARGability table gives exact before/after patterns. The parameter sniffing section provides ranked, copy-paste-ready solutions. | 3 / 3 |
Workflow Clarity | The diagnostic flowchart is a clearly sequenced 5-step process where each step narrows the cause before proceeding. Each step includes what to look for and what to fix. The parameter sniffing strategies are explicitly ranked with rationale for when to use each. Decision rules for temp tables vs table variables provide clear branching logic. | 3 / 3 |
Progressive Disclosure | The skill provides a comprehensive but scannable overview with well-signaled one-level-deep references to six specific reference files. Each reference link is annotated with what it covers. The main file contains enough to act on immediately while pointing to deeper material for specialized topics. | 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