Loading...
Loading...
Found 6 Skills
Query and sync YApi interface documentation. Use when user mentions "yapi 接口文档", YAPI docs, asks for request/response details, or needs docs sync. Also triggers when user pastes a YApi URL that matches the configured base_url.
Use after PR hardening is complete, to sync knowledge across global documents and prepare the next phase
Bidirectional conversion between Markdown and Feishu (Lark) documents using md2fs and fs2md CLI tools. Use this skill whenever the user mentions Feishu, Lark, 飞书, feishu.cn URLs, md2fs, fs2md, md-lark-converter, pasting documents to Feishu, exporting from Feishu, converting to/from Feishu format, syncing content with Feishu, setting up Feishu cookies, or any workflow involving Markdown and Feishu documents — even if they don't explicitly say 'convert'. Also trigger when the user shares a feishu.cn or lark link.
Audits docs/en/specifications/, docs/en/issue/, and docs/en/policy/ for English documents that are missing a Korean translation in docs/ko/, or where the Korean version appears out of date compared to the English source, then creates or updates those translations. Use this to keep docs/ko/ in sync. Triggered by "sync docs", "번역 동기화", "update translations", "sync translations", or "mirror docs".
MindOS Knowledge Base Operation Guide (Chinese) for Agent tasks on local markdown/csv knowledge bases. It should be automatically triggered whenever tasks involve note files, SOP/workflow documents, profile/context documents, CSV tables, knowledge base organization, cross-Agent handover or decision synchronization, and are executed via the MindOS MCP tool. Typical requests include "update notes", "search knowledge base", "organize files", "execute SOP", "review according to team standards", "hand over tasks to another Agent", "synchronize decisions", "append to CSV", "retrospect this conversation", "extract key experiences", "adaptively update retrospective results to corresponding documents", "route this information to corresponding files", "synchronously update all related documents", etc.; it should be triggered even if the user does not explicitly mention MindOS.
Update existing app design document based on codebase changes and project evolution