SkillAgentSearch skills...

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-journal

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

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.

Substance
20/30
Structure
18/20
Description
15/15
Adoption
20/20
Freshness
15/15

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.

SkillScoreStarsUpdatedFormat
desk-journal (this skill)by github9039.3k1d agoSKILL.md
ai-job-searchby MadsLorentzen10043.9k4d agoCLAUDE.md
claude-howtoby luongnv8910041.7k5d agoCLAUDE.md
algorithmic-artby anthropics100177.9k2d agoSKILL.md
pptxby anthropics100177.9k2d agoSKILL.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.

name: 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

View on GitHub
GitHub Stars39.3k
CategoryDevelopment
Updated1d ago
Forks5.0k

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions