Install any skill in seconds. Free to start, no credit card required.
Get Started Free →saffron-health/glimpse-changes
Create a visual explanation of the current session diff as a single HTML page and show it in a native Glimpse window.
Passed 17 of 20 test cases with the skill, and 10 of 20 without it.
and 6 more in the full report
9 fixed10 passed either way2 still failing1 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.
What command checks the available options and setup flags for the visual changes walkthrough renderer package?
| Checked | Without skill | With skill |
|---|---|---|
| Executes npx [email protected] --help | Missed | Passed |
The instructions your model reads when the skill loads.
Render a Markdown walkthrough in a native Glimpse window with syntax-highlighted code and rich diff rendering.
npx [email protected] --help
Use Glimpse to walk another developer through the code in the clearest order, not necessarily the order files appear in the diff.
Aim for a short, reviewable document:
changes or diff blocks to explain intent, tradeoffs, and review risks.Prefer a narrative that follows the user or developer flow: what someone sees or does, how the request/state/data moves through the system, then any supporting helpers, tests, docs, or cleanup. If another order is clearer, use that instead.
Write like a developer walking another developer through the change. Be direct and specific. Avoid dumping one large diff with a generic explanation. Prefer smaller, focused sections when they help the reader understand the code.
Good explanation style:
Template:
# <Title>
## Summary
- <User-visible or developer-visible effect>
- <Main code path changed>
test cases passed, vs 10 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.