acquire-codebase-knowl…
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like…
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.
Claude Code
$ npx -y skills add github/awesome-copilot --skill desk-journal --agent claude-code
Codex
$ npx skills add github/awesome-copilot --skill desk-journal -a codex -y
Cursor
$ npx skills add github/awesome-copilot --skill desk-journal -a cursor -y
Gemini CLI
$ npx skills add github/awesome-copilot --skill desk-journal -a gemini-cli -y
GitHub Copilot
$ npx skills add github/awesome-copilot --skill desk-journal -a github-copilot -y
OpenCode
$ npx skills add github/awesome-copilot --skill desk-journal -a opencode -y
Windsurf
$ npx skills add github/awesome-copilot --skill desk-journal -a windsurf -y
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.'
Manage a desk's journal — the persistent memory that survives session boundaries.
Append to `desks/<desk-name>/journal.md` (for a desk in a group folder, `<group>-desks/<desk-name>/journal.md` — look in `desks/` first, then in each `*-desks/` folder). 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>
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.
the next session from walking the same path.
3-5 lines per entry. If you need more, the important context should go on the bench as a separate artifact.
Without a next step, it has to re-derive everything.
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>
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.
the way. Every entry is a stone.
is more useful than silence.
Write for someone who knows nothing about what you just did.
A community-created collection of custom agents, instructions, skills, hooks, workflows, and plugins to supercharge your GitHub Copilot experience.
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like…
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps…
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default,…
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks,…
Use this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like…
Add educational comments to the file specified, or prompt asking for file to comment if one is not provided.
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…