Loading...
Loading...
Found 33 Skills
Read, edit, and manage WPS Notes via MCP tools, based on the block document model, with all content exchanged in XML format. Use this when users say "help me check my notes", "search notes", "create a note", "edit note content", "organize tags", or mention WPS Notes, WPS Note, or cloud notes. It also applies to troubleshooting MCP tool call errors (such as BLOCK_NOT_FOUND, EDITOR_NOT_READY).
Official skill for Youdao Cloud Note, supporting basic operations such as note CRUD (Create/Read/Update/Delete), to-do management, web clipping, note search, and folder management. If you need to build a knowledge base or Wiki, please use the youdaonote-llm-wiki skill instead of this skill.
Work with Obsidian vaults (plain Markdown notes) via notesmd-cli. Use when the user asks to create, read, search, list, move, delete notes, manage frontmatter, or interact with their Obsidian vault from the terminal. Works without Obsidian running.
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.
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