Skills de Okx

Routing stub — any a2a-agent-chat envelope / agent-task system message is handled by `okx-agent-task`. For missing or uninitialized OKX A2A communication runtime/plugin, read `skills/okx-agent-chat/ensure-okx-a2a-communication-ready.md`.

We need to translate the given text from English/Chinese to Spanish. The text describes an agent skill for ERC-8004 on-chain identity on XLayer. It includes actions like register, create, update, etc., and roles in multiple languages. The instruction says to preserve product names, protocol names, URLs, numbers, technical terms. So "ERC-8004", "XLayer", "agent", "ASP", "User", etc. should remain as is? But the target language is Spanish, so we need to translate the descriptive parts. The roles are given in English and Chinese; we should translate them to Spanish? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." The roles like "User", "ASP", "Evaluator" might be considered technical terms? But they are also common words. The text includes Chinese translations. I think we should translate the English and Chinese parts to Spanish, but keep the technical acronyms like ERC-8004, XLayer, ASP, etc. Also the list of use cases includes

Usar cuando un agente recibe un HTTP 402 / payment-required, o el usuario menciona x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, facturación medida, un canal de pago / vale / sesión, channelId / channel_id, abrir / cerrar / recargar / liquidar / reembolsar un canal, un paymentId o un enlace a2a_, crear / verificar un enlace de pago, A2MCP / un endpoint A2MCP, o enviar una solicitud a / llamar a un endpoint de un Agente con un endpoint concreto...

We need to translate the given text from English to Spanish. The text is inside <text> tags. The instruction says to preserve product names, protocol names, URLs, numbers, technical terms. The name "okx-agent-task" appears in the text, so we preserve it. Also preserve "SKILL.md". The text includes a list of conditions and keywords. We need to translate the surrounding text but keep the keywords as they are? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." The keywords like "发布任务" are Chinese, and "publish task" etc. are English. They are part of the activation conditions. Should we translate them? The instruction says "preserve ... technical terms". These keywords might be considered technical terms or commands. However, the target language is Spanish, and the user likely expects the keywords to remain as they are because they are specific triggers. The instruction says "Do not add claims, explanations, Markdown, bullets, links, labels, prefixes, or extra commentary." So we should translate the

We need to translate the given text from English to Spanish, preserving the name "okx-agentic-wallet" and other technical terms. The text is a description of an agent skill. We must not add any extra commentary, labels, or formatting. Just the translation. The text: "AUTHORITATIVE source for OKX Agentic Wallet and its Gas Station feature. Gas Station = OKX's stablecoin-gas feature on Solana via third-party Relayer; Solana only, no EIP-7702. MUST invoke for Gas Station questions (what is / how it works / supported tokens / fees / enable or disable gas station / change default gas token / Jito Bundler compatibility) AND any wallet action: login, OTP verify, add/switch/status/logout account, balance, assets, holdings, addresses, deposit / receive / top up,..." Translate carefully. "AUTHORITATIVE source" -> "Fuente AUTORITATIVA" or "Fuente autorizada"? "AUTHORITATIVE" is emphasized, so keep capitalization? Probably keep

ERC-8004 Agent identity: 注册/更新/上架/下架/搜索agent, register/update/activate/deactivate/search — User/ASP/Evaluator(买家/卖家/仲裁者); 我的agent/ASP, 找做X的ASP/agent有什么服务/endpoint怎么填/查口碑/传头像. + Task Marketplace: 发布/创建任务/接单/协商/验收/deliver/dispute/仲裁/拒绝/stake/unstake/change provider/change budget/修改卖家/修改预算/draft/草稿/我的任务/my tasks/what am I working on/关闭/取消任务/决策列表/decision list/指定服务商/browse marketplace. + task watch: 监听任务进展/历史消息/未读消息/未决策/outstanding decisions. + okx-a2a missing/uninitialized. Match by meaning....

