Loading...
Loading...
Found 48 Skills
This skill drafts weekly reports by synthesizing the progress documented in the Obsidian vault. It is suitable for scenarios where users want to generate weekly summaries based on recently created files, previous reports, and project background documents.
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.
Manage notes in Get笔记 via the getnote CLI
Manage knowledge bases in Get笔记 via the getnote CLI
Control Obsidian from the terminal via the Obsidian CLI. Read, create, search, and manage notes, tasks, properties, and more. Includes vault structure commands (orphans, dead ends, backlinks, unresolved wikilinks), Bases, and plugin development.
Log information for future reference. Use when user says "fyi", "remember this", "note that", "for your info".
Processes .athenabrief research packages exported from the Athena note-taking app. This skill should be used when the user uploads a .athenabrief file, mentions Athena briefs, research briefings, exported notes, or asks to work with research packages from Athena. Supports zero-instruction processing where the brief itself contains all necessary context. Always packages final results using the athena-package skill.
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.
Project notes system for preventing AI context loss and reasoning loops. Initialize notes, save notes mid-flow, recover context, migrate messy notes, and resolve lessons. Subcommands: /notebook, /notebook save, /notebook recover, /notebook migrate.
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.
Add notes and learnings to Tim's work knowledge base at Spotify from any Claude Code session
Review reusable project knowledge and decide what belongs in project memory, notepad, or durable docs