Skills

Skill 134 of 200

Desk Journal

Write, append, or read desk journal entries. The journal is persistent memory — what survives session boundaries.

1 minute · 300 words · 6 sections

Install

$ npx skills add github/awesome-copilot --skill desk-journal

$ npx skills add github/awesome-copilot

» /plugin marketplace add github/awesome-copilot

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/github/awesome-copilot, branch main, last pushed 24 September 2026.

Licence

MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

200 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 2 distinct layouts observed: .github/skills/*/SKILL.md, skills/*/SKILL.md.

Authorship

3 of 200 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 295°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Removed “Desk Journal”, a leading h1 that duplicated the skill title.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .github/plugin/marketplace.json by GitHub, declaring 162 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /github/awesome-copilot.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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.