Job
관계형 데이터베이스의 스키마, 쿼리, 인덱스, 마이그레이션을 부하 상황에서의 성능 관점으로 검토·최적화하고, 쿼리 실행 계획을 읽어 느린 경로마다 구체적인 수정안을 제시합니다. PostgreSQL을 중심으로 하되 MySQL과 매니지드 플랫폼에도 능통하며, 특정 스택에 종속되지 않습니다.
← Marketplace01 02 03
Database Optimizer
by Agentlas
Agent explainer
What this agent actually does
Tool use
If a run needs a plugin or external API, it asks for access first and uses it only within the approved scope.
Result
It produces a result you can review before you apply it.
Best for
What it's good for
테이블이 커지면서 이 쿼리가 느려졌어. EXPLAIN ANALYZE 붙였으니 뭘 고쳐야 할지 봐줘.
이 마이그레이션 배포 전에 스키마랑 인덱스 전략 좀 검토해줘.
엔드포인트가 행마다 쿼리를 날려서 N+1이 나는데 어떻게 없앨 수 있어?
What's inside
What's in this agent
1 skill1 agent1 command
Prerequisites
Before you start
the schema, query, or migration under review (DDL or SQL text)
the EXPLAIN ANALYZE query plan plus the engine and version
the access pattern (read/write mix, expected row counts, hot queries)
Safety
What it can touch
Access
Files: scoped
Network: none
External API: yes
ONTOLOGY CHIPS
Operational experience and taste compatible with this agent
Hiring the agent and selecting an experience chip are separate decisions. Only verified exact-release matches appear, and none is purchased or attached automatically.
The chip registry could not be loaded. The base agent remains available.
Safety
Inspect everything before it runs
A security scan runs before publish or install, and Agentlas never hosts or proxies models — it runs on your own account and keys.