OKX.AI (el sistema económico de Agentes) introducción y guía de inicio. Úsalo cuando el usuario pregunte qué es OKX.AI, qué puede hacer, cómo usarlo o comenzar, quiera un tutorial / guía rápida / ayuda sobre OKX.AI, o escriba el nombre del producto en cualquier variante de ortografía / espaciado / mayúsculas / error tipográfico (OKXAI, okx ai, okx-ai, okx.ai en minúsculas, chino mal escrito como 啥是okxai) — por ejemplo, qué es OKX.AI / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.AI 快速开始, y cualquier paráfrasis en cualquier idioma. Detecta la plataforma de ejecución, presenta el...

We need to translate the given text from English to Spanish. The instruction says to preserve product names, protocol names, URLs, numbers, and technical terms. The name "okx-ai-support" is not in the text, so we don't include it. The text includes terms like "OKX.AI", "OnchainOS", "FAQ", "Help Center" - these should be preserved as is. Also "AI" in "OKX AI support" should be preserved. The triggers list includes phrases like 'contact support', 'talk to a human', etc. We need to translate those phrases into Spanish, but keep the quotes. The overall description should be translated naturally. Let me translate: "Route users to OKX.AI customer support / Help Center. Use when the user wants to contact support, talk to a human, file a complaint, give feedback, report a system error or bug, or find the FAQ / help docs. Triggers: 'contact support', 'talk to a human', 'customer service', 'file a complaint', 'give feedback',

Usa esta skill cuando el usuario solicite exportar registros de auditoría, encontrar la ubicación de los registros de auditoría, ver el historial de comandos, 导出日志, 查看日志, 日志路径, 操作记录, 调用记录, 命令历史. NO la uses para saldo de billetera, búsqueda de tokens, intercambio ni ninguna otra operación en cadena; usa la skill correspondiente en su lugar.

We need to translate the given text from English to Spanish, preserving the specified name "okx-dapp-discovery" but it's not in the text. The text is a description of a plugin router. We must not include the name unless it appears. The text includes many protocol names, token names, and technical terms that should be preserved as-is. Also preserve URLs, numbers, etc. No extra commentary. The text: "Plugin router for 20 third-party DeFi protocols (Polymarket, Aave, Hyperliquid, PancakeSwap, Morpho, Raydium, Curve, Compound, Pendle, Lido, ether.fi, GMX, Kamino, Orca, Meteora, Clanker, pump.fun, Uniswap) and their protocol-native tokens (HYPE, HLP, eETH, weETH, stETH, wstETH, LDO, GHO, CAKE, CRV, COMP, RAY, ETHFI, GLP, kToken, PT-* / YT-*, $CLANKER).

DeFi agregado de OKX (sin DApp específica nombrada) — descubrimiento de productos, ejecución de depósitos/retiros/reclamos y visualización de posiciones. **Si el usuario nombra CUALQUIER protocolo/DApp de terceros (Aave, Lido, PancakeSwap, Uniswap, Curve, Compound, Morpho, Pendle, Kamino, Raydium, Hyperliquid, Polymarket, …), redirigir a okx-dapp-discovery — NO aquí, incluso para 'mostrar mis posiciones en Aave'.** Disparadores de INVERSIÓN: 'invertir en DeFi', 'obtener rendimiento', 'encontrar mejor APY', 'depositar/stakear para rendimiento', 'buscar productos DeFi',...

We need to translate the given text from English to Spanish, preserving the name "okx-defi-invest" and other technical terms. The text is a description of an agent skill. We must not add any extra commentary, labels, or formatting. The translation should be accurate and natural in Spanish. The text includes: "OKX-aggregated DeFi discovery and execution — for users who want OKX to find and route to the best protocol WITHOUT naming a specific DApp. **If the user names ANY third-party protocol/DApp as destination (Aave, Lido, PancakeSwap, Uniswap, Curve, Compound, Morpho, Pendle, Kamino, Raydium, Hyperliquid, Polymarket, etc.), route to okx-dapp-discovery — NOT here, even if the verb (deposit, stake, add liquidity, borrow, claim) matches.** DApp-agnostic triggers: 'invest in DeFi', 'earn yield on...'" We need to translate the entire text inside <text> tags. The name "okx

