database-performance-tuning
Skill24 starsChanged 8 months agoGPL-3.0View on GitHub
Diagnose and fix slow databases the way a DBA does — measure first, read the plan, then change one thing. Use this skill whenever a query, endpoint, job or report is slow, times out, or got slower after a deploy; whenever someone asks about indexes (missing, unused, duplicate, composite order, partial, covering, GIN/BRIN), EXPLAIN or query plans, seq scans, N+1 queries, slow pagination, table or index bloat, autovacuum, VACUUM, ANALYZE, stale statistics, connection or lock pileups, high CPU/IO on the database, partitioning, or a migration that locked a table. Also trigger on Portuguese phrasings: 'query lenta', 'consulta lenta', 'banco lento', 'timeout no banco', 'falta índice', 'criar índice', 'travou a tabela', 'lock', 'vacuum', 'plano de execução'. Postgres is the core; MySQL/InnoDB is covered in references/mysql.md. Use it even when the user just says 'this page is slow' and the data comes from a database — the first job of this skill is to find out whether the database is actually the problem.
In this repository38 other files it gives its agents.
- engineering-betterauth-integrationSkill
- engineering-bullmq-game-queuesSkill
- narrative-character-design-narrativeSkill
- infrastructure-ci-cd-gameSkill
- claude-agent-sdkSkill
- infrastructure-claude-code-game-workflowSkill
- infrastructure-cursor-codex-integrationSkill
- engineering-elevenlabs-sound-musicSkill
- foundry-vtt-module-devSkill
- foundry-vtt-system-devSkill
- engineering-game-backend-architectureSkill
- design-game-design-fundamentalsSkill
- game-architectSkill
- game-balanceSkill
- game-buildSkill
- game-expandSkill
- game-loreSkill
- game-questSkill
- game-reviewSkill
- design-game-economy-designSkill
- engineering-gameplay-analyticsSkill
- engineering-game-state-syncSkill
- design-level-designSkill
- engineering-matchmaking-systemSkill
- infrastructure-monitoring-game-opsSkill
- nuvemshop-sdkSkill
- openclaw-genieSkill
- engineering-postgres-game-schemaSkill
- design-procedural-genSkill
- design-quest-mission-designSkill
- narrative-quest-narrative-coherenceSkill
- react-animationsSkill
- engineering-redis-game-patternsSkill
- design-skill-progression-treesSkill
- narrative-story-structure-gameSkill
- engineering-stripe-game-paymentsSkill
- design-ui-ux-gameSkill
- narrative-worldbuildingSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 2 are distinctive, and 8 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.