- Home
- Skills
- Mobile Development
- Mobile Performance Regression Hunt
Mobile Performance Regression Hunt
Find which change made an app slower, hotter, or hungrier by measuring before and after, bisecting suspects, and confirming the fix.
$5
Works with the AI Agents you already use
Mobile Performance Regression Hunt
Example session with this skill installed
**Compare startup measurements:** good build runs of 1400, 1450, 1380 ms against bad build runs of 2600, 2550, 2650 ms.
- Read your context and instructions
- Compiled the mobile performance regression
Running the bundled comparator on those runs produces: ```text startup_ms: good median=1400 (range 1380-1450) bad median=2600 (range 2550-2650) change=+85.7% SEVERE ``` The comparator exits 1 here, because a regression is flagged; it exits 0 when no metric crosses the 20 percent threshold. The skill's worked example completes the hunt: the suspect ranking puts a new analytics SDK initialized synchronously on the launch path first, isolation by moving initialization to after first paint returns the median to 1.5 seconds, and the release procedure gains a cold-startup check with a 20 percent threshold.
Connects securely to your tools. The creator never sees your data.
About this skill
Performance intuition is unreliable: the change that "must" be responsible usually is not. This skill replaces intuition with bisection plus measurement. It starts by writing the metric and the repeatable procedure before measuring anything, measures a last-known-good build and the current build under identical conditions with repeated runs, ranks suspects by proximity to the metric, size of behavioral change, and timing, isolates one suspect at a time, confirms the culprit by reverting or fixing and re-measuring, and sets a release guard so the regression cannot silently return. It includes a decision table mapping each regressed metric to where to look first, investigation thresholds (20 percent or 500 ms for startup, 50 percent or 2 seconds for severe), a hunt record template, and a 15-point rubric. A runnable comparator reads two CSVs of repeated runs and reports medians, ranges, and percent change with investigate/severe flags.
- Needs a baseline: a previous build that behaved acceptably. Without one, this is tuning, not hunting. - Produces decisions a team can act on, not lab-grade benchmark statistics. - Subjective metrics (such as observed stutter) need a fixed pattern and, where possible, blind judging to stay honest.
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 23 days ago