Performance optimizer
Skill DominikTobureto/awesome-grok-build/.grok/skills/performance-optimizer
Grok Build resources, reusable .grok/skills, AGENTS.md templates, hooks, prompts, and starter workflows.
npx -y skills add DominikTobureto/awesome-grok-build --skill performance-optimizerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Use for slow endpoints, p95/p99 latency, database query issues, frontend bundle/render performance, memory leaks, caching, profiling, or performance regressions.
SKILL.md
1.6 KB, as published. Nobody here has run it
Performance Optimizer
Measure first, optimize second, verify always.
Grok Build Mode
- Use Plan Mode before broad rewrites or caching changes.
- Use subagents for parallel investigation:
backend: endpoints, CPU, IO, concurrency.database: query shape, indexes, N+1, transactions.frontend: bundle, render loops, hydration, assets.infra: deploy, network, cache, limits.
- Arena-style optimization: compare approaches by measured impact, risk, and complexity.
- Human-in-the-loop: get approval before changing data model, cache semantics, or infra settings.
Workflow
- Define the metric and baseline.
- Reproduce or inspect evidence.
- Find the bottleneck with the least invasive tool available.
- Propose 2-3 fixes with tradeoffs.
- Implement the smallest fix.
- Re-measure or run a focused benchmark/test.
- Document the before/after.
Rules
- Do not optimize without a metric.
- Avoid caching correctness bugs.
- Prefer algorithm/query fixes over hardware assumptions.
- Keep performance tests stable and bounded.
- Watch for memory and bundle-size regressions.
Example Prompts
Use performance-optimizer. Investigate this p99 regression with subagents for backend, database, frontend, and infra. No edits until evidence is summarized.
Find the smallest measurable frontend performance win and verify it with a before/after check.