Loading...
Loading...
Found 1,128 Skills
ZeroBounce integration. Manage data, records, and automate workflows. Use when the user wants to interact with ZeroBounce data.
Bancontact Payconiq Company integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bancontact Payconiq Company data.
Tutor LMS integration. Manage data, records, and automate workflows. Use when the user wants to interact with Tutor LMS data.
Structurizr integration. Manage data, records, and automate workflows. Use when the user wants to interact with Structurizr data.
Create business process and integration diagrams using PlantUML syntax with BPMN, EIP, and Lean Mapping stencil icons. Best for workflow automation, approval processes, message-based integration patterns, ETL pipelines, and value stream mapping. NOT for simple flowcharts (use mermaid) or UML activity diagrams (use uml skill).
Update GSD to latest version with changelog display
飞书邮箱（Mail）操作。查看邮件、发送邮件、回复、转发、管理草稿、批量获取、线程、过滤。 当用户请求"发邮件"、"看邮件"、"查邮件"、"回复邮件"、"转发邮件"、"邮件草稿"、"收件箱"、 "feishu mail"、"lark mail"、"未读邮件"时使用。
Yugabyte integration. Manage data, records, and automate workflows. Use when the user wants to interact with Yugabyte data.
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.
Copperx integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Copperx data.
Phase 1 of the Issue Workflow - Translate the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Phase 2's responsibility). This phase is also the only official decision point for determining whether to take the fast track or the standard path: first read the relevant code based on the user's description, and if the root cause can be identified at a glance and the changes required are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "log this bug", "I found a problem". This is the starting point of the issue workflow with no pre-requisites.
Manage a team's tasks and use Box as the file storage backend