obsidian

Create an Obsidian note documenting a non-code work decision — research, investigation, planning, or design choices. Entirely interview-based with no git context required. Use when the user wants to log a problem they investigated, options they considered, and a decision they reached.

Create a retrospective Obsidian note from a development task. Given a task name and brief background, the AI collects git and code context, interviews the user about decisions and insights, and writes a structured markdown log to the vault. Use when the user wants to document a completed task, feature, or bugfix as a retrospective note.

This skill should be used when the user asks to "write in a human tone", "avoid AI style", "make this sound human", "remove AI patterns", "write naturally", or when asked to write blog posts, articles, emails, social media posts, or any text where sounding human is important.

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.

Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.

Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.

Create a team-facing work log from a development task and push it directly to a shared GitHub repository via gh CLI. Collects git context automatically and asks 2–3 focused questions for weekly team review. Use when the user wants to share what they worked on with their team.