Menü
Look up whether Justin has already done something he may have forgotten.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when Justin asks you to search, read, write, or manage notes in the vault, OR when performing structural/physical vault maintenance (hygiene, task archiving, capitalization healing, link repair, and nightly cron plumbing).
Run vault compile-inputs — Phase 0 apply Ready to Apply, then phased Readings/Sources/Meetings/Others.
Interactive daily wrap-up: 1. Input candidates (Slack/email); 2. Discovered contacts; 3. Work log draft/write; 4. Next day's calendar preview.
Master Justin's automated note-taking, ingestion, and logging pipeline (Brain Feeds Ingest). Coordinates email forwarding, Linear reactions, Telegram bookmarks, and central vault logging/entity integration.
Manage and operate the Obsidian Semantic Pointer CLI for on-demand historical bridging, semantic search, and context pruning.
Master conventions for chronological logs: governs Daily Notes, Meetings, and incoming Inputs (Emails, Slack, Readings).
| name | did-i-already-do-this |
| description | Look up whether Justin has already done something he may have forgotten. |
| triggers | ["did I already do X","have I done X","did I send / write / finish / complete X","did I ever X"] |
Justin captures completed work, appointment details, and correspondence in Obsidian, Gmail, or Google Calendar. Check in this order:
Use the obsidian skill to search notes. Work logs, meeting notes, and project notes are the most likely places. Search by keyword; also check dated work log entries if a rough timeframe is known. Include filed query syntheses (category: [[Thoughts]] notes with ## Question sections) as search targets.
When searching for bookings, appointments, confirmations, or correspondence, query the Google Workspace API:
python3 ~/.hermes/skills/productivity/google-workspace/scripts/gws_multi.py --account all calendar list --start <YYYY-MM-DD>T00:00:00-04:00 --end <YYYY-MM-DD>T23:59:59-04:00 --max 100
python3 ~/.hermes/skills/productivity/google-workspace/scripts/gws_multi.py --account all gmail search "Keywords" --max 10
python3 ~/.hermes/skills/productivity/google-workspace/scripts/gws_multi.py --account <account> gmail get <id>
Use session_search to scan past conversation transcripts. Useful if the thing was discussed or decided here but may not have been formally captured anywhere.