Total 53,674 skills, Platform Services has 618 skills
Showing 12 of 618 skills
Получение и обновление профиля текущего пользователя, управление статусом, кастомные поля сотрудников. Используй когда нужно: получить свой профиль, обновить статус, узнать дополнительные поля. НЕ используй для: управления другими сотрудниками (→ pachca-users).
Shopify platform development. Stack: Shopify CLI, GraphQL/REST APIs, Polaris UI, Liquid templating. Capabilities: app development (OAuth), checkout UI extensions, admin UI extensions, POS extensions, theme development, webhooks, billing API, product/order/customer management. Actions: build, extend, customize, integrate Shopify apps/themes. Keywords: Shopify, Shopify CLI, GraphQL Admin API, REST API, Polaris, Liquid, checkout extension, admin extension, POS extension, theme, webhook, billing API, OAuth, app bridge, metafields, product, order, customer, storefront, hydrogen, oxygen. Use when: building Shopify apps, customizing checkout, creating admin interfaces, developing themes, integrating payments, managing store data via APIs, extending Shopify functionality.
Call the RawUGC API to generate AI videos/images/music, manage content (personas, products, styles, characters), schedule social media posts, research TikTok content, and analyze viral videos. Use when the user wants to interact with any RawUGC API endpoint.
KuCoin Broker and Affiliate using the KuCoin API. Affiliate invite management, commission queries, Broker Pro user management, and ND (Exchange) Broker queries. Authentication requires API Key, API Secret, and Passphrase.
OmniStudio OmniScript creation and validation with 120-point scoring. Use when building guided digital experiences, multi-step forms, or interactive processes that orchestrate Integration Procedures and Data Mappers. TRIGGER when: user creates OmniScripts, designs step flows, configures element types, or reviews existing OmniScript configurations. DO NOT TRIGGER when: building FlexCards (use sf-flexcard), creating Integration Procedures directly (use sf-integration-procedure), or analyzing dependencies (use sf-omnistudio-analyze).
Binance Onchain-Pay (Connect) fiat-to-crypto on-ramp Open API skill. Enables partners to integrate crypto buying services: - **payment-method-list**: Get available payment methods (Card, P2P, Google Pay, Apple Pay, etc.) with limits for a fiat/crypto pair - **trading-pairs**: List all supported fiat currencies and cryptocurrencies - **estimated-quote**: Get real-time price quote including exchange rate, fees, and estimated crypto amount - **pre-order**: Create a buy order and get redirect URL to Binance payment flow - **order**: Query order status and details (processing, completed, failed, etc.) - **crypto-network**: Get supported blockchain networks with withdraw fees and limits - **p2p/trading-pairs**: List P2P-specific trading pairs
Use when the user mentions staking WAL, withdrawing hawal, claiming rewards, or operating haWAL on Haedal Protocol (a DeFi/LST protocol on SUI). Trigger phrases: “stake hawal”,"stake hawal", "withdraw hawal", "withdraw wal","instant withdraw hawal","instant withdraw wal","claim hawal rewards","claim wal rewards" . This skill calls https://skillsapi.haedal.xyz/api/v1/hawal/* via curl POST. On HTTP 200 returns txBytes (base64); on non‑200 returns msg.
Use when user wants to query blockchain data or build Web3 applications using the web3-tools skill without API key authentication — paying with USDC via the x402 protocol instead, using wallet-based auth (SIWX/SIWE/SIWS), credit charging, or pay-per-use billing
Integrate wallets with IC dApps using ICRC signer standards (ICRC-21/25/27/29/49). Covers the popup-based signer model, consent messages, permission lifecycle, and transaction approval flows. Implementation uses @dfinity/oisy-wallet-signer. Do NOT use for Internet Identity login, delegation-based auth (ICRC-34/46), or threshold signing (chain-key). Use when the developer mentions wallet integration, OISY, oisy-wallet-signer, wallet signer, relying party, consent messages, wallet popup, or transaction approval.
Build with Surf pay-per-use APIs at surf.cascade.fyi. Twitter data, Reddit data, web search/crawl, and LLM inference - no signup, no API keys, just pay per call. Use when working with Surf endpoints, fetching Twitter/X data, Reddit data, web crawling/search, pay-per-request LLM inference, setting up x402-proxy or @x402/fetch with Surf, or any mention of surf.cascade.fyi. Triggers on surf, surf.cascade.fyi, surf API, twitter data, reddit data, web crawl, surf inference, x402 endpoints, MCP surf tools.
This skill should be used when the user asks to "integrate web api", "add web api", "connect to dataverse", "add api integration", "set up web api calls", "integrate api for my tables", "add crud operations", "hook up web api", "add data fetching", "connect frontend to dataverse", or wants to integrate Power Pages Web API into their site's frontend code with proper permissions and deployment. This skill orchestrates the full integration lifecycle: code integration, permissions setup, and deployment.
Query real-time ZenMux account data via the Management API: subscription detail, quota usage (5h/7d/monthly), account status, Flow rate, PAYG balance, and per-generation cost. Use whenever the user wants to CHECK or LOOK UP current usage, remaining quota, credit balance, Flow rate, or a generation's cost/tokens. Trigger on: "check my usage", "quota left", "my balance", "subscription status", "Flow rate", "generation cost", "bonus credits", "查用量", "余额", "配额", "订阅详情", "Flow 汇率", "查一下请求花了多少", "额度还剩多少". Activate even without "ZenMux" when user asks to retrieve usage numbers, quota, balance, or generation cost in a ZenMux context. Do NOT trigger for docs, integration setup, plan comparison, top-up instructions, error troubleshooting, or code-writing — use zenmux-context.