github/desk-journal
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.
npx skills add https://github.com/github/awesome-copilot --skill desk-journal
Manage a desk's journal — the persistent memory that survives
session boundaries.
Append to desks/<desk-name>/journal.md. Each entry is a section:
## <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):
## <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.
Take github/desk-journal from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.