Desk Journal
GitHubOfficialFirst committed by jennyf19Distributed by GitHub
- Skill
- Meta (authoring, orchestration, planning, memory)
- Agent tooling
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The desk-journal skill provides a structured method for maintaining persistent memory across AI agent sessions. By recording progress, current status, and future objectives in a standardized format, the agent creates a trail of context that ensures continuity. It is designed to help the agent pick up exactly where it left off, preventing redundant work and preserving valuable insights from previous sessions.
What it does
- Records session progress, current state, and upcoming tasks.
- Provides a standardized template for daily journal entries.
- Supports end-of-desk summaries for project completion or handoff.
- Enables reading of past entries to reconstruct context at session start.
- Encourages documenting dead ends to avoid repeating unsuccessful paths.
When to use it
- At the end of a session to summarize work and define the next steps.
- At the start of a new session to review previous progress.
- During mid-session checkpoints to record significant decisions.
- When closing a desk to provide a final project summary and handoff notes.
Advantages
- Ensures continuity by providing a clear starting point for future sessions.
- Reduces cognitive load by offloading state management to persistent storage.
- Prevents the repetition of failed approaches by documenting dead ends.
- Facilitates better handoffs by summarizing accomplishments and artifacts.
Usage examples
- “Write a journal entry for today's session.”
- The agent creates a new section in the journal file with the current date, summarizing the work completed, the current state of the project, and the specific next steps for the next session.
- “Read the journal to catch me up on this desk.”
- The agent reads the most recent entries from the journal file and provides a summary of the project's history, current status, and the pending next steps.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/github/desk-journal/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip desk-journal.zip -d .agents/skills
Documentation by jennyf19
Desk Journal
Manage a desk's journal — the persistent memory that survives session boundaries.
When to use
End of session: Write what was done, current state, next step
Start of session: Read the journal to pick up where you left off
Mid-session checkpoint: Note significant progress or decisions
Desk wind-down: Write a final summary when a desk is being closed
How to write a journal entry
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>Guidelines
Be specific. "Worked on security scanning" is useless to the 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.
Include what didn't work. Dead ends are valuable — they prevent the next session from walking the same path.
Keep it short. The journal is a trail marker, not a diary. 3-5 lines per entry. If you need more, the important context should go on the bench as a separate artifact.
Always include next step. The next session starts from zero. Without a next step, it has to re-derive everything.
End-of-desk entry
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>Reading the journal
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.
Principles
The journal is a cairn — stones left so the next traveler finds the way. Every entry is a stone.
Honesty over completeness. "I got stuck on X and don't know why" is more useful than silence.
The journal is for the next session, not for the current one. Write for someone who knows nothing about what you just did.
Files
- ATTRIBUTION.mdAdded by AutoGineer857 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md2.4 KiB
Requirements and compatibility
Written for: GitHub Copilot
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- First committed by
jennyf19
- Publisher
- GitHub (Official)
- Distributed by
- GitHub
- Source
- github/awesome-copilot · skills/desk-journal · commit 797337f
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Contributors
- jennyf19
AutoGineer is not affiliated with or endorsed by jennyf19 or GitHub.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download desk-journal.zip