Skill sql-optimization
Optimalkan performa database melalui strategi indexing, analisis query, desain schema, dan pola implementasi.
- Bintang GitHub
- 23
- File
- 1
- Commit terakhir
- 11 Nov 2026
- Lisensi
- CC-BY-SA-4.0
- Tool yang diizinkan
- —
Apa fungsi skill sql-optimization?
Optimalkan performa database melalui strategi indexing, analisis query, desain schema, dan pola implementasi.
Ringkasan dibuat dari SKILL.md skill ini.
Tentang skill sql-optimization
Meningkatkan performa database melalui query tuning dan desain schema adalah fungsi utama dari skill ini. Developer menggunakannya saat perlu menganalisis query yang lambat, merancang strategi indexing yang efisien, atau mengimplementasikan pola data yang lebih baik. Seorang agent harus memuat skill ini untuk mengubah SQL yang tidak efisien menjadi kode yang berperforma tinggi dengan menerapkan prinsip seperti composite indexing, menghindari masalah N+1, dan menggunakan cursor-based pagination alih-alih offset limits yang lambat.
Skill ini memberikan panduan spesifik dalam menginterpretasikan output EXPLAIN ANALYZE, serta membedakan antara sequential scans dan index-only scans. Selain itu, skill ini mencakup teknik optimasi schema seperti normalisasi untuk workload yang berat di penulisan (write-heavy) atau denormalisasi untuk kecepatan pembacaan (read speed). Untuk menjaga keamanan, skill ini menekankan penggunaan parameterized statements guna mencegah SQL injection dan menyarankan untuk menjalankan performance benchmarks di lingkungan staging yang sudah disanitasi daripada di database production. Skill ini juga menyarankan penggunaan statement timeouts untuk mencegah kehabisan sumber daya akibat query yang kompleks.
Apa yang bisa dilakukan agent dengannya
- 1Analisis execution plan pada query yang lambatPeriksa output EXPLAIN ANALYZE untuk mengidentifikasi apakah sebuah query melakukan full table scan yang lambat.
Ditulis dari SKILL.md milik skill tersebut. Setiap use case diverifikasi dengan kutipan darinya.
Cara install skill sql-optimization
Setiap perintah menyalin folder skill ke direktori skills client. Restart client atau mulai sesi baru untuk memuatnya.Install skill sql-optimization di Plugin
/plugin marketplace add andreibesleaga/GABBE /plugin install gabbe-data@gabbe
Install skill sql-optimization di Claude Code
~/.claude/skills/sql-optimization/SKILL.md
$ npx degit andreibesleaga/GABBE/plugins/gabbe-data/skills/sql-optimization ~/.claude/skills/sql-optimizationInstall skill sql-optimization di Claude Code (project)
.claude/skills/sql-optimization/SKILL.md
$ npx degit andreibesleaga/GABBE/plugins/gabbe-data/skills/sql-optimization .claude/skills/sql-optimizationInstall skill sql-optimization di Codex
~/.agents/skills/sql-optimization/SKILL.md
$ npx degit andreibesleaga/GABBE/plugins/gabbe-data/skills/sql-optimization ~/.agents/skills/sql-optimizationInstall skill sql-optimization di Gemini CLI
~/.gemini/skills/sql-optimization/SKILL.md
$ npx degit andreibesleaga/GABBE/plugins/gabbe-data/skills/sql-optimization ~/.gemini/skills/sql-optimizationInstall skill sql-optimization di Claude.ai
npx degit andreibesleaga/GABBE/plugins/gabbe-data/skills/sql-optimization sql-optimization && zip -r sql-optimization.zip sql-optimization # claude.ai → Customize → Skills → + → Create skill → Upload a skill → sql-optimization.zip
Pengecekan otomatis
Berjalan 16 Nov 2026Laporan lengkap →Belum terverifikasi. Skill perlu skor 80, tanpa temuan serius, dan data yang cukup untuk kami cek. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkauandreibesleaga/gabbe/plugins/gabbe-data/skills/sql-optimization is public and reachablegithub.com/andreibesleaga/gabbe/tree/HEAD/plugins/gabbe-data ↗Lolos
- Lisensi open source (OSI)CC-BY-SA-4.0 is not OSI-approvedspdx.org/licenses/CC-BY-SA-4.0.html ↗Temuan
- Ada commit atau release dalam satu tahun terakhirLast commit 2026-11-11github.com/andreibesleaga/gabbe/commits ↗Lolos
- Skrip tanpa unduh-lalu-jalankan atau pencurian kredensialNo scripts in the skill folderLolos
- Tidak ada instruksi tersembunyi di SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/andreibesleaga/gabbe/blob/HEAD/plugins/gabbe-data ↗Lolos
- Tool yang diizinkan otomatis dibatasiNo pre-approved tools; the agent asks before using onegithub.com/andreibesleaga/gabbe/blob/HEAD/plugins/gabbe-data ↗Lolos
- SKILL.md mengikuti format Agent SkillsValid name and description; says when to use it; 81 linesgithub.com/andreibesleaga/gabbe/blob/HEAD/plugins/gabbe-data ↗Lolos
SKILL.md
Lihat di GitHubsql-optimization Skill
Goal
This skill focuses on ensuring database interactions are performant and scalable.
Steps
1. The Golden Rule: Indexing
- Primary Keys: Always indexed by default (B-Tree).
- Foreign Keys: MUST be indexed manually in most DBs (Postgres/MySQL) to avoid full table scans on joins.
- Where Clauses: Columns used in
WHERE,ORDER BY,GROUP BYneed indexes. - Composite Indexes: Order matters!
(last_name, first_name)supports lookup bylast_nameORlast_name + first_name, but NOT byfirst_namealone.
2. Analyzing Queries (EXPLAIN ANALYZE)
Always run EXPLAIN ANALYZE on suspect queries.
| Output Term | Meaning | Action |
|---|---|---|
| Seq Scan / Full Table Scan | Reading every row. | Bad (unless table is tiny). Add an index. |
| Index Scan | Reading index + looking up heap. | Good. |
| Index Only Scan | Reading only index. | Best. (Covering Index). |
| Nested Loop | Looping for joins. | Fine for small datasets. Bad for large. |
| Hash Join | Building hash table for join. | Good for large datasets. |
3. Implementation Patterns
1. Select Only What You Need
- Bad:
SELECT * FROM users - Good:
SELECT id, name FROM users - Reason: Reduces IO, network payload, and memory usage.
2. Solve the N+1 Problem
- Problem: Fetching 100 posts, then running 100 queries to get authors.
- Fix: Use
JOINor eager loading (ORM specific:include,with). - Detection: Use logs or APM query counts.
3. Pagination
- Offset/Limit:
OFFSET 1000000is slow (DB scans 1M rows then discards). - Cursor/Keyset:
WHERE id > last_seen_id LIMIT 10. O(1) performance.
4. Transactions
- Keep them short.
- Don't make external API calls inside a DB transaction (holds locks).
4. Schema Optimization
- Normalization (3NF): Reduces redundancy, ensures integrity. Good for write-heavy.
- Denormalization: Adds redundancy for read speed (e.g., storing
author_nameonpoststable). - Data Types: Use the smallest needed type.
VARCHAR(255)vsTEXT(Postgres treats similar, MySQL differs).INTvsBIGINT.JSONB(Postgres) for unstructured data, but don't overuse it.
5. Maintenance
- Run
VACUUM ANALYZE(Postgres) regularly to update planner statistics. - Monitor index usage. Remove unused indexes (they slow down writes).
Security & Guardrails
1. Skill Security (SQL Optimization)
- Query Parameterization: Optimized queries must always use parameterized statements or prepared statements to prevent SQL Injection (SQLi). Never concatenate strings for query building.
- Safe EXPLAIN Execution: Be cautious when running
EXPLAIN ANALYZE, as it actually executes the query. On production, ensure it is only run onSELECTstatements, as running it onINSERT/UPDATE/DELETEwill modify data.
2. System Integration Security
- Resource Exhaustion Prevention: Limit the execution time of optimized queries (e.g.,
statement_timeoutin Postgres) to prevent Denial of Service (DoS) attacks via complex, CPU-intensive queries. - Data Exposure Restrictions: When optimizing
SELECTqueries or adding denormalized columns, ensure that access control rules (Row-Level Security) are maintained and sensitive columns are not inadvertently exposed.
3. LLM & Agent Guardrails
- SQLi Generation Defense: LLMs tasked with optimizing SQL must be strictly instructed and verified to output parameterized queries, rejecting user inputs that attempt to inject raw SQL commands.
- Execution Sandboxing: Agents must not execute optimized queries directly against production databases. Performance benchmarking must be done in a sanitized, ephemeral staging environment.
- Data Masking in Context: When feeding slow queries and
EXPLAINplans into an LLM for analysis, all literal values (e.g., specific user emails, IDs) must be masked or redacted to prevent PII leakage into the model's context.
Berkas dalam skill ini
1Pertanyaan seputar skill sql-optimization
Bagaimana cara install skill sql-optimization di Claude Code?
Jalankan npx degit andreibesleaga/GABBE/plugins/gabbe-data/skills/sql-optimization ~/.claude/skills/sql-optimization. Claude Code memuat skill dari ~/.claude/skills (semua proyek) atau .claude/skills (satu proyek) dan menggunakan skill saat deskripsinya cocok dengan tugas.
Client mana saja yang bisa menggunakan skill sql-optimization?
Client apa pun yang membaca format Agent Skills: Claude Code, Codex, Gemini CLI, dan claude.ai (unggah sebagai ZIP). Script dalam skill hanya berjalan di client yang mengizinkan eksekusi kode.
Bagaimana cara mengidentifikasi query yang lambat menggunakan EXPLAIN ANALYZE?
Anda dapat mencari 'Seq Scan' atau 'Full Table Scan' pada output, yang mengindikasikan bahwa database membaca setiap baris dan mungkin memerlukan index.