okx-agent-identity

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, 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

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 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

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...

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 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',