Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tutti-os/tutti-record-agent-session-replay
From a Tutti checkout, run, audit, freshly replay, publish, or diagnose Session Replay cassettes that are driven by case-repository scenario scripts (CDP), not by interactive UI recording.
Passed 12 of 19 test cases with the skill, and 2 of 19 without it.
and 16 more in the full report
11 fixed3 passed either way9 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to start the case repository QA console locally to review test plans. I plan to run `pnpm dev` and open `http://127.0.0.1:3334` in my browser. Is this port correct, or is there a different port or service setup required?
| Checked | Without skill | With skill |
|---|---|---|
| Directs browser access to http://127.0.0.1:3333 | Missed | Passed |
| Prohibits running the dev console with the background service concurrently | Missed | Passed |
The instructions your model reads when the skill loads.
Work from the Tutti checkout. Keep product implementation and the generic
runner in Tutti; keep Case metadata, scenario scripts, fixtures, qualified
Cassettes, and evidence in the external case repository (tutti-os/tutti-replay).
Mental model (script-first, not UI recording):
scenarios/*.mjs (prepare / drive /
assert) in the case repository — that script is the recording plan.Prove qualification in this order:
existing scenario script -> live Record (script + Provider) -> structural audit -> fresh Replay -> optional publication
Never call a Cassette qualified until Record, audit, and a fresh isolated
Replay have all passed. If the scenario script itself is missing or wrong,
stop and use the case repository write-replay-case skill — do not invent
Cases inside Tutti.
Qualification is assertion-specific, not command-specific. A replay passed
exit proves transport and semantic playback, but does not prove that every
Case action ran during Replay. Build a four-column matrix for each core
assertion: Record proof | Cassette proof | Replay proof | Evidence. Stop and
repair the scenario when any required Replay cell is empty.
Browsing Cases, Test Plans, and one-click Record/Replay (which run the same
scenario scripts) live in the case repository (sibling checkout, commonly
../tutti-replay; GitHub: tutti-os/tutti-replay).
From the case repository root:
test cases passed, vs 2 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.