Loading...
Loading...
Found 156 Skills
Download paper PDFs from arXiv, extract text and images, and generate detailed paper interpretation notes embedded with original images in the Obsidian vault (similar to AlphaXiv blog style)
Activate when the user mentions their Obsidian vault, notes, tags, frontmatter, or daily notes. Teaches sharp edges and error recovery for the MCP-Obsidian server that tool descriptions alone don't cover.
Orchestrates creation of structured Obsidian notes with markdown, canvas diagrams, and table bases. Use when users ask to create notes, save knowledge, or document concepts in their Obsidian vault. Delegates to specialized format skills.
Activate when the user mentions their Obsidian vault, notes, tags, frontmatter, daily notes, backup, or sync. Route operations across MCP, Obsidian CLI/app actions, and git sync with safe defaults.
Use this skill whenever the user wants Claude to directly interact with their Obsidian vault — reading a note or daily note, writing or appending content, searching vault contents, counting or listing notes, managing tasks, moving or renaming files, finding orphaned notes or broken links. Without this skill, Claude has no way to access vault data or execute vault operations. Treat any request that implies "go into my vault and do X" as a trigger — the user is asking Claude to act, not to explain. Also trigger for vault automation, CLI scripting, or cron-based workflows involving Obsidian, managing sync history, querying Bases, restoring file versions via history, managing bookmarks, or running JavaScript against the Obsidian API. Skip for pure conceptual questions: how Obsidian's GUI works, navigating settings menus, theme or plugin installation via the UI, iCloud/third-party sync conflicts, general Dataview query syntax, keyboard shortcuts, or parsing vault files with external scripts — anything where the user needs an explanation rather than Claude performing a vault operation.
Configure multiple Obsidian environments for development, testing, and production. Use when managing separate vaults, testing plugin versions, or establishing a proper development workflow with isolated environments. Trigger with phrases like "obsidian environments", "obsidian dev vault", "obsidian testing setup", "multiple obsidian vaults".
Export the Obsidian wiki's knowledge graph to structured formats for use in external tools. Use this skill when the user says "export wiki", "export graph", "export to JSON", "export to Gephi", "export to Neo4j", "graphml", "visualize wiki", "knowledge graph export", or wants to use their wiki data in another tool. Outputs graph.json, graph.graphml, cypher.txt (Neo4j), and graph.html (interactive browser visualization) into a wiki-export/ directory at the vault root.
Sync the current project's knowledge into the Obsidian wiki. Use this skill from any project when the user says "update wiki", "sync to wiki", "save this to my wiki", "update obsidian", or wants to distill what they've been working on into their knowledge base. This is the cross-project skill that lets you push knowledge from wherever you are into the vault.
Scan the Obsidian wiki and automatically discover missing cross-references between pages. Use this skill when the user says "link my pages", "find missing links", "cross-reference", "connect my wiki", "add wikilinks", "what pages should be linked", or after any large ingestion to ensure new pages are woven into the existing knowledge graph. Also trigger when the user mentions "orphan pages" in the context of wanting to connect them, or says things like "my wiki feels disconnected" or "pages aren't linked well". This is a write-heavy skill — it actually modifies pages to add links, unlike wiki-lint which just reports issues.
Ingest any raw text data, conversation logs, chat exports, or unstructured documents into the Obsidian wiki. Use this skill when the user wants to process data that isn't standard documents or Claude history — things like ChatGPT exports, Slack threads, Discord logs, meeting transcripts, journal entries, CSV data, browser bookmarks, email archives, or any raw text dump. Triggers on "ingest this data", "process these logs", "add this export to the wiki", "import my chat history from X". This is the catch-all for any text source not covered by the more specific ingest skills.
Enforce consistent tagging across the Obsidian wiki using a controlled vocabulary. Use this skill when the user says "fix my tags", "normalize tags", "clean up tags", "tag audit", "what tags should I use", "tag taxonomy", or whenever you're creating or updating wiki pages and need to choose the right tags. Also trigger when the user asks about tag conventions, wants to add a new tag to the taxonomy, or says "my tags are a mess". Always consult this skill's taxonomy file before assigning tags to any wiki page.
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.