norrietaylor

Onboarding wizard — verify MCP connectivity, detect transport, and configure scheduled tasks via Claude Code routines

Synthesize multiple knowledge entries into a cohesive narrative with citations

Contrast internal implementation knowledge against ambient intelligence, find where they meet, and emit a directional assessment (ahead / exposed / decide / confirm)

Generate an ambient intelligence digest from recent feed activity with source suggestions

Produce a knowledge dashboard with recent entries, corrections, expiring soon, stale knowledge, and unresolved items. In team mode, also shows team activity, related entries from teammates, and the review queue.

Compile deep context on a topic by combining semantic search with relationship traversal across 4 retrieval phases

Add, remove, or list monitored feed sources (RSS and GitHub)

Save a URL with an auto-generated summary to the knowledge base

Check the user's Google Calendar for today and the next few days. Use when the user asks about their calendar, agenda, meetings today, what's coming up, next meeting, schedule, or what's on the calendar. Read-only — never creates or modifies events.

Check what's on the user's Gmail plate by triaging unread and recent threads for actionable items. Use when the user asks about email, inbox, what's on their plate, what they owe replies to, or what follow-ups are waiting in email. Also trigger on "check my gmail", "what's in my inbox", or "anything actionable in email".

Check what's on the user's Notion plate by querying task databases, mentions, and waiting-on items. Use when the user asks about Notion tasks, follow-ups, what's assigned to them in Notion, what they're waiting on from others, or what they owe replies to in Notion.

Deep-dive investigation into a technical domain's history, architecture evolution, key people, and decisions. Use when asked to understand "how X works", "history of Y", "who built Z", or when needing comprehensive context on a codebase area, feature, or system.

Check what's on the user's GitHub plate by querying notifications and open threads, then dig into each to determine required action. Use when the user asks about GitHub notifications, what needs their attention, what's on their plate, pending issues or PRs, or what they should reply to.

Check what's on the user's GitLab plate by querying todos and open threads, then dig into each to determine required action. Use when the user asks about GitLab notifications, what needs their attention, what's on their plate, pending issues or MRs, or what they should reply to.

Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.

Reference for the Obsidian CLI (v1.12+). Provides command syntax, parameter patterns, output formats, and gotchas. Use when running obsidian commands, writing scripts that call the CLI, or automating vault operations.