Works with the AI Agents you already use
MySQL Performance Doctor
Diagnose MySQL performance with query plans, indexes, locks, buffer behavior, and workload-specific evidence.
$9.99
MySQL Performance Doctor
Example session with this skill installed
A MySQL report query is slow after a new filter was added. Create a diagnostic sequence before changing indexes.
- Read your context and instructions
- Compiled the mysql performance doctor
MySQL Performance Doctor: practical plan
MySQL diagnostic sequence
Establish context
Capture MySQL version, query, parameters, table sizes, indexes, row counts, workload timing and when the regression began. Compare old and new query behavior.
Explain the plan
Use EXPLAIN and, where safe and supported, EXPLAIN ANALYZE. Review chosen index, estimated rows, join order, access type, temporary tables and filesort. Compare estimates with actual rows.
Predicate and index review
Check whether the new filter is selective, type-compatible and sargable. Look for functions or implicit casts on indexed columns. Evaluate composite index column order against real predicates and sort needs; account for write and storage cost.
System bottlenecks
Inspect CPU, I/O, buffer-pool hit patterns, lock waits, connection saturation and replication. Check for parameter skew and concurrency differences.
Safe change
Test query rewrite or index in staging with representative data. Measure p50/p95 latency and write impact. Roll out with monitoring and a rollback plan. Avoid copying generic tuning settings without evidence.
Measurement and review
Record the baseline, source, date range, denominator and owner. Use one primary measure plus quality guardrails; compare like-for-like cohorts and disclose missing data. Treat estimates as scenarios, not observed outcomes.
Risks and controls
Check relevance, consent, disclosure, workload and downside before scaling. Keep an evidence trail, obtain human review for material commitments, and pause if trust, quality or compliance signals deteriorate.
Next steps
- Confirm the goal, audience and available capacity.
- Gather the minimum evidence for a first test.
- Assign an owner, budget and review date.
- Run a small pilot, record outcomes and decide whether to iterate, expand or stop.
Connects securely to your tools. The creator never sees your data.
About this skill
Create a practical, evidence-led MySQL Performance Doctor workflow. Diagnose MySQL performance with query plans, indexes, locks, buffer behavior, and workload-specific evidence. Distinguish observations from assumptions, request missing inputs, give actionable recommendations with owners and measurable outcomes, and flag uncertainty. Avoid fabricated metrics, unsupported guarantees, deceptive tactics and unnecessary personal data.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago