Loading...
Loading...
Found 161 Skills
Use when the agent needs access to information beyond its training data — knowledge sources, RAG pipelines, or grounding data.
Apply the Knowledge-Based View (Grant, 1996) and Nonaka and Takeuchi's SECI model to analyze how organizations create, transfer, and integrate knowledge for competitive advantage. Use this skill when the user needs to design knowledge management systems, understand why knowledge transfer fails across teams, evaluate knowledge creation processes, or when they ask 'how do we capture tacit knowledge', 'why does knowledge stay siloed', or 'how can we turn individual expertise into organizational capability'.
Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
Build and maintain a research repository that makes findings findable, reusable, and cumulative across the organization.
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, editing, or linting any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge__*` tool call (`exec`, `search`, `write`, `edit`, `lint`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.
Intelligent Q&A Appender that appends Q&A content from conversations to existing notes or creates new independent cards. Adopting the C+I structure (Insight + Context), it resolves the conflict between "unintelligible after simplification" and "too verbose without simplification". Triggers: /qa, /ask
Structured web research workflow that ensures research results are incrementally saved to files, preventing loss due to session truncation. This skill is triggered when users say "research", "search for information", "help me look up", "learn about", or "latest information".
Use this skill when the user types "/notes" or "@notes" with phrases like "save this", "document this", "file this under <project/client>", "extract decisions", "extract action items", or "update notes from this discussion". The skill spawns the notes-librarian subagent to extract durable knowledge and file it into the right Docmost page using the existing workspace structure. Falls back to a configured inbox page when confidence is low.
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
ADBPG Knowledge Base Management: Create knowledge bases, upload documents, search, Q&A. Triggers: "knowledge base", "document library", "document upload", "knowledge search", "RAG", "Q&A", "embedding", "ADBPG", "AnalyticDB PostgreSQL"
Pack, share, and load context using Epismo context packs. Trigger on: 'pack this', 'new pack', 'get <id>', 'read <alias>', 'load my context', 'what context do I have', 'restore session', 'save this context', 'share with my team', 'pack this up', 'hand this off', 'publish this guide', 'organize my packs', or any intent to persist or retrieve knowledge across tools or sessions.
Persistent memory system for Claude Code. Two-layer architecture (hot cache + knowledge wiki), safety hooks, /close-day end-of-day synthesis. Zero external dependencies.