obsidian-second-brain

ALWAYS invoke this skill (via the Skill tool) for any web clipping or article extraction request. Extract clean, readable markdown from web pages using the Defuddle CLI tool, stripping navigation, ads, and clutter. Use this skill when someone wants to save web content to their Obsidian vault, clip articles, extract clean text from URLs, convert web pages to markdown, or reduce token usage when processing web content. Also triggers on "web clipper", "save article", "extract webpage", "clean HTML", or "convert URL to markdown". Prefer Defuddle over raw WebFetch for standard web pages, articles, docs, and blog posts.

ALWAYS invoke this skill (via the Skill tool) for any Obsidian canvas or .canvas file request. Create and edit Obsidian canvas files (.canvas) following the JSON Canvas Spec 1.0 with nodes, edges, groups, and visual connections. Use this skill when someone asks about creating or editing Obsidian canvases, building visual knowledge maps, node diagrams, mind maps in Obsidian, connecting notes visually, or working with .canvas files. Also triggers on "JSON Canvas", "canvas file", "visual board", "Obsidian whiteboard", or requests to create visual note connections.

Compile captured Obsidian sources into cited, invalidatable knowledge-page previews and apply an exact reviewed diff. Use for source synthesis, compiled wiki pages, claim provenance, stale compiled knowledge, contradictions, rebuilds, or source privacy purges. Do not use for ordinary note editing, unconstrained summarization, or automatic/scheduled vault mutation.

ALWAYS invoke this skill (via the Skill tool) for any Obsidian Bases or .base file request. Create and edit Obsidian Base files (.base) for database-like views, filters, formulas, and data summaries within your vault. Use this skill whenever someone asks about Obsidian Bases, creating database views, filtering notes by properties, building task trackers, reading lists, project dashboards, or any structured data view in Obsidian. Also triggers on ".base files", "Obsidian database", "note database", "vault database", or questions about filters, formulas, and summaries in the context of Obsidian.

ALWAYS invoke this skill (via the Skill tool) for any Obsidian CLI or terminal automation request. Execute Obsidian vault operations via the official command-line interface (v1.12.4+). Covers reading, creating, searching, and managing notes, tasks, properties, tags, links, daily notes, sync, publish, and plugin/theme development workflows. Use this skill whenever someone asks about Obsidian CLI commands, wants to automate vault operations from the terminal, build shell scripts for Obsidian, manage daily notes programmatically, develop Obsidian plugins/themes with CLI tooling, or integrate Obsidian with AI agents via the CLI. Also use when someone mentions "obsidian" combined with terminal, command line, shell, script, automation, cron, or developer tools.

ALWAYS invoke this skill (via the Skill tool) for any Obsidian markdown syntax or formatting request. Create and edit Obsidian-flavored Markdown files (.md) with wikilinks, embeds, callouts, properties, block references, comments, and other Obsidian-specific syntax. Use this skill whenever someone asks about writing notes in Obsidian, formatting Obsidian markdown, using wikilinks or internal links, embedding files, creating callouts, managing YAML frontmatter/properties, or any Obsidian markdown syntax question. Also triggers on mentions of Obsidian note formatting, block references, nested tags, or Obsidian-specific markdown extensions.

ALWAYS invoke this skill (via the Skill tool) for any qmd semantic search, vector search, or vault indexing request. Local-first semantic search for Obsidian vaults using qmd — combines BM25 full-text, vector semantic search, and LLM re-ranking. Use this skill when someone asks about setting up qmd, configuring vault indexing, choosing between search modes (BM25 vs vector vs hybrid), connecting qmd's MCP server to Claude, troubleshooting search quality, or understanding how qmd works. Also triggers on "semantic search", "vector search", "qmd", "embed vault", "vault indexing", "search my notes by meaning", "find similar notes", or "natural language vault search".

ALWAYS invoke this skill (via the Skill tool) for any PKM methodology or vault organization request. Personal knowledge management methodology for Obsidian vaults — Zettelkasten, PARA, Maps of Content (MOCs), progressive summarization, and atomic notes. Use this skill whenever someone asks about organizing their vault as a second brain, building a knowledge system, creating MOCs or maps of content, linking notes together strategically, applying Zettelkasten or PARA methods, structuring a PKM workflow, deciding where a note should live, or asking "how should I organize this?" in the context of Obsidian. Also triggers on "evergreen notes", "literature notes", "fleeting notes", "permanent notes", "note-taking system", "knowledge graph", "linking my thinking", or "connect my notes".

ALWAYS invoke this skill (via the Skill tool) for any vault health, audit, or organization improvement request. Vault health assessment and ongoing alignment with second-brain best practices. Use this skill when someone asks about improving their vault organization, wants to know if their vault follows best practices, asks "how healthy is my vault", mentions vault drift or inconsistency, wants to audit their knowledge system, or asks about maintaining their second brain over time. Also triggers on "vault health", "organization check", "vault audit", "clean up my vault", "improve my vault", "vault maintenance", "align my vault", "reorganize my vault", or "my vault is messy". Use this proactively when you notice vault organization issues during other vault operations.

ALWAYS invoke this skill (via the Skill tool) for any Obsidian note template or archetype request. Library of proven note templates and archetypes for Obsidian vaults — meeting notes, book reviews, project briefs, weekly reviews, literature notes, permanent notes, and more. Use this skill when someone asks to create a specific type of note (e.g., "meeting note", "book review", "project brief"), wants a template for a recurring note type, asks about frontmatter conventions for different note types, or says things like "set up a template for", "what properties should a X note have", or "create a note for my meeting/book/project/review". Also triggers on "note template", "note archetype", "weekly review template", "daily template", or any request to scaffold a structured note.