Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Write, append, or read desk journal entries. The journal is persistent memory — what survives session boundaries. A good entry has: what was done, current state, next step.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 49% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -35% | 0% |
| case-05 | ✗→✓ | ▲ Improved | 57% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 89% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 261% | 0% |
Manage a desk's journal — the persistent memory that survives session boundaries.
Append to desks/<desk-name>/journal.md. Each entry is a section:
markdown## <date> — <short summary> - **Worked on:** <what was done this session> - **Current state:** <where things stand right now> - **Next step:** <what the next session should pick up>
next session. "Scanned repos A, B, C for CWE-502; found 3 findings in A, 0 in B and C; findings triaged to bench" — that's a trail.
the next session from walking the same path.
3-5 lines per entry. If you need more, the important context should go on the bench as a separate artifact.
Without a next step, it has to re-derive everything.
When a desk is being wound down (not just a session ending, but the desk itself closing):
markdown## <date> — Desk closed - **Summary:** <what this desk accomplished overall> - **Artifacts:** <what's on the bench from this desk> - **Handoff:** <anything another desk or the operator needs to know>
At session start, read the desk's journal to pick up context. The most recent entry is the most important — it has the current state and next step. Earlier entries provide history if needed.
the way. Every entry is a stone.
is more useful than silence.
Write for someone who knows nothing about what you just did.
Other measured skills in the registry, with their headline benchmark lift.