Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· AI
Skill
Connect to business AI agents on the Sooda network. Use when: user mentions Sooda, the Sooda network, or asks to talk to a Sooda agent by name (travelwise, d...
skill openclawclawhub Free
Connect to business AI agents on the Sooda network. Use when: user mentions Sooda, the Sooda network, or asks to talk to a Sooda agent by name (travelwise, d...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 2.0.0
Provenance
- Publisher
- tkim5574
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Sooda Bridge
Send messages to business AI agents through the Sooda network.
First-Use Setup
Before sending any message, check if SOODA_API_KEY is set in the environment. If SOODA_API_KEY IS set β skip to "Send a Message". If SOODA_API_KEY is NOT set β sign up for a session key: Ask the user for their email address Run the signup call inline: curl -s -X POST https://sooda.ai/api/v1/signup \ -H "Content-Type: application/json" \ -d '{"email":"USER_EMAIL_HERE"}' Parse the JSON response: { "agent_id": "uuid", "agent_name": "user-a1b2c3d4", "api_key": "sk_...", "connected_agents": ["travelwise", "dineout", "support", "helpdesk", "procurebot", "vendorbot"] } Hold the api_key value in memory as SOODA_API_KEY for this session Tell the user: "You're connected! To persist across sessions, run: export SOODA_API_KEY=sk_..."
Send a Message
Use this curl template to relay a message to any connected agent: curl -s -X POST https://sooda.ai/api/v1/relay/AGENT_NAME \ -H "Content-Type: application/json" \ -H "Authorization: Bearer $SOODA_API_KEY" \ -H "X-Sooda-Context-ID: CONTEXT_ID_OR_OMIT" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "message/send", "params": { "message": { "role": "user", "parts": [{"type": "text", "text": "USER_MESSAGE_HERE"}] } } }' Replace AGENT_NAME with the target agent (e.g. travelwise, helpdesk) Replace USER_MESSAGE_HERE with the user's message For the first message in a conversation, omit the X-Sooda-Context-ID header For follow-up messages, include the context_id from the previous response
Response Parsing
The relay response is JSON: { "jsonrpc": "2.0", "id": 1, "result": { "status": "completed", "session_id": "uuid", "context_id": "uuid", "a2a_task_id": "uuid", "a2a_response": { "result": { "id": "...", "status": { "state": "completed" }, "artifacts": [{ "parts": [{"type": "text", "text": "The agent's reply text"}] }] } } } } Extract the agent's reply from .result.a2a_response.result.artifacts[0].parts[0].text. Save the context_id from .result.context_id β pass it as X-Sooda-Context-ID on follow-ups to continue the conversation.
Status values
StatusMeaningActioncompletedAgent respondedExtract text from a2a_responseworkingAgent is still processingPoll for result (see below)queuedAgent at capacity, message queuedPoll for resultfailedDelivery failedShow error message to user
Error responses
Errors use JSON-RPC error format: { "jsonrpc": "2.0", "id": 1, "error": { "code": -32600, "message": "description" } }
Async Polling
If the status is working or queued, poll for the result using the session_id: curl -s https://sooda.ai/api/v1/sessions/SESSION_ID/result \ -H "Authorization: Bearer $SOODA_API_KEY" Poll every 2-3 seconds until the response contains a completed result.
Multi-Turn Context Tracking
Every relay response includes a context_id. You MUST: Parse and store the context_id from the FIRST relay response to an agent Pass it as the X-Sooda-Context-ID header on EVERY follow-up to the same agent If you do NOT pass the context ID, the follow-up creates a NEW conversation instead of continuing the existing one. ALWAYS pass the context ID for follow-ups.
Available Agents
helpdesk β Customer support helpdesk (orders, returns, refunds, shipping issues). Escalates to internal-ops for backend operations. travelwise β AI travel booking agent (flights, hotels, activities) dineout β AI restaurant booking agent (reservations, dining recommendations) support β Customer support (orders, returns, help) procurebot β B2B procurement agent (sourcing, quotes, purchase orders) vendorbot β B2B vendor/supplier sales agent More agents are added as partners join the network.
External Endpoints
URLMethodData SentPurposehttps://sooda.ai/api/v1/signupPOSTEmail, optional agent nameOne-time signup to get API keyhttps://sooda.ai/api/v1/relay/{agent}POSTJSON-RPC message with user textSend A2A message to a business agenthttps://sooda.ai/api/v1/sessions/{id}/resultGETNone (Bearer token in header)Poll for async agent response
Security & Privacy
All communication uses HTTPS only. No plaintext HTTP requests. Authentication via Bearer token (SOODA_API_KEY) in the Authorization header. No local data storage β the API key is held in memory for the session only. Message content is opaque to Sooda's relay layer; it is forwarded to the target agent as-is. The API key scopes access to the registered agent's connections only.
Trust Statement
Sooda.ai is a third-party A2A relay platform. By using this skill, messages are sent through Sooda's infrastructure to business agents registered on the network. The SOODA_API_KEY controls which agents you can communicate with β it cannot access other users' data or agents outside your connection graph. Sooda does not store message content beyond delivery; see sooda.ai for full terms.
Category context
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md