Loading...
Loading...
Found 22 Skills
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.
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.
Processes a new source from raw/ into the wiki. Activates when the user asks to ingest, process, add, or incorporate a source into the knowledge base.
Feishu knowledge base navigation. Activate when user mentions knowledge base, wiki, or wiki links.
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.
Guides technical support engineering—customer ticket investigation, reproduction, log and API analysis, root-cause isolation, workaround communication, engineering escalation with evidence, and knowledge-base fixes for product bugs and integration issues. Use when debugging a customer-reported issue, writing a repro for engineering, analyzing API errors, drafting technical replies, or improving support runbooks—not for CS program design, renewals, or billing ops (customer-ops-specialist), production incident command (incident-management-engineer), building product features (fullstack-software-engineer), or company-wide crisis statements and launch announcements (communication-lead), or exec/VIP and community escalation program design (community-executive-escalations-program-manager). Product how-to, macros, and ticket triage without deep debugging: product-support-specialist.
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).
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.
Generate, grade, and adapt Vietnamese AI practice exams from a knowledge base. Use for de on tap, mock exam, MCQ, multi-select, fill-in-blank, rubric grading, and updating learner knowledge profiles.
Interact with Heptabase using the CLI to create, read, and edit notes, journals, tags, and cards, and to browse AI Tutor goals, courses, and lessons. Use when the user asks to manage their Heptabase knowledge base, search cards, work with journals or tags, or read AI Tutor content.
Read content from Feishu cloud documents or knowledge bases and analyze document structure. It is used when users request to "view", "read", "analyze", "fetch", "open" Feishu documents or knowledge bases. It supports reading via document ID, knowledge base Token or URL. Markdown is used as the intermediate format and stored in the /tmp directory.
Use Orchata MCP tools to search, browse, and manage knowledge bases programmatically. For MCP-connected environments only.