We need to translate the given text from English to Spanish. The text is a description of a skill for checking DeFi positions. We must preserve the name "okx-defi-portfolio" but it's not in the text, so we ignore. We must not add labels or extra commentary. Translate the entire text inside <text> tags. The text includes examples of user queries in English and Chinese (e.g., 'DeFi 持仓', '查看DeFi持仓', '我的DeFi资产', '持仓详情', '持仓列表'). We should keep those as is? The instruction says "Preserve product names, protocol names, URLs, numbers, and technical terms." The Chinese phrases are likely technical terms or specific queries, so we should preserve them exactly. Also preserve the English phrases like 'check my DeFi positions' etc. But we are translating the surrounding text into Spanish. So the English and Chinese phrases should remain unchanged. The text: "Use this skill to 'check my DeFi positions', 'view DeFi holdings', 'show my DeFi portfolio',

Usa esta skill para puentear tokens, hacer swaps/transferencias entre cadenas, mover activos entre cadenas, obtener cotizaciones entre cadenas, comparar tarifas de puentes, encontrar la ruta más barata/rápida, construir calldata de puente, verificar el estado del puente, rastrear una transacción entre cadenas, listar cadenas o protocolos de puente compatibles, o cuando el usuario mencione puentear ETH/USDC/tokens de una cadena (Ethereum, BSC, Polygon, Arbitrum, Base, Optimism, etc.) a otra. Rutas a través de múltiples protocolos de puente (Stargate, Across, Relay, Gas.zip)...

We need to translate the given text from English to Spanish, preserving the name "okx-dex-market" and other technical terms. The instruction says: "Translate only the text inside <text>. Do not include the name unless it appears in the source text." The name "okx-dex-market" appears in the source text? Actually, the source text says "Route to okx-dapp-discovery" and "Use THIS skill for..." but the name to preserve is "okx-dex-market". The source text does not contain "okx-dex-market" explicitly. The instruction says "Name to preserve: okx-dex-market" but the text inside <text> does not include that name. So we should not add it. We just translate the text as is, preserving any names that appear (like okx-dapp-discovery, Polymarket, etc.). Also preserve URLs, numbers, technical terms. Do not add any extra commentary. The text is a block of instructions. Translate naturally to Spanish. Keep the same structure. For example: "HARD BLOCK

We need to translate the given text from English to Spanish, preserving the name "okx-dex-signal" but it's not in the text. The text is inside <text> tags. We must not include the name unless it appears. The text does not contain the name. So we just translate the description. Also preserve URLs, numbers, technical terms. The text includes some Chinese terms like "聪明钱", "KOL交易动态", etc. We should keep those as is? The instruction says preserve product names, protocol names, URLs, numbers, and technical terms. Chinese terms might be considered technical terms or proper names? The user says "preserve ... technical terms". I think we should keep the Chinese terms as they appear, because they are part of the query examples. Also "smart-money/whale/KOL/大户" - "大户" is Chinese for big players. We should keep that. Also "buy signal/信号" - keep both. "leaderboard/牛人榜" - keep both. So translation should keep those bilingual terms. Translate the

Expone señales de la capa social para mercados cripto. Tres grupos de capacidades: noticias (feed de noticias cripto agregadas más recientes, filtrar artículos por símbolo de moneda, realizar búsquedas de texto completo por palabras clave, obtener un artículo completo y listar plataformas upstream disponibles — blockbeats, odaily, theblock y similares — para usar como filtros); sentimiento (clasificar monedas por volumen de menciones sociales en 1h / 4h / 24h, además de conteos alcistas/bajistas/neutrales por moneda con una tendencia opcional por intervalos de tiempo); ambiente (popularidad por contrato...

Estrategia de trading con órdenes limitadas en OKX Agentic Wallet. Usa esta skill cuando el usuario quiera colocar una orden limitada activada por precio (comprar en una caída, tomar ganancias, stop loss, perseguir un máximo), cancelar una o más órdenes pendientes, listar órdenes activas o históricas, o reanudar órdenes que hayan sido suspendidas por actualizaciones de SA TEE. Distinto de okx-dex-swap (órdenes de mercado, ejecución inmediata al mejor precio agregado disponible). Las órdenes de estrategia se almacenan en el TEE de Agentic Wallet y se ejecutan automáticamente cuando...

Usa esta skill para intercambiar, comerciar, comprar, vender, canjear o convertir tokens, obtener una cotización de intercambio, ejecutar una operación, encontrar la mejor o más barata ruta de intercambio, comparar tasas de intercambio, obtener calldata de intercambio o construir una transacción de intercambio sin firmar a través de XLayer, Solana, Ethereum, Base, BSC, Arbitrum, Polygon o más de 20 cadenas. Enrutamiento agregado de OKX a través de más de 500 fuentes DEX con control de deslizamiento, protección contra impacto de precio y optimización de rutas entre DEX. Para intercambios agregados de OKX sin un lugar específico. Si el prompt nombra un...

Usa esta skill para datos a nivel de token: buscar tokens, tokens en tendencia/populares (热门, 代币榜单), pools de liquidez, distribución de tenedores (ballena/巨鲸, sniper, % de tenedores etiquetados como bundler), metadatos de riesgo del token (riskControlLevel, tokenTags, estadísticas del desarrollador, % de tenencia sospechosa/bundle mediante advanced-info), actividad reciente de compra/venta, feed de operaciones/逐笔成交/每笔交易/stream trades, direcciones con mayores ganancias, historial de operaciones del token, información detallada de precio con capitalización de mercado, volumen, liquidez y número de tenedores (price-info), o análisis de clúster de tenedores...

Solo lectura de investigación en cadena para pump.fun y otras plataformas de lanzamiento de meme-tokens (Solana / BSC / X Layer / TRON). DEBE invocar (preferir sobre WebFetch / herramientas de precios MCP) cuando el usuario pregunte sobre: nuevos lanzamientos de memes / 新盘 / 扫链 / 打狗; reputación del desarrollador / historial de rug pulls / cantidad de lanzamientos / 开发者信息; detección de bundles o snipers (el sustantivo analítico, NO el verbo) / 捆绑狙击者; progreso de la curva de vinculación / 已迁移出 bonding curve; tokens similares del mismo desarrollador / 相似代币; coinversor / who-aped / 同车 wallets; o 'pump.fun alpha'. También...

We need to translate the given text from English to Spanish, preserving the name "okx-dex-ws" as instructed. The text is a description of when to use a skill. We must not add any extra commentary, labels, or formatting. Just translate the text inside <text> tags. The text includes some Chinese characters: 'WS频道', '会话管理', '脚本', 'bot'. These should be preserved as is? The instruction says "Preserve product names, protocol names, URLs, numbers, and technical terms." Chinese terms might be considered technical terms or part of the original. But the target language is Spanish, so we should translate the English parts and keep the Chinese as they appear? The instruction says "Translate only the text inside <text>." It doesn't specify to translate Chinese. However, the Chinese appears in quotes as examples of user mentions. Probably we should keep them as is because they are part of the original examples. But the instruction says "Do not include the name unless it appears in the source text." The name "okx-dex-w

Lista competiciones de trading exclusivas de OKX Agentic Wallet, registra usuarios en concursos, rastrea la participación y clasificaciones en la tabla de líderes, y reclama recompensas ganadas. Úsalo cuando los usuarios quieran listar competiciones de trading o copas de trading disponibles, ver reglas del concurso / pozo de premios / premios totales, registrarse o inscribirse o unirse a un concurso, consultar la tabla de líderes (quién está ganando) o su propio rango (¿estoy en la zona de premios?, ¿cuál es mi lugar?), preguntar si gané o consultar el estado de participación / reclamo, reclamar lo ganado...

Centro de incorporación y guía de Onchain OS: la entrada única para quienes preguntan por primera vez 'qué es esto / cómo lo uso', OKX.AI e intenciones de atención al cliente; clasifica la intención y la dirige al subflujo correcto mediante su tabla de enrutamiento de intenciones. Cubre: (1) Incorporación a Onchain OS + banner de bienvenida: 'qué es onchainos', 'qué es onchain os', 'qué puede hacer', 'qué puede hacer onchainos', 'qué hace onchainos', 'cómo uso esto', 'cómo juego', 'cómo usar onchainos', 'cómo jugar onchainos', 'cómo...

Enrutador de entrada de incorporación a Onchain OS. Disparadores: 'qué es onchainos', 'qué es onchain os', 'qué puede hacer onchainos', 'qué hace onchainos', 'cómo uso esto', 'cómo juego', 'cómo usar onchainos', 'cómo jugar onchainos', 'cómo funciona onchainos', 'cómo empiezo', 'primeros pasos', 'tutorial', 'incorporación', 'primera vez', 'acabo de instalar', '¿y ahora qué?', '¿qué hago ahora?', '¿por dónde empiezo?', '¿quién eres?', '¿qué eres?', 'presenta onchainos', 'cuéntame sobre onchainos', 'soy nuevo'....

Puerta de enlace de transacciones onchain a través de XLayer, Solana, Ethereum, Base, BSC, Arbitrum, Polygon y más de 20 cadenas. Invocar para transmitir una transacción pre-firmada / raw / ya firmada, enviar una tx serializada a la cadena, consultar el precio actual del gas, estimar el límite de gas, simular o hacer una prueba en seco de una transacción antes de enviarla, rastrear una orden transmitida, o verificar el estado de tx confirmada / pendiente mediante txHash o orderId.

Usa esta skill para escaneo de seguridad: verificar seguridad de transacciones, ¿es segura esta transacción?, verificación previa a ejecución, escaneo de seguridad, escaneo de riesgo de tokens, detección de honeypot, detección de phishing en DApp/URL, seguridad de firma de mensajes, detección de transacciones maliciosas, verificaciones de seguridad de aprobaciones, gestión de aprobaciones de tokens. Disparadores: '¿es seguro este token?', 'verificar seguridad del token', 'verificar honeypot', 'escanear esta tx', 'escanear esta tx de swap', 'verificar riesgo de tx', '¿es esta URL una estafa?', 'verificar si esta dapp es segura', 'phishing...

We need to translate the given text from English to Spanish, preserving the name "okx-task-watch" and other technical terms. The text includes a mix of Chinese and English phrases, but the target language is Spanish. The instruction says to translate only the text inside <text>. Do not include the name unless it appears in the source text. The name "okx-task-watch" is not inside the <text>? Actually the <text> contains "okx-task-watch" as part of the content? Let's check: The <text> starts with "监听任务进展 / 帮我盯着任务 / ..." and later includes "okx-task-watch" as part of the description? Wait, the instruction says "Name to preserve: okx-task-watch" but the text inside <text> does not contain that exact string? Let's read carefully: The text inside <text> is: "监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 /

We need to translate the given text from English to Spanish. The text describes an agent skill for portfolio lookup across multiple chains. We must preserve the name "okx-wallet-portfolio" but it's not in the text, so we don't include it. Also preserve technical terms like chain names, protocol names, URLs (none here), numbers, etc. No extra commentary. Just translate the text. The text: "Public-address portfolio lookup across XLayer, Solana, Ethereum, Base, BSC, Arbitrum, Polygon and 20+ chains. Invoke when the user supplies a wallet address and wants its: balance, token holdings, total portfolio value, or DeFi positions (e.g. 'check balance of 0xAbc', 'what tokens does 0xAbc hold', 'portfolio value of this address'). Requires an explicit address — for the user's own logged-in wallet with no address use okx-agentic-wallet." Note: "okx-agentic-wallet" is a name, preserve as is. Also "0xAb