Menu
Search and retrieve past notes — answer questions from the vault
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Log a work achievement as a linked note in the vault — for performance reviews
End-of-day check-in — pulls GitHub activity, compares to existing logs, and creates missing entries
Log a concrete task with an optional deadline — surfaces in daily briefings
Morning planning session - reads recent vault activity, flags urgent items, plans the day
Initialise claudia for a new user — walks through prerequisites, then uses the Obsidian CLI to set up the vault
Weekly review - flags forgotten ideas/tasks, summarises the week
| name | recall |
| description | Search and retrieve past notes — answer questions from the vault |
| argument-hint | <what you want to find or know> |
Search the vault and answer a question. Today: !date +%Y-%m-%d.
Input: $ARGUMENTS
If $ARGUMENTS is empty, ask: "What do you want to find?"
Analyse the query and determine the search strategy:
after: / before: filters (e.g. "last week" → after:YYYY-MM-DD)tag:work/shipped, "decisions" → type:decision)Run one or more searches:
obsidian search query="[terms and filters]"
Also check Atlas files (Work.md, Ideas.md, Tasks.md, Knowledge.md) if the query is broad (e.g. "what did I do this week").
Read the top matching notes (up to 10). For each, read the full note content.
Synthesise an answer:
[[note-name]] linksIf the results are extensive, offer: "Want me to narrow this down or go deeper on any of these?"
Keep the answer concise. The user wants information, not a lecture.