Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingtai-ai/preset-skill-op-activation-session-refresh
How a saved preset becomes the running default, first-run/setup choice semantics, propagation, and what /refresh actually switches.
Passed 20 of 22 test cases with the skill, and 5 of 22 without it.
and 22 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/2/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
When the agent setup wizard writes out the manifest configuration for allowed presets, in what order does it write the default preset relative to other user-selected allowed presets?
| Checked | Without skill | With skill |
|---|---|---|
| State that the preset setup wizard writes the default preset as the first entry in manifest.preset.allowed. | Missed | Passed |
| Explain that user-checked presets are written after the default entry in row order. | Missed | Passed |
The instructions your model reads when the skill loads.
Evidence: tui/internal/tui/firstrun.go:2889-3073,
tui/internal/tui/firstrun.go:3615,
tui/internal/tui/firstrun.go:3697, tui/internal/tui/app.go:971-1020,
tui/internal/tui/app.go:1240-1342, tui/internal/tui/app.go:1407-1491, and
tui/internal/tui/app.go:1702-1728.
enterAgentPresets() (firstrun.go:2899-3000) lists only saved
presets (Source == SourceSaved via preset.IsTemplate), never raw
templates. A built-in template isn't "endorsed" onto this surface until
the user has edited and saved it — which materializes a saved preset. See
reference/operations/saved-presets/SKILL.md for the save mechanics that
put a preset here in the first place.
The wizard defaults to "nothing allowed except the one the user's cursor
was on when they entered this step" — the schema invariant is that
default must be a member of allowed, and the default row is always
forced into presetAllowed. allowedPresetRefs()
(firstrun.go:3042-3057) writes the default preset first, then the rest
of the user-checked rows in row order, into
manifest.preset.{default,allowed}.
Re-running /setup on an agent that already has an init.json hydrates
presetAllowed/presetDefaultIdx from the existing
manifest.preset.{default,allowed} (firstrun.go:2945-2997) rather than
resetting to "nothing allowed" — so re-running setup only changes what the
user explicitly changes. Path comparison is normalized (~/... vs
absolute) via presetRefMatches (firstrun.go:3014-3035) so the same file
referenced two different ways still matches. A preset the wizard's cursor
now points at, but which isn't in the existing allowed list (e.g. just
created in the editor), is auto-checked so it doesn't silently stay
unauthorized — the user can still uncheck it.
test cases passed, vs 5 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.