Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/phx-perf
Analyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto optimization, genserver bottlenecks.
Passed 18 of 22 test cases with the skill, and 12 of 22 without it.
and 6 more in the full report
9 fixed12 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
At the end of a Phoenix performance review report, which slash command option should be offered when the developer wants to apply a top priority fix directly?
| Checked | Without skill | With skill |
|---|---|---|
| The response includes the '/phx-quick' slash command option. | Missed | Passed |
The instructions your model reads when the skill loads.
Analyze code for performance issues across Ecto, LiveView, and OTP layers. Prioritize findings by impact and effort.
/phx-perf # Analyze full project
/phx-perf lib/my_app/accounts.ex # Analyze specific module
/phx-perf --focus ecto # Ecto queries only
/phx-perf --focus liveview # LiveView memory only
/phx-perf --focus otp # OTP bottlenecks only
$ARGUMENTS = Optional module/context path and --focus flag.
MIX_ENV=prod for performance measurements; dev mode includes code reloading, debug logging, and unoptimized compilation that invalidate resultsCheck specific file if provided. Otherwise scan full project:
# Find hot paths: contexts, LiveViews, workers
find lib/ -name "*.ex" | head -50
Spawn analysis agents in parallel based on focus:
test cases passed, vs 12 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.