skills/pickmeup/SKILL.md
--- tldr: Resurface recent activity to re-enter a project after time away category: observation --- # /eidos:pickmeup Re-entry point after days away — surface what happened, what's open, and where you left off. ## Usage ``` /eidos:pickmeup [days] ``` - `days` — how many days back to look (default: 3) ## Instructions ### 1. Determine Window Parse the optional `days` argument (default 3). Calculate the start date. ### 2. Gather Git Activity ```bash # Commits in the window, grouped by dat
npx skillsauth add agenticnotetaking/eidos skills/pickmeupInstall 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.
Re-entry point after days away — surface what happened, what's open, and where you left off.
/eidos:pickmeup [days]
days — how many days back to look (default: 3)Parse the optional days argument (default 3).
Calculate the start date.
# Commits in the window, grouped by date
git log --since="<days> days ago" --format="%h %ad %s" --date=short
# Branches touched in the window
git log --since="<days> days ago" --all --format="%D" | grep -oE 'task/[^ ,]+' | sort -u
# Files changed in the window
git log --since="<days> days ago" --name-only --format="" | sort -u
Group commits by date, most recent first. Only show dates where something actually happened — skip silent days.
Scan memory/ for files with timestamps inside the window:
plan -)
session -)decision -)solved -)todo -)Match timestamps in filenames (YYMMDDHHMM) against the window.
Same as /eidos:next but summarised, not interactive:
Run date '+%y%m%d%H%M' to get the current timestamp.
Create memory/pickmeup - <timestamp> - <claim>.md (per [[spec - naming - prefixes structure filenames as prefix claim pairs]], e.g. pickmeup - 2602141030 - last 3 days activity.md) with this structure:
---
tldr: Pickmeup for <start date> to <end date>
---
# Pickmeup: <start date> — <end date>
## Timeline
### <date> (<day name>)
- `abc1234` commit message
- [changed-file.md](<path>)
- `def5678` commit message
- => branch `task/feature-name` active
### <earlier date> (<day name>)
- ...
## Plans
### [[plan - YYMMDDHHMM - claim]]
- **Status:** active
- **Progress:** Phase 2 — 3/5 actions done
- **Last action:** description of most recent [x] action
- **Next action:** description of next [ ] action
## Decisions Made
- [[decision - YYMMDDHHMM - claim]] — one-line summary
## Completed
- [[solved - YYMMDDHHMM - claim]]
## Still Open
- [[todo - YYMMDDHHMM - claim]]
- N unprocessed goodjobs
## Where You Left Off
Brief narrative (2-3 sentences) synthesising: what was the focus, what got done, what's the natural next step.
Show the pickmeup content directly in chat. Commit the file.
Then ask:
Ready to pick up where you left off?
1 - Continue active plan
2 - Work on open todo
3 - Something else
What feels right?
memory/pickmeup - <timestamp> - <claim>.mddevelopment
--- 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