Sql Optimization
v1.0.0Deep SQL performance workflow—symptom framing, execution plans, indexing strategy, query rewrite, locking/transaction behavior, statistics, partitioning, and...
⭐ 0· 105·1 current·1 all-time
byClawKK@codekungfu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (deep SQL performance workflow) align with the SKILL.md content. The document focuses on framing, measuring, reading plans, indexing, query/transaction tuning, and verification — all directly relevant to SQL optimization. It does not request unrelated binaries, services, or credentials in metadata.
Instruction Scope
Instructions are detailed and remain within SQL optimization scope. They explicitly recommend running EXPLAIN (ANALYZE, BUFFERS), repeated measurements, DDL proposals (create/drop indexes, concurrent operations), load tests/shadow traffic, and monitoring. These are expected for the purpose but are high-impact operations: EXPLAIN ANALYZE and load tests can execute queries and load production systems, and DDL changes can affect writes. The skill does not autonomously prescribe exactly when to execute such operations in production — the user/agent must ensure safe targeting and approvals.
Install Mechanism
No install spec and no code files — instruction-only. This is low risk from an install/execution point of view because nothing is downloaded or written by the skill itself.
Credentials
Metadata declares no required env vars or credentials, which is reasonable for an instruction-only guide. However, the workflow implicitly requires database connectivity and sufficient DB privileges to run EXPLAIN ANALYZE, inspect plans/stats, and (optionally) create/drop indexes or run load tests. That implicit need for DB access (and potentially elevated write/DDL permissions) should be acknowledged before granting an agent access to environments, especially production.
Persistence & Privilege
always:false and no install actions; the skill does not request persistent presence or modify other skills/config. Autonomous invocation is allowed by platform default but the skill itself does not require elevated platform privileges.
Assessment
This guidance is coherent and useful for DB tuning, but it assumes access to a database and the ability to run potentially disruptive commands. Before using it: (1) never grant the agent unrestricted production DB credentials — prefer read-only or restricted-analysis roles for initial investigation; (2) require human approval for any DDL (index creation/drop) or changes that affect writes; use CONCURRENT/online DDL where supported; (3) be cautious with EXPLAIN ANALYZE and load tests — they can execute heavy queries and stress systems; run them against staging or shadow traffic when possible; (4) have backups, monitoring, and rollback plans in place before changing schema or indexes; (5) ensure audit logs and change controls capture any commands the agent runs; and (6) if you want the agent to actually execute commands, explicitly provision least-privilege credentials and limit the scope (specific DB, read-only by default). If these operational safeguards are acceptable, the skill's guidance appears appropriate and coherent.Like a lobster shell, security has layers — review code before you run it.
latestvk971nnsw6xw8zxfnxg9z339dmn83g509
License
MIT-0
Free to use, modify, and redistribute. No attribution required.