← Back to catalog

A few people have been asking about my Grok Bot setup. This is one of the skills I actively use.

A reusable /optimize skill measures speed first, applies safe fixes on a separate branch, reruns the same tests, and reports before and after plus what it couldn't measure.

For

An app feels slow and you want fixes checked against the same tests.

When you're done

On a small internal app it found a duplicate page load and repeated data reads; repeat-visit time fell 32–40% per the author.

How

  1. 01

    Save an /optimize skill covering N+1 queries, repeated reads, connection pooling, sequential API calls, heavy JavaScript and blocking tasks.

  2. 02

    Have it measure first.

  3. 03

    Apply safe fixes on a separate branch.

  4. 04

    Rerun the same tests and read the before-and-after report.

Notes

What's good: measure, fix on a branch, retest. The catch: results are from the author's own app.

Related plays

Write-ups follow public posts and official docs. No likes, views, or dashboard numbers. Open the source to check the original. About