Loading...
Loading...
Found 36 Skills
Maintains persistent codebase knowledge across sessions through a structured knowledge graph stored in a local Obsidian vault (.doctrack/). Use this skill whenever you have just made meaningful code changes (new features, modified components, refactoring, bug fixes) to update the project's documentation. Also use it when the user asks to document code, update docs, sync documentation, initialize documentation for an existing project, or when you want to understand the existing codebase structure at the start of a session. This skill should be used proactively after any significant code modification — don't wait for the user to ask. If you changed code, update the docs. Think of it as your long-term memory system: read before working, write after changing. Also use this when a user says "doctrack init", "doctrack refresh", "refresh docs", "update docs", "sync docs", "initialize docs", "document this project", or wants to bootstrap documentation for a codebase that has no .doctrack/ vault yet.
Prepare for upcoming meetings — pulls Cal.com bookings, researches participants, audits previous sessions from Obsidian vault, and creates prep notes. Also links prep notes to post-meeting session notes.
Generate a dedicated Obsidian learning vault for any certification, course, or study goal. Creates structured notes with domains, concepts, lessons, scenarios, MoCs, dataview queries, action items, and multiple navigation paths. Inspired by the genome vault pattern. Use when the user wants to create a study vault, learning vault, certification prep vault, or structured knowledge base for a learning goal.
Manage Obsidian vault for persistent knowledge storage, search, and retrieval
Ingest GitHub Copilot CLI session history into an Obsidian wiki as distilled knowledge pages. Use this skill when the user wants to capture their Copilot CLI sessions into a personal wiki — extracting architecture decisions, debug notes, and patterns into searchable Obsidian pages. Triggers on phrases like "ingest my copilot sessions into obsidian", "add my copilot history to my wiki", "pull my copilot session history into the vault", "capture what I've learned from copilot into obsidian", "just the new sessions since last time", or "mine patterns across my copilot sessions". Also triggers when the user mentions session-store.db, ~/.copilot/session-state, or VS Code copilot-chat transcripts in the context of building a wiki or knowledge base. Does NOT trigger for general copilot usage questions, searching sessions, or backing up history.
Review and promote staged wiki pages to their final locations. Use when WIKI_STAGED_WRITES=true and the user says "/wiki-stage-commit", "review staged pages", "commit staged writes", "promote staged pages", "approve staged changes", or "what's waiting in staging". Shows each staged file, lets the user accept or reject it, and moves accepted files to their final wiki locations. Rejected files are moved back to _raw/ for manual editing.
Interview the user through their OWN investment screening checklist - you ASK the questions one at a time and the USER answers and clears each gate; the tool never answers, never invents questions, and never checks a gate off. The questions are James's own and live in his Obsidian vault (the source of truth); ask exactly what is there. A decision-support thinking tool, not financial advice. Complements /munger. Use when the user invokes /investment-checklist, says "run this through my investment checklist", "screen this idea/stock/ticker", or pastes a thesis/ticker to be screened.
Scaffold a new Obsidian vault with pre-configured settings, keymaps, and core plugins. Use when the user wants to "set up a new Obsidian vault", "create an Obsidian vault", or "replicate my Obsidian setup".
Switch between multiple Obsidian wiki vault profiles. Use this skill when the user says "/wiki-switch NAME", "switch to my work wiki", "switch vault", "change wiki", "which wiki am I on", "list my wikis", "show my vaults", "create a new vault config", or "add a new wiki profile". The skill manages named config files at ~/.obsidian-wiki/config.NAME and activates one by symlinking it to ~/.obsidian-wiki/config.
Import a wiki knowledge graph from a graph.json export file into the current vault. Use this skill when the user says "import wiki", "import from export", "load graph.json", "import vault", "/wiki-import", or wants to transfer pages from one vault to another using the output of wiki-export.
Scaffold and operate Claude Blog Brain, a source-cited Obsidian brain for blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill. Use when the user says "claude-blog-brain", "Claude Blog Brain", "create a blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill brain", "import sources", "synthesize plan", "render report", or wants a persistent vault-backed operating system for blog content creation, optimization, and management dual-optimized for Google rankings (E-E-A-T, the 2026 core updates) and AI citations (GEO/AEO), spanning writing, rewriting and freshness, SERP-informed briefs and outlines, editorial calendars and strategy, semantic topic clusters, schema and internal linking, multilingual publishing, the FLOW framework, factchecking, personas, distribution, and the blog delivery contract, grounded in the claude-blog skill.
Manage Obsidian vaults with full support for Obsidian Flavored Markdown — wikilinks, embeds, callouts, YAML properties, Dataview queries, Canvas, and Bases. Organize notes using MOCs (Maps of Content), atomic note principles, and consistent folder/tag taxonomies. Always ask the user where to save before creating notes.