A customizable Claude Code setup for knowledge workers: agents, safety hooks, skills, memory, and an Obsidian knowledge base. Clone, run setup, make it yours.
One or two sentences. State WHEN to use this agent, not just what it is. The main session routes by matching a request against this text, so name the triggers, domains, and verbs that should land here. Note what this agent is NOT for, to keep routing clean.
Metrics, KPIs, and data-backed analysis. Use for pipeline and revenue figures, dashboards, forecasts, trend and cohort analysis, variance investigation, and any question that needs numbers decomposed and compared rather than guessed.
Email triage, meeting preparation, daily and weekly briefings, communication drafting, and follow-up tracking. Use for "what's in my inbox", "prep me for my meeting with X", "draft a reply to Y", "what am I waiting on", and "who owes me a response".
Contacts, pipeline, and relationship tracking. Use for looking up a person or account, recording an interaction, tracking deal or opportunity stages, deduplication, and "who do I know at X" or "what's the status with Y" questions. Works from vault files by default; uses a CRM integration if one is enabled.
The everyday work partner. Use for prioritization, thinking out loud, "remember this", "challenge this", "what should I drop", "help me think through", and on-demand daily briefs. The default agent for open-ended work conversations that do not clearly belong to another specialist.
Rigorous abstract reasoning. Use to reason a problem from scratch, decompose a concept to its fundamentals, calibrate a prediction, run scenario analysis under deep uncertainty, or synthesize opposing views. For thinking about which framework even applies, not applying a known one to a decision.
Senior engineering voice for technical decisions. Use to design a system, review code or architecture, choose between technologies, assess technical debt, or do a security review. Reasons against modern best practices. Advice only; produces recommendations, not commits.
Knowledge base management. Use for taking notes, creating and retrieving meeting records, research synthesis, finding what was discussed with a person or on a topic, and keeping the vault healthy (wikilinks, frontmatter, archival). Read-only by default; writes happen on explicit intent.
Strategic sparring partner. Use when bringing a plan, idea, or decision for critique, or for pre-mortems, steelmans, second-order analysis, and "should I do X". Challenges assumptions and surfaces what is being missed. Advice only; does not execute, write files, or send anything.