Index of every page on this site: llms.txt
All skills
dominiktobureto avatar

/performance-optimizer

@9125e02
Run it yourself

Use for slow endpoints, p95/p99 latency, database query issues, frontend bundle/render performance, memory leaks, caching, profiling, or performance regressions.

Use this Skill: https://skilld.dev/gh/dominiktobureto/awesome-grok-build/performance-optimizer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈46 tokens for metadata: the name and description. ≈353 when used: this file.

Description uses 2.3% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈185 characters, or 2.3%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

  1. Define the metric and baseline.
  2. Reproduce or inspect evidence.
  3. Find the bottleneck with the least invasive tool available.
  4. Propose 2-3 fixes with tradeoffs.
  5. Implement the smallest fix.
  6. Re-measure or run a focused benchmark/test.
  7. 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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts5mo3 checks · Risk SAFE
  • Gen Agent Trust Hub5mo

    No security issues were detected. The skill provides safe, high-level process guidance for performance optimization tasks, emphasizing measurement, verification, and human oversight.

  • Socket5mo

    No alerts

  • Snyk5mo

    Risk: LOW · No issues

Signed by skilld at 9125e02. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 6 months ago
version
1.0.0
author
awesome-grok-build

README badge

README badge for dominiktobureto/awesome-grok-build/performance-optimizer