source-minelisted

# Skill: /source-mine [source] Turn an account, corpus, or directory you already own into attributed vault notes — the sweep that gets the graph from empty to useful, and the one nobody wants to hand-write twice. **Don't:** write a note without its source and mine date in the body; an unattributed claim is unverifiable a month later and indistinguishable from something you made up. **Don't** mine and synthesize in one pass — extract first, decide what deserves a note second, or the interesting-but-irrelevant all gets written up. **Don't** touch the source: mining is read-only, always. ## Inputs `source` is one of: `github`, `filesystem`, `google`, `chat-history` (ChatGPT / Claude.ai / Perplexity), or `vault` (re-reading for unlinked material). If ambiguous, ask which — the extraction rules differ per source. ## Steps 1. **Read [source-recipes.md](../_lib/source-recipes.md)** for this source's endpoints, extraction targets, and known pitfalls. 2. **Inventory before extracting.** List what exists — repo count, thread count, directory listing — and report the scale. A sweep whose size is unknown at the start silently becomes a sample. 3. **Extract to a scratch list**, not to the vault. One line per candidate: what it is, why it might matter, where it came from. 4. **Check each candidate against the vault** before writing: `obsidian search query='<candidate>' limit=5`. Existing note → append an `## Update — <date>` section. No note → create. 5. **Write the notes.** Route by