Loading...
Loading...
Found 288 Skills
Use Huly platform APIs for swarm communication across tasks, channels, and documents.
Slack: Send messages, search conversations, list channels and users, reply to threads, and add reactions.
Create a holistic experience map showing the full ecosystem of user touchpoints, channels, and relationships.
Generates EventCatalog documentation files (services, events, commands, queries, domains, flows, channels, containers) with correct frontmatter, folder structure, and best practices. Use when user asks to "document a service", "create EventCatalog files", "add an event to the catalog", "document my architecture", "generate catalog documentation", "create documentation for my microservice", or "document a database".
Build with MPP (Machine Payments Protocol) - the open protocol for machine-to-machine payments over HTTP 402. Use when developing paid APIs, payment-gated content, AI agent payment flows, MCP tool payments, pay-per-token streaming, or any service using HTTP 402 Payment Required. Covers the mppx TypeScript SDK with Hono/Express/Next.js/Elysia middleware, pympp Python SDK, and mpp Rust SDK. Supports Tempo stablecoins, Stripe cards, Lightning Bitcoin, and custom payment methods. Includes charge (one-time) and session (streaming pay-as-you-go) intents. Make sure to use this skill whenever the user mentions mpp, mppx, machine payments, HTTP 402 payments, Tempo payments, payment channels, pay-per-token, paid API endpoints, or payment-gated services.
Measure, report on, and optimize marketing performance across channels and campaigns. Trigger on requests for performance dashboards, campaign result analysis, channel metrics review (email, social, paid ads, SEO, content), trend analysis, forecasting, attribution modeling, A/B testing guidance, or actionable optimization recommendations.
WebRTC peer-to-peer communication. Signaling, ICE/STUN/TURN, media streams, data channels, screen sharing, and SFU integration (mediasoup, LiveKit). USE WHEN: user mentions "WebRTC", "video call", "peer-to-peer", "P2P", "screen sharing", "data channel", "STUN", "TURN", "mediasoup", "LiveKit" DO NOT USE FOR: server-to-client streaming - use `sse`; chat messaging - use `socket-io`
NetEase Cloud Music Intelligent Assistant, with model judgment at its core, executes operations via ncm-cli. Core capabilities: Analyze user's liked songs playlist preference profile, develop multi-keyword search strategies, intelligently recommend playlists/albums/singles (including two-layer recommendation explanations), playback control (play/pause/next track/volume/queue), manage scheduled push tasks, push recommendation results to IM channels like Feishu via OpenClaw, create and add to playlists. Trigger conditions (activate if any is met): - Messages contain "NetEase Cloud" or "Cloud Music" - User wants to listen to music, needs playlist recommendations, or looks for certain types of music - User wants to analyze their music preferences or liked song records
Configure voicemail, voice channels, and emergency (E911) services for your phone numbers. This skill provides REST API (curl) examples.
Help apps and distribution channels integrate PCS Hub into their frontend. Use when user says "/hub-api-integration", "integrate PCS Hub", "embed PCS Hub swap", "PCS Hub integration guide", "how do I add PCS Hub to my wallet", "create a PCS Hub integration spec", or describes wanting to embed PCS Hub quote/swap functionality in an external UI.
Use when installing or configuring OpenClaw with DingTalk, Feishu, Discord, and additional channels with Bailian/DashScope models on Linux hosts. Use when provisioning a new OpenClaw node, troubleshooting gateway/channel startup, standardizing openclaw.json mapping, or automatically discovering extra channels from https://docs.openclaw.ai/channels.
Comprehensive reference for LINE MINI App — Service Messages, Common Profile Quick Fill, In-App Purchase, Console setup (3 internal channels), submission review, and performance guidelines for web apps running inside LINE as an enhanced LIFF platform. This skill should be used when the user asks to "build a LINE MINI App", "send a service message", "set up Common Profile Quick Fill", "implement in-app purchase", "configure MINI App Console", "submit MINI App for review", or mentions LINE MINI App, Service Messages, notification token, Common Profile, IAP purchase flow, 3 internal channels, consent simplification, Custom Path, custom share messages, or verified vs unverified MINI App. Always use this skill whenever the user mentions LINE MINI App, mini apps in LINE, or enhanced LIFF features like service messages or in-app purchase, even if they don't explicitly say "MINI App".