brek-ai-skill

What This Skill Does

The brek-ai-skill is a sophisticated integration layer designed to connect OpenClaw AI agents with the Brek Partner Core Chat API. It is purpose-built to facilitate high-stakes hotel search, booking assistance, and payment orchestration while maintaining strict security and compliance standards. The skill acts as an intelligent intermediary, handling session lifecycle management, event dispatching, and error handling for external Brek-powered environments. It ensures that agents operate within established call-control guardrails, preventing abuse through robust idempotency management and rate-limit awareness. By utilizing this skill, developers can abstract the complexities of stateful chat sessions, ensuring that hotel search results are accurately captured, booking options are handled with transaction-safe keys, and sensitive payment confirmations are routed without ever exposing raw credit card data to the AI agent.

Installation

To install this skill in your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/leo9/brek-ai

Ensure your runtime environment is pre-configured with the required environment variables: BREK_BASE_URL and BREK_PARTNER_API_KEY.

Use Cases

• Automated Hotel Booking: Guiding users through real-time availability checks, price comparisons, and final booking confirmation.
• Payment Orchestration: Triggering secure, tokenized payment flows for completed booking transactions without handling raw PAN or CVV data.
• Complex Session Management: Maintaining persistent state for end-users across multiple chat turns, ensuring that search history and selection context remain intact.
• Transactional Integrity: Providing reliable, idempotent execution for critical user actions like price confirmations or booking cancellations.

Example Prompts

1. "Find me a 4-star hotel in downtown Tokyo for the weekend of October 12th under $300 per night and start a session with Brek."
2. "I'd like to book the Grand Hyatt option we found earlier; please proceed with the payment confirmation step."
3. "Can you check if my existing booking for the Marriott in Berlin can be canceled without a penalty fee?"

Tips & Limitations

• Session Integrity: Never share a session across different users. Always generate a unique session per actorId to prevent cross-user data leakage.
• Security First: Never request or store raw card numbers, CVV, or full PANs within the chat context. Always use paymentMethodId derived from provider-hosted fields.
• Idempotency: When executing sensitive commands like action_book_option or action_confirm_payment_card, always provide a valid idempotencyKey formatted as <partnerId>:<sessionId>:<kind>:<clientActionId> to ensure transaction safety and prevent duplicate billing.
• Rate Limiting: Always respect 429 responses and implement exponential backoff to ensure your integration remains healthy and compliant with Brek service limits.