Loading...
Loading...
Found 4,920 Skills
Add/update tags for tasks
Update GSD to latest version with changelog display
飞书邮箱（Mail）操作。查看邮件、发送邮件、回复、转发、管理草稿、批量获取、线程、过滤。 当用户请求"发邮件"、"看邮件"、"查邮件"、"回复邮件"、"转发邮件"、"邮件草稿"、"收件箱"、 "feishu mail"、"lark mail"、"未读邮件"时使用。
Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as "when a record is created", "trigger daily at", "send an email when", "update the field when", "automate", "workflow", or "flow XML/metadata". This is the only skill for Salesforce Flow generation.
Morning preparation. Calendar lookahead, meeting context loading, open threads from yesterday, active task review. Extends briefing with actionable prep.
Copperx integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Copperx data.
Follow this sub-process when fixing bugs—turn the verbal description of "discovered a problem" into a closed loop of verification and repair, leaving three documents in the middle: issue report, root cause analysis, and repair record. This process adds a buffer between "seeing the problem" and "starting to modify code", avoiding several common pitfalls: the problem description in your mind disappears after modification, fixing only the surface without analyzing the root cause, uncontrollable expansion of repair scope that cannot be traced, and not knowing if the fix is correct without verification after modification. This skill only acts as a router, deciding which of report / analyze / fix to proceed with based on existing outputs. For simple problems that can be identified at a glance, a fast track will be taken, skipping the two middle steps and only keeping the fix-note.
Write or update external guide documents for the project —— dev-guide (for contributors / integrators / downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push when feature-acceptance is completed.
Enter this sub-process when developing new features — turn the vague idea of "adding X capability" into a closed-loop acceptance process, with solution files archived so that both AI and users can later check what was thought and why decisions were made at that time. Trigger scenarios are focused on new capabilities ("develop new features", "add X", "implement XX") and do not address bugs in existing code. This skill only handles routing, deciding which next step to take among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
Manage a team's tasks and use Box as the file storage backend
Implement tasks from a working change. Use when the user wants to start implementing, continue implementation, or work through planned tasks.
Process user-provided patent figures and generate formal drawing descriptions. Use when user says "附图处理", "figure description", "附图说明", "drawings description", or wants to describe patent figures with reference numerals.