Total 53,674 skills, Platform Services has 618 skills
Showing 12 of 618 skills
Subscribe to BingX spot WebSocket market data streams including real-time trades, order book depth, K-lines, 24h ticker, latest price, best bid/ask, and incremental depth. Use when the user asks about real-time spot market data, live spot price feeds, streaming spot order books, or WebSocket subscriptions for spot trading.
Outseta integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Outseta data.
Use when a user mentions Jupiter token verification, VRFD eligibility, paying 1000 JUP to verify a token, submitting a verification request, or updating metadata via the Jupiter express verification flow.
Stock prices, funds, gold, silver, crypto, macro indicators, bank rates, price charts, and company financials (income statement, balance sheet, cash flow, ratios). Use when user asks about stock prices, gold/silver prices, fund performance, interest rates, macro data, price history charts, or company financial statements.
Swap any pair of Solana tokens via DFlow. Use when the user wants to trade, swap, or convert tokens on Solana, get a price quote, build a swap UI, tune priority fees so a swap lands under congestion, or build a gasless / sponsored swap where the app pays fees. Covers both the `dflow` CLI and the DFlow Trading API. Do NOT use for Kalshi prediction-market YES/NO trades or builder-side platform fees.
Steedos metadata internationalization (i18n) system. Two file types: translation files (.translation.yml) for app names, tab labels, and custom labels; objectTranslation files (.objectTranslation.yml) for object labels, field labels/help/options, listview labels, action labels, group labels, and object-scoped CustomLabels. Covers directory structure, naming conventions, supported languages (en, zh-CN), and all translatable metadata sections.
Build unified cross-chain USDC balance management with Circle Unified Balance Kit SDK via App Kit (`@circle-fin/app-kit`) or standalone (`@circle-fin/unified-balance-kit`). Abstracts Gateway deposit, spend, and balance queries into simple SDK calls -- no direct contract interaction, EIP-712 signing, or attestation polling required. App Kit is recommended for extensibility across swap, bridge, send, and unified balance. Standalone Unified Balance Kit provides the same API surface in a lighter package. Neither requires a kit key for unified balance operations. Supports EVM chains and Solana via adapter packages. Use when: depositing USDC into a unified balance, spending from a unified balance to any supported chain, checking unified balance across chains, setting up Unified Balance Kit adapters (Viem, Solana, Circle Wallets), managing delegates for account separation, or building chain-abstracted USDC payment flows. Triggers on: unified balance, Unified Balance Kit, UnifiedBalanceKit, @circle-fin/unified-balance-kit, deposit USDC unified, spend unified balance, getBalances, cross-chain USDC SDK, chain abstraction SDK, adapter-viem, adapter-solana, depositFor, addDelegate, unified USDC.
XYO Protocol 2.0 domain knowledge. Covers payloads, bound witnesses, schemas, the module system (archivist, diviner, witness, sentinel, node), accounts, wallets, and protocol best practices. Activates when building on XYO or working with @xyo-network packages.
Use this skill when the user asks about Goldsky Subgraphs — deploying, managing, or querying subgraphs. Triggers on: 'deploy a subgraph', 'migrate from The Graph', 'what is a subgraph', 'GraphQL endpoint', 'low-code or no-code subgraph', 'subgraph tags', 'subgraph webhooks', 'cross-chain subgraph', 'subgraph stalled', 'subgraph API key', 'init subgraph', 'scaffold subgraph', 'subgraph logs', 'pause subgraph', 'start subgraph', 'graft subgraph'. Also use this skill when the user wants to build a GraphQL API over onchain data, power a dApp frontend with indexed blockchain data, or reuse an existing TheGraph subgraph on Goldsky. For questions about streaming raw chain data directly to a database without GraphQL, use the turbo-builder or mirror skills instead.
SOP for Vehicle Entry/Exit Operation Process of AIKE Smart Parking Open Platform (End-to-end Orchestration for Entry/Exit). This skill is applicable when users want to complete the full entry/exit of a vehicle, simulate the real physical entry/exit process, run through the entire link of 'Supplement/Capture Entry → Correction' or 'Exit Capture → Correction → Fee Inquiry → Payment', or ask questions like 'How does a vehicle enter/exits the parking lot?', 'Entry/exit process', 'Entry/exit SOP', 'How to move a vehicle into/out of the parking lot', 'Simulate vehicle entry/exit', or encounter stuck/debugging issues during entry/exit (e.g., vehicle fails to enter after capture or correction, capture returns error code 908, unsure how to proceed to the next step). This skill is a cross-domain orchestration layer that connects multiple commands from parking (supplement/correction/inventory), device (capture), and trade (fee inquiry/payment), and clarifies cross-command hard constraints (paired exit, capture device, channel release mode, token validity) and failure handling. Boundary: For querying a single record, checking on-site vehicles, locking vehicles, or calling a single command, please directly use the corresponding domain skills openydt-record / openydt-device / openydt-billing instead of this process skill.
Manages PubNub apps, keysets, and environment separation. Covers the publish/subscribe/secret key model, dev/staging/prod isolation, key rotation hygiene, demo-key boundaries, and custom origin configuration. Use when setting up a new PubNub project, separating environments, rotating keys, configuring demo or production keysets, or asking about apps, keysets, or custom origins.
Use this skill when users need to create, modify, or validate Salesforce Validation Rules. Trigger when users mention validation rules, field validation, data quality rules, formula validation, error messages, or validation logic. Also use when users encounter validation errors, need to update formulas, or want to enforce business rules at the data layer. Always use this skill for any validation rule work.