Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
Agent Hotel Booking
Integrate with Brek Partner Core Chat API for hotel-search and booking assistant flows. Use when an agent needs to create or continue Brek chat sessions, sen...
skill openclawclawhub Free
Integrate with Brek Partner Core Chat API for hotel-search and booking assistant flows. Use when an agent needs to create or continue Brek chat sessions, sen...
โฌ 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, agents/openai.yaml, references/call-control.md, references/api-templates.md, references/payment-and-billing.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
- 1.0.2
Provenance
- Publisher
- leo9
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Brek AI Partner Core Chat
Execute Brek through /api/partner/v1/core-chat. Use this execution order: Create one session per end user (POST /sessions) with a stable actor.actorId. Reuse that session for all follow-up messages (POST /events). Read the latest state when needed (GET /sessions/{sessionId}). Do not share one session across different users.
Required runtime inputs
Require these inputs before calling Brek: BREK_BASE_URL BREK_PARTNER_API_KEY actorId (stable partner-side end-user ID) workspaceId or tenant context if your product uses workspaces partnerId (stable partner tenant ID for idempotency and billing grouping) clientActionId for each write-like event kind If one required input is missing, stop and request it. If BREK_PARTNER_API_KEY is missing: stop outbound calls ask the user to get the key from their internal owner or approved support channel never request secrets through unapproved channels
Call safety guardrails
Apply these guardrails before every upstream call: Enforce local budget limits from references/call-control.md. Attach a deterministic idempotencyKey for all write-like event kinds. Respect 429 with retry-after and exponential backoff. Open a circuit breaker after repeated 5xx or timeout failures. Log x-request-id, x-partner-id, x-ratelimit-limit, and x-ratelimit-remaining. Never retry booking or payment-confirm actions without the same idempotencyKey.
Event-kind rules
When kind is one of: command_book_by_option_id action_book_option action_confirm_price_change action_confirm_payment_card action_cancel_booking Always include idempotencyKey. Generate idempotencyKey as: <partnerId>:<sessionId>:<kind>:<clientActionId> If partnerId is unavailable in your runtime, use stable tenant context (for example workspaceId) and keep the key format deterministic.
Payment handling
Handle payment in two layers: End-user card setup and confirmation in secure portal flow. Agent-to-agent usage billing and settlement. Follow references/payment-and-billing.md for both layers. Hard rules: Never request or store raw card number, CVV, or full PAN in chat. Accept only tokenized paymentMethodId from provider-hosted fields. Require explicit user confirmation before action_confirm_payment_card and booking actions.
Response mapping
Map Brek response as: data.result.status -> state machine key for UI and orchestration data.result.message.text -> user-visible assistant text data.result.artifacts -> structured payload (shortlist, payment setup URL, booking metadata)
Error handling
400: request validation failed. Fix payload. 401/403: API key issue. Stop calls. Tell user to rotate or provision key through their internal owner or approved support channel. 404: session not found or wrong tenant. 409: actor/session mismatch. Recreate correct session. 429: throttle locally and retry by retry-after. 5xx: retry with backoff, then open breaker.
References
Read only what you need: API payload templates: references/api-templates.md Call-control and anti-abuse policy: references/call-control.md Payment and billing orchestration: references/payment-and-billing.md
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
4 Docs1 Config
- SKILL.md
- references/api-templates.md
- references/call-control.md
- references/payment-and-billing.md
- agents/openai.yaml