Loading...
Loading...
Found 1,421 Skills
Design and build SuperPlane workflow canvases from requirements. Translates workflow descriptions into canvas YAML with triggers, components, edges, and expressions. Use when the user wants to create a new workflow, build a canvas, design a pipeline, or wire up components. Triggers on "build canvas", "create workflow", "design pipeline", "automate".
Feishu (Lark) API Integration Guide. Use this when users request to "create Feishu apps", "manage base tables", "add collaborators", "generate Feishu reports", "set Feishu permissions" or "automate Feishu operations". Prioritize using MCP tools for real-time interactive operations.
Slack messaging, channels, and notifications - send messages, manage channels, interact with users, upload files, and add reactions. Use for team communication, incident notifications, and workflow alerts.
Use this skill when automating LinkedIn tasks via Rube MCP (Composio): create posts, manage profile, company info, comments, and image uploads. Always search tools first for current schemas.
Check for and apply updates to installed skill branches from upstream.
This skill implements a specific task from a project's ROADMAP.md file. It should be used when the user wants to work on a roadmap action item by its ID (e.g., '1.1', '2.3'). Triggered by requests like '/do-task 1.1', '/do-task 2.3', or 'do task 3.1'. Works alongside the project-init skill (which creates the roadmap) and the checkpoint skill (which commits afterward).
Toolkit client usage for AIClient, AppDBClient, WorkflowClient, and CodeEngineClient.
Automatically create a PR to register insights, conventions, and best practices obtained from the current project as rules in the TBSten/skills repository. It runs the entire end-to-end process: collecting insights from the project's CLAUDE.md, .claude/rules/ directory and codebase, packaging them as reusable Claude Code rules, and creating the PR. Rules are files stored in .claude/rules/, and unlike skills, they do not require frontmatter. RULE.md serves as the main rule body, while detailed documentation (<rule-name>.md / <rule-name>.ja.md) is placed directly under the rules/ directory. Use when the user requests: "Register insights as rules", "contribute rule", "Share this rule", "Register as a rule", "Compile rules into a PR", "Turn this convention into a rule", "Turn best practices into rules". gh CLI and git must be installed.
Prepare advisors for client review meetings by assembling context packages, performance summaries, drift analysis, talking points, and meeting agendas. Use when the user asks about preparing for a client review, building a pre-meeting checklist, generating talking points for an upcoming meeting, identifying allocation drift before a review, automating review prep workflows, or assembling a meeting package with exhibits. Also trigger when users mention 'client meeting prep', 'review preparation', 'what should I discuss with my client', 'proactive recommendations', 'life event triggered review', 'meeting agenda', or 'compliance pre-check before review'.
Testmo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Testmo data.
Code42 integration. Manage data, records, and automate workflows. Use when the user wants to interact with Code42 data.
Kooomo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kooomo data.