skills/done/SKILL.md
--- tldr: End session with export and merge offer category: utility --- # /eidos:done Structured session end. ## Usage ``` /eidos:done ``` ## Instructions ### 1. Export Conversation Run `/eidos:tomd` to create a session export in `memory/`. ### 2. Offer Reflection ``` Session exported: [[session - <timestamp> - <claim>]] Reflect on this session? (extracts learnings, tasks, incoherences) ``` If yes, run `/eidos:reflect` on the export. ### 3. Update Active Plan If there's an active pl
npx skillsauth add agenticnotetaking/eidos skills/doneInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structured session end.
/eidos:done
Run /eidos:tomd to create a session export in memory/.
Session exported: [[session - <timestamp> - <claim>]]
Reflect on this session? (extracts learnings, tasks, incoherences)
If yes, run /eidos:reflect on the export.
If there's an active plan, add a session summary to its Progress Log:
- <timestamp> - Session end. [Brief summary of what was accomplished]
If any plans are now completed/abandoned, or any todos are solved,
propose archiving them with /eidos:archive (always propose, never move unprompted).
See [[c - archiving moves done files into an archive subdir preserving basename and links]].
Show branch status and offer to merge:
Branch: task/feature-name (N commits)
Merge to main? (y/n)
If yes: git checkout main && git merge --no-ff task/feature-name
development
--- tldr: Check the status of messages you sent to peer inboxes category: core --- # /eidos:outbox Find messages **you sent** to peer repos and report their status. Your sent messages live in the peers' inboxes, not here. So this skill sweeps every registered peer and reads back what became of them. This is the mirror of [[spec - inbox skill - read and act on your own inbox]]. - The inbox is messages others sent **to** you. You own and edit it. - The outbox is messages you sent **to** others.
development
--- tldr: Send a message to a peer repo's inbox category: core --- # /eidos:message Write a message into another repo's `agent-inbox/`. The recipient is a peer repo, addressed by its registered name. See [[spec - agent communication - cross repo inboxes with append only messages and registry resolution]]. ## Usage ``` /eidos:message [recipient repo] [what to say] ``` ## Instructions ### 1. Resolve the recipient - Identify the recipient repo name. Ask if not given. - Resolve its path: `
development
--- tldr: Read and act on your own inbox category: core --- # /eidos:inbox List and work through messages other repos have left in your `agent-inbox/`. You own this inbox. You may edit its files freely. Agents from other repos may push **new** messages into your inbox at any time. They never edit existing files. Only you do. So re-check the inbox. Don't assume it is unchanged since you last looked. See [[c - foreign agents append to an inbox - only the owner edits in place]]. See [[spec - ag
tools
--- tldr: Move done files into archive subdirs (memory/ and agent-inbox/) category: utility --- # /eidos:archive Retire finished files into the `archive/` sibling of their directory. Done `memory/` files into `memory/archive/`, done inbox messages into `agent-inbox/archive/`. A `git mv`, never a rename. The basename is preserved, so wiki links keep resolving. See [[c - archiving moves done files into an archive subdir preserving basename and links]]. ## Usage ``` /eidos:archive [optional fil