Loading...
Loading...
Found 106 Skills
Capture and organize knowledge in workspace platforms. Structures information into wikis, databases, and connected knowledge graphs.
Extract decisions and learnings from Claude session transcripts. Triggers: "extract learnings", "process pending", SessionStart hook.
AgentDB memory system with HNSW vector search. Provides 150x-12,500x faster pattern retrieval, persistent storage, and semantic search capabilities for learning and knowledge management. Use when: need to store successful patterns, searching for similar solutions, semantic lookup of past work, learning from previous tasks, sharing knowledge between agents, building knowledge base. Skip when: no learning needed, ephemeral one-off tasks, external data sources available, read-only exploration.
Extracts valuable learnings, patterns, and workflows from conversations and persists them as reusable skill files. This skill should be used when a complex problem was solved, a valuable workflow was discovered, or the user explicitly requests to capture knowledge as a skill.
Analyze recent conversation context and capture learnings to project knowledge files (for project-specific insights) or skills/commands/subagents (for cross-project patterns). Use when the user asks to "capture this learning", "update the docs with this", "remember this for next time", "document this issue", "add this to CLAUDE.md", "save this knowledge", or "update project knowledge". Also triggers after resolving build/setup issues, discovering non-obvious patterns, or completing debugging sessions with valuable insights.
Create narrative lore entries that transform technical work into mythological stories. Use when generating agent memory, documenting changes as narrative, or building persistent knowledge through storytelling.
Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers: brain/ modifications, "add to brain".
Update documentation based on lessons learned. Use after completing work to capture learnings and prevent future issues.
Capture technical breakthroughs and transform them into actionable, reusable documentation. Use this skill when the user has achieved a significant technical insight, solved a hard problem, discovered a non-obvious solution, or wants to document a breakthrough moment. Also trigger when the user mentions "eureka", "breakthrough", "document this insight", "capture this discovery", or wants to turn a technical win into reusable knowledge.
MindOS is the user's local knowledge assistant and shared knowledge base. It keeps decisions, meeting notes, SOPs, debugging lessons, architecture choices, research findings, and preferences available across sessions and agents. 更新笔记, 搜索知识库, 整理文件, 执行SOP/工作流, 复盘, 追加CSV, 跨Agent交接, 路由非结构化输入到对应文件, 提炼经验, 同步关联文档. NOT for editing app source, project docs, or paths outside the KB. Core concepts: Space, Instruction (INSTRUCTION.md), Skill (SKILL.md); notes can embody both. Trigger on: save or record anything, search for prior notes or context, update or edit a file, organize notes, run a workflow or SOP, capture decisions, append rows to a table or CSV, hand off context to another agent, check if something was discussed before, look up a past decision, distill lessons learned, prepare context for a meeting, quick-capture to staging area, organize inbox, check knowledge health, detect conflicts or contradictions, find stale content. Chinese triggers: 帮我记下来, 搜一下笔记, 更新知识库, 整理文件, 复盘, 提炼经验, 保存, 记录, 交接, 查一下之前的, 有没有相关笔记, 把这个存起来, 放到暂存台, 整理暂存台, 知识健康检查, 检测知识冲突. Proactive behavior — do not wait for the user to mention MindOS: (1) When user's question implies stored context may exist (past decisions, previous discussions, meeting records) → search MindOS first, even if they don't explicitly mention it. (2) After completing valuable work (bug fixed, decision made, lesson learned, architecture chosen, meeting summarized) → offer to save it to MindOS for future reference. (3) After a long or multi-topic conversation → suggest persisting key decisions and context.
Set up a new Obsidian knowledge base with the LLM Wiki pattern. Use when the user wants to create a wiki, second brain, personal knowledge base, initialize a vault, or says "onboard", "set up", "new wiki", or "new vault".
Use when working with Obsidian vaults, markdown notes with [[wikilinks]], ![[embeds]], callouts (> [!type]), YAML frontmatter/properties, #tags, block IDs (^id), ==highlights==, %%comments%%, Obsidian CLI commands (obsidian create/read/append/search/move/tags/daily/etc.), vault organization (PARA, MOC, flat+tags, Johnny Decimal), folder restructuring, daily notes, templates, task management, backlink analysis, or any file operations in an Obsidian vault directory. Trigger this skill whenever the user mentions Obsidian, .md files inside an Obsidian vault, knowledge base organization, or note-taking workflows — even if they don't explicitly say "Obsidian".