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.
Install / Use
npx skills add github/awesome-copilot --skill desk-journalInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of desk-journal
desk-journal scores 90/100 on our quality scale, 300th of 1,751 Development & Engineering skills we index (top 18%).
Its SKILL.md is 2.4 KB long, well organised into 9 sections with 2 code examples: moderately detailed.
With 39,348 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated yesterday, so desk-journal is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
desk-journal compared with similar skills
All 4 of these similar skills score higher than desk-journal; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| desk-journal (this skill)by github | 90 | 39.3k | 1d ago | SKILL.md |
| ai-job-searchby MadsLorentzen | 100 | 43.9k | 4d ago | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 41.7k | 5d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 2d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 2d ago | SKILL.md |
Frequently asked questions
- How do I install desk-journal?
- Run
npx skills add github/awesome-copilot --skill desk-journal. The install tabs above show the steps for each supported agent. - Which AI agents does desk-journal work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is desk-journal safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is desk-journal still maintained?
- The repository was last updated yesterday, so desk-journal is actively maintained.
Skill content
View source on GitHubname: desk-journal description: '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.'
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.
Related Skills
ai-job-search
43.9kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
41.7kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
