Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/lv-assigns
Inspect LiveView socket assigns for memory bloat — missing temporary_assigns, unused assigns, unbounded lists needing streams, memory estimates.
Passed 13 of 18 test cases with the skill, and 11 of 18 without it.
and 1 more in the full report
4 fixed12 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
In `lib/metrics_web/live/telemetry_live.ex`, the socket holds a list of 1,000 log entry maps in assigns. What is the estimated memory footprint range that should be reported, and what concern level applies?
| Checked | Without skill | With skill |
|---|---|---|
| Estimates memory usage around 100 to 500 KB for a 1,000 item list. | Missed | Passed |
| Flags the memory footprint concern level as High. | Passed | Passed |
The instructions your model reads when the skill loads.
Analyze LiveView socket assigns for memory efficiency, clarity, and best practices.
Use Grep to find all assign( and assign_new( calls in the target LiveView file.
Use Grep to find large data patterns: lists stored in assigns (assign.*\[\], assign.*Repo\.all) and full schema storage (assign.*Repo\.get) in the target file.
| Pattern | Problem | Solution |
|---|---|---|
assign(:items, Repo.all(...)) | Unbounded list | Use stream/3 |
assign(:user, Repo.get!(...)) | Full schema | Select only needed fields |
assign(:file_data, binary) | Large binary | Store reference, not data |
| Nested preloads | Excessive data | Preload only what's rendered |
Should use temporary_assigns:
test cases passed, vs 11 / 18 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.