PromptWorks/kb/SKILL.md

name

description

kb

Vault-first recall. Search Daniel's Obsidian KB (D:\Repos\Obsidian) BEFORE WorkIQ/M365, Azure DevOps, IcM, or the browser. Use for any lookup: "who is X", "what's my/his alias, SC-ALT, email, ID, manager, office", "what did we decide about X", "when did we meet about X", "what is <acronym>", "remind me", "do we know", "look it up", "check the KB", plus anything about squads, Connects, RISE, meetings, daily notes, or people Daniel works with.

kb — vault-first recall

The Obsidian vault at D:\Repos\Obsidian is the system of record for durable facts. External systems (WorkIQ/M365, ADO, IcM, browser) are the fallback, not the first stop. 247 notes / ~2.3 MB — searching it is effectively free, so there is never a latency excuse to skip it.

Read D:\Repos\Obsidian\AGENTS.md §5.2 (query) for the full protocol. Its layer rules bind you: never edit anything in the Raw layer (Transcripts/, 00 - Chats/, 02 - Meetings/*.vtt, 07 - AI Sessions/).

Search ladder — stop as soon as you have the answer

1. Quick Reference — 05 - Resources\Quick Reference.md. The cheat sheet for accounts, aliases, SC-ALT, Graph IDs, org/management chain, team rosters, tooling handles. Most "simple thing" questions end here. Read it before anything else.
2. MOC hubs — meta\moc\_index.md, then people.md, connects.md, and the squad MOCs (c3-omr-reliability-tooling.md, c4-sre-core.md).
3. Entity pages — 03 - Squads\<Squad>\02 - People.md, 04 - Decisions.md, 05 - Open Questions.md, 06 - Glossary.md.
4. Full-text search — use the grep tool (ripgrep), case-insensitive, scoped to D:\Repos\Obsidian. Search the person/term AND its likely aliases (first name, alias, email local-part, acronym). Batch several grep calls in one response rather than probing one at a time.
5. Filename / date search — use glob for dated material: 01 - Daily\YYYY-MM-DD.md, 02 - Meetings\YYYY-MM-DD - *\summary.md, 00 - Chats\YYYY-MM\*.md.
6. Past AI sessions — 07 - AI Sessions/, or the richer sessql MCP (find_sessions_hybrid) when the answer was likely worked out in an earlier session rather than written to a note.

Answering

• Cite the notes. Name the specific file(s) the answer came from, as [[wikilink]] or a path. An uncited recall answer is not acceptable.
• Never fabricate. If the vault is silent, say so explicitly.
• Prefer specific over stale. If two notes conflict, trust the one with the newer updated: frontmatter and say the two disagree.

On a miss

State plainly what you searched and that the vault came up empty, then escalate to the external system (WorkIQ/M365, ADO, IcM, browser). Do not silently fall through — the user needs to know the KB has a gap.

Closing the loop (this is what makes it compound)

When you resolve a durable, reusable fact from an external system that the vault should have known:

1. Offer to write it back. Do not write silently — ask first (AGENTS.md §5.2 step 4).
2. Route it: identity/account/org facts → append to the right table in 05 - Resources\Quick Reference.md; a person → meta\moc\people.md or a person page; a squad decision → that squad's 04 - Decisions.md; anything else durable → a new type: resource page in 05 - Resources\.
3. Bump updated: in frontmatter, add a sources: entry, and append a one-line entry to meta\log.md per AGENTS.md §7.

Facts that are personal preferences or standing behavioral rules belong in Scout memory (m_remember) instead of the vault.