Loading...
Loading...
Found 17 Skills
Use this skill when the user wants to detach, archive, purge, or otherwise change the lifecycle state of an Obsidian project knowledge base.
Design, create, and configure orq.ai Agents with tools, instructions, knowledge bases, and memory stores. Use when building new agents, attaching KBs or memory, writing system instructions, selecting models, or setting up RAG pipelines. Do NOT use for debugging existing agents (use analyze-trace-failures) or comparing agents across frameworks (use compare-agents).
Feishu knowledge base navigation. Activate when user mentions knowledge base, wiki, or wiki links.
Show the current state of the wiki — what's been ingested, what's pending, and the delta between sources and wiki content. Use this skill when the user asks "what's the status", "how much is ingested", "what's left to process", "show me the delta", "what changed since last ingest", "wiki dashboard", or wants an overview of their knowledge base health and completeness. Also use before deciding whether to append or rebuild. Includes an insights mode triggered by "wiki insights", "what's central", "show me the hubs", "central pages", "what's connected", "wiki structure" — analyzes the shape of the wiki itself to surface top hubs, cross-domain bridges, and orphan-adjacent pages.
This skill should be used when docs-researcher agent needs guidance on "how to search documentation", "WebSearch query patterns", "filtering search results", "documentation research strategy", or "creating knowledge files". Provides systematic methodology for effective technical documentation research.
Use Orchata MCP tools to search, browse, and manage knowledge bases programmatically. For MCP-connected environments only.
DingTalk knowledge base and document management operations. This skill is used when users mention "DingTalk Docs", "knowledge base", "create new document", "view document directory", "read document content", "write to document", "update document", "document members", "dingtalk doc", "knowledge base". It supports all document-related operations including creating knowledge bases, querying knowledge base lists, creating new documents/folders, reading/writing document body content, and managing member permissions.
Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when the mission demands. Use when fixing bugs, implementing features, refactoring, investigating flows, or any development task in unfamiliar territory. Triggers on "fix this", "implement this", "how does this work", "investigate this flow", "help me with this code". Do NOT use for greenfield scaffolding, CI/CD, or infrastructure provisioning.
Use Orchata CLI commands to manage knowledge bases from the terminal. For shell/terminal operations only.
Obsidian Knowledge Base Organization Workflow. Trigger scenarios: When users mention "organize Obsidian", "clean up folders", "messy knowledge base", "too many directories", "merge categories". Applicable to: Personal knowledge management, note organization, folder restructuring.
Feishu Message Sending and Document Creation Workflow. Trigger Scenarios: When users mention "send Feishu message", "Feishu document", "notify someone", "send to Feishu", "Feishu notification". Applicable to: Sending Feishu messages, creating Feishu documents, operating Feishu Base, managing Knowledge Base.
Harness Engineering Phase 1 Step 2: Conduct in-depth analysis of project code and fill in the substantive content of each file in the docs/ knowledge base. Use this skill after the directory skeleton is created by harness-step1-create-agents-md. Immediately trigger this skill when the user says "fill document content", "improve docs/ files", "add substantive content to documents", "analyze project and write architecture document", "write ARCHITECTURE.md", or "write technical decision document". Prerequisite: The project already has AGENTS.md and the docs/ directory skeleton (created by harness-step1).