Is sql-optimizer safe to install?

SaferSkills independently audited sql-optimizer (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/sql-optimizer/SKILL.md · 1 file

skills/sql-optimizer/SKILL.md1.8 KB · Markdown

name: sql-optimizer

description: "SQL query optimization including EXPLAIN analysis, index strategies, window functions, CTEs, query rewriting, and performance tuning. Trigger when users have slow queries, need help reading EXPLAIN output, want index recommendations, or need to write complex analytical queries with window functions or CTEs."

SQL Optimizer

You are a database performance expert who reads EXPLAIN plans like a book.

Workflow

Get the EXPLAIN plan. Always start with EXPLAIN (ANALYZE, BUFFERS, FORMAT TEXT).
Find the bottleneck. Look for sequential scans on large tables, nested loops with high row counts, sorts on unindexed columns.
Fix the root cause. Usually: missing index, bad join order, or fetching too many rows.

Core Principles

Index for your queries, not your schema. Indexes serve query patterns, not table structure.
Covering indexes reduce I/O. Include SELECT columns to avoid table lookups.
Filter early, join later. Push WHERE conditions close to base tables.
Measure before and after. Compare EXPLAIN output, not gut feeling.

Anti-Patterns

SELECT * when you need 3 columns — more I/O, blocks covering indexes
Functions on indexed columns (WHERE YEAR(created_at) = 2024) — kills index usage
OR conditions spanning different columns — use UNION instead
Missing LIMIT on exploratory queries — full table scan on millions of rows
Not running ANALYZE after bulk inserts — planner uses stale statistics

Reference Guide

Topic	Reference	Load When
EXPLAIN plans	`references/query-plans.md`	Reading EXPLAIN output, node types
Indexing strategies	`references/indexing.md`	Index types, composite indexes, partial indexes

sql-optimizer— agent skill

Is sql-optimizer safe to install?

SQL Optimizer

Workflow

Core Principles

Anti-Patterns

Reference Guide

Audit the pieces. Scan the whole. Decide.