recall

スター3

フォーク0

更新日2026年3月24日 17:24

Search and retrieve past notes — answer questions from the vault

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

ソース

iainmaitland88

iainmaitland88/claudia

ダウンロード

If $ARGUMENTS is empty, ask: "What do you want to find?"
Analyse the query and determine the search strategy:
- By topic: extract key terms, search note content
- By date range: convert to after: / before: filters (e.g. "last week" → after:YYYY-MM-DD)
- By tag: map to known tags (e.g. "what I shipped" → tag:work/shipped, "decisions" → type:decision)
- By project: search for the project note name
- By ticket: search for the Jira ticket ID in content or frontmatter
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:
- Lead with the direct answer to the question
- Reference source notes with [[note-name]] links
- Include dates and tags for context
- If the query spans a time range, organise chronologically
- If nothing matches, say so clearly — don't fabricate
If 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.

このリポジトリの他の Skills

同じリポジトリ

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:
- By topic: extract key terms, search note content
- By date range: convert to after: / before: filters (e.g. "last week" → after:YYYY-MM-DD)
- By tag: map to known tags (e.g. "what I shipped" → tag:work/shipped, "decisions" → type:decision)
- By project: search for the project note name
- By ticket: search for the Jira ticket ID in content or frontmatter
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:
- Lead with the direct answer to the question
- Reference source notes with [[note-name]] links
- Include dates and tags for context
- If the query spans a time range, organise chronologically
- If nothing matches, say so clearly — don't fabricate
If 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.