Desk-Journal
Desk-Journal is an code AI skill with a core value of Write, append, or read desk journal entries. It
helps developers solve real-world problems in the code domain, boosting
efficiency, automating repetitive tasks, and optimizing workflows.
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.
Quick Facts
mkdir -p ./skills/desk-journal && curl -sfL https://raw.githubusercontent.com/github/awesome-copilot/main/skills/desk-journal/SKILL.md -o ./skills/desk-journal/SKILL.md Run in terminal / PowerShell. Requires curl (Unix) or PowerShell 5+ (Windows).
Skill Content
# 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.
🎯 Best For
- Claude users
- GitHub Copilot users
- Software engineers
- Development teams
- Tech leads
💡 Use Cases
- Code quality improvement
- Best practice enforcement
📖 How to Use This Skill
- 1
Install the Skill
Copy the install command from the Terminal tab and run it. The SKILL.md file downloads to your local skills directory.
- 2
Load into Your AI Assistant
Open Claude or GitHub Copilot and reference the skill. Paste the SKILL.md content or use the system prompt tab.
- 3
Apply Desk-Journal to Your Work
Open your project in the AI assistant and ask it to apply the skill. Start with a small module to verify the output quality.
- 4
Review and Refine
Review AI suggestions before committing. Run tests, check for regressions, and iterate on the skill output.
❓ Frequently Asked Questions
Is Desk-Journal compatible with Cursor and VS Code?
Yes — this skill works with any AI coding assistant including Cursor, VS Code with Copilot, and JetBrains IDEs.
Do I need specific dependencies for Desk-Journal?
Check the install command and Works With section. Most code skills only require the AI assistant and your codebase.
How do I install Desk-Journal?
Copy the install command from the Terminal tab and run it. The skill downloads to ./skills/desk-journal/SKILL.md, ready to use.
Can I customize this skill for my team?
Absolutely. Edit the SKILL.md file to add team-specific instructions, examples, or workflows.
⚠️ Common Mistakes to Avoid
Skipping validation
Always test AI-generated code changes, even for simple refactors.
Missing dependency updates
Check if the skill requires updated dependencies or new packages.