Loading...
Loading...
Found 7,115 Skills
Guidance for creating standalone CLI tools that perform neural network inference by extracting PyTorch model weights and reimplementing inference in C/C++. This skill applies when tasks involve converting PyTorch models to standalone executables, extracting model weights to portable formats (JSON), implementing neural network forward passes in C/C++, or creating CLI tools that load images and run inference without Python dependencies.
Use the Docyrus CLI (`docyrus`) to interact with the Docyrus platform from the terminal. Use when the user asks to authenticate, list apps, query/manage data records (`ds`), manage dev app data source schema objects (`studio`), send API requests, switch environments/tenants/accounts, or discover OpenAPI specs via the `docyrus` command-line tool. Triggers on tasks involving docyrus CLI commands, terminal-based Docyrus operations, `docyrus ds list`, `docyrus studio`, `docyrus discover`, `docyrus auth`, `docyrus env`, or shell-based Docyrus workflows.
Search Feishu cloud docs, messages, and apps. Use this when users request "search docs", "search messages", "search apps", "find docs", "look up", "search docs", "find Feishu docs", or "are there any docs about xxx". Also applicable for: users wanting to find Feishu docs or Wiki on a specific topic, retrieve message records by keywords, or find internal apps. The search API must use a User Access Token, and this skill includes a complete pre-authentication check process.
Skill for using Paperclip — open-source orchestration platform for running autonomous AI-agent companies with org charts, budgets, governance, and heartbeats.
Use the Notion CLI (`ntn`) to interact with the Notion API, manage workers, and upload files. Use when the user asks to "call the Notion API", "deploy a worker", "upload a file to Notion", "create a page", "query a database", or any task involving the `ntn` command.
Feishu chat browsing, message interaction and group chat management. View chat history, obtain group chat historical messages, search group chats, get message details, Reaction emoji responses, Pin pin/unpin, delete messages, group chat information query and management (obtain/update/dissolve/member management). Supports two modes: regular groups and topic groups, with automatic thread reply retrieval for topic groups. All commands require a User Token. Use this skill when users request "view chat history", "check messages with someone", "group chat history", "group messages", "search group chats", "check group information", "group members", "recent messages", "chat history", "Reaction", "emoji response", "pin message", "Pin", "delete message", "get message", "message details", "what was talked about with whom", "what was discussed in the group", "summarize group messages", "topic replies", "thread replies", or "thread replies". It also applies to scenarios where users provide a group chat name or chat_id and want to browse its messages, even if they don't explicitly say "chat history". This skill should be used when users want to know what a group has been discussing recently, find conversation content with someone, or perform interactive operations on messages.
HTTP clients for frontend and Node.js. Covers Axios, Fetch API, ky, and ofetch. Includes interceptors, error handling, retry logic, and auth token management. Use for configuring API clients and HTTP communication. USE WHEN: user mentions "HTTP client", "Fetch API", "ky", "ofetch", "HTTP wrapper", "retry logic", "token refresh", asks about "which HTTP client to use", "HTTP request library", "API client setup", "request interceptors" DO NOT USE FOR: Axios-specific questions - use `axios` instead; GraphQL - use `graphql-codegen` instead; tRPC - use `trpc` instead; WebSocket connections
SuprSend CLI is a command-line interface tool for managing your SuprSend account and resources. It provides a convenient way to interact with the SuprSend API, allowing you to perform various operations such as managing workspaces, users, workflow, templates and more.
Use DingTalk Workspace CLI (dws) to manage DingTalk contacts, calendar, todos, attendance, approvals, and more from the command line or AI agent workflows.
Use this skill whenever the user needs backend infrastructure management — creating database tables, running SQL, deploying serverless functions, managing storage buckets, deploying frontend apps, adding secrets, setting up cron jobs, checking logs, or running backend diagnostics — especially if the project uses InsForge. Trigger on any of these contexts: creating or altering database tables/schemas, writing RLS policies via SQL, deploying or invoking edge functions, creating storage buckets, deploying frontends to hosting, managing secrets/env vars, setting up scheduled tasks/cron, viewing backend logs, diagnosing backend health or performance issues, or exporting/importing database backups. If the user asks for these operations generically (e.g., "create a users table", "deploy my app", "set up a cron job", "check backend health") and you're unsure whether they use InsForge, consult this skill and ask. For writing frontend application code with the InsForge SDK (@insforge/sdk), use the insforge skill instead.
WeCom to-do item editing skill, which supports creating, updating, deleting to-dos and changing the user's task processing progress status. It is applicable to scenarios requiring write operations on to-dos, such as when users say "Help me create a to-do", "Assign this task to Zhang San", "Mark the to-do as completed", "Delete that to-do", "Help me set a reminder", "Update the to-do content", "Change the reminder time to next week", "Accept this to-do", "Reject this to-do", etc.
WeCom schedule management skill. It meets users' various management needs for WeCom schedules. Use this skill when users need to: (1) Query the schedule list within a specified time range or obtain detailed schedule information (title, time, location, participants, etc.), (2) Create new schedules and set reminders, participants, etc., (3) Modify information such as title, time, location of existing schedules or cancel schedules, (4) Add or remove schedule participants, (5) Query the busy/free status of multiple members and analyze common free time slots to arrange meetings.