okx-ai-support

tarafından okx

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', 'help center', 'FAQ', 'user guide', 'system error', 'system bug', 'something is broken', 'find help docs', 'OKX AI support', 'OnchainOS support', 'human agent'.

npx skills add https://github.com/okx/onchainos-skills --skill okx-ai-support

ZIP İndir GitHub

OKX.AI Support — Customer Service Guidance

Guidance-only skill. It returns a fixed Help Center walkthrough so the user can reach OKX.AI support. It runs entirely in the conversation layer: no CLI call, no network request, no wallet or credential access, no side effects.

When to use

Trigger and render the template

Response

You can get help through the OKX.AI Help Center:

🔗 OKX.AI Help Center: https://okx.ai 

There you can:
* Chat with support online — talk in real time to report an issue or file a complaint

How to chat with support online:
1. Click the https://okx.ai link to go to the OKX.AI website
2. Find the support icon in the bottom-right corner of the page
3. In the chat window that appears, click Start Chat
4. Select your region, then click Continue
5. You're all set — you can start chatting right away

okx tarafından daha fazla skill

okx-agent-identity

We need to translate the given text from English/Chinese to Turkish. The text describes an agent skill for ERC-8004 on-chain Agent 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", "evaluator" etc. should remain as is or translated? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." So "ERC-8004" and "XLayer" are protocol/product names, keep them. "Agent" might be a technical term, but it's also a common word. However, in context, it's part of the skill name "okx-agent-identity" which is preserved but not in the text. The text uses "agent" repeatedly. Should we translate "agent" to Turkish? The instruction says "preserve technical terms". "Agent" is a technical term in

OKX.AI (Ajan ekonomik sistemi) tanıtımı ve kullanıma başlama girişi. Kullanıcı OKX.AI’nin ne olduğunu, ne yapabileceğini, nasıl kullanılacağını veya nasıl başlanacağını sorduğunda, OKX.AI eğitimi / hızlı başlangıç / yardım istediğinde veya ürün adını herhangi bir yazım / boşluk / büyük-küçük harf / yazım hatası varyantında (OKXAI, okx ai, okx-ai, küçük harfli okx.ai, yanlış yazılmış Çince 啥是okxai) yazdığında — örn. OKX.AI nedir / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.A

researchapidocument

okx-agentic-wallet

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

apiweb-scrapingdevelopment

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

developmentapicommunication

Gelen zarflarda ZORUNLU etkinleştirme: (1) {agentId, message:{source:"system", event, jobId, ...}} — sistem olayı; (2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — ajanlar arası görev sohbeti (alanlar üst düzeyde; sender.role = KARŞI TARAF, siz değil); (3) zarfta "Read okx-agent-task/SKILL.md" ifadesi. AYRICA şu anahtar kelimeler için etkinleştir: 发布任务 / 创建任务 / 帮我发任务 / publish task / create task / 接任务 / 接单 / 协商 / 验收 / 拒绝 / 仲裁 / dispute / stake / unstake / 修改卖家 / 修改预算 / change provider / change budget...

developmentapicommunication

okx-agent-payments-protocol

Bir aracı HTTP 402 / payment-required hatası aldığında veya kullanıcı x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, bir ödeme kanalı / kupon / oturum, channelId / channel_id, bir kanalı açma / kapatma / doldurma / kapatma / ger

Bu beceriyi güvenlik taraması için kullanın: işlem güvenliğini kontrol etme, bu işlem güvenli mi, işlem öncesi kontrol, güvenlik taraması, token risk taraması, honeypot tespiti, DApp/URL kimlik avı tespiti, mesaj imzası güvenliği, kötü amaçlı işlem tespiti, onay güvenliği kontrolleri, token onay yönetimi. Tetikleyiciler: 'bu token güvenli mi', 'token güvenliğini kontrol et', 'honeypot kontrolü', 'bu işlemi tara', 'bu takas işlemini tara', 'işlem risk kontrolü', 'bu URL dolandırıcılık mı', 'bu dapp güvenli mi kontrol et', 'kimlik avı...

监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听 / task watch / user watch / monitor task progress / catch me up on tasks / outstanding decisions — OKX A2A user-session task-notification monitor: live long-poll via `okx-a2a user watch` (also drains backlog of past/missed/unread events on entry) plus un-replied decision_request lister via `okx-a2a user outdated-list`. Not for wallet / gas / task-list / status queries.

developmentapiproductivity