padel

What This Skill Does

The Padel Booking Skill is a specialized OpenClaw agent capability designed to automate the search and management of padel court reservations. By integrating with the local padel CLI tool, this skill allows users to query availability across preferred clubs, review upcoming schedules, and initiate booking workflows without leaving the terminal or chat interface. The skill abstracts the complexity of command-line interaction, providing a streamlined, conversational interface for sports enthusiasts.

Installation

To integrate this skill into your OpenClaw ecosystem, use the following command:

clawhub install openclaw/skills/skills/local/padel

Ensure that the padel binary is available on your system's PATH. The skill assumes the presence of a moltbot-compatible plugin bundle. Once installed, verify connectivity by checking the version or running the help command via the agent.

Use Cases

1. Routine Check-ins: Quickly verify your next match time or court location before heading out.
2. Strategic Booking: Scout for availability during high-demand weekend slots across multiple venues simultaneously.
3. Delegation: Allow the agent to assist in finding slots while you finalize attendance with your team, ensuring only authorized personnel finalize the financial transaction.

Example Prompts

1. "Check my next padel booking and tell me where it is. 🎾"
2. "Find me a padel court at PadelClub A or B for this Saturday between 6 PM and 9 PM. 🎾"
3. "I need to book a court for Tuesday. Can you check availability and list the first 3 options? 🎾"

Tips & Limitations

• Venue Configuration: For the best results, ensure your preferred venues are pre-configured within your local padel environment. The skill will default to these settings.
• Authorization: Safety is a priority. This skill does not finalize payments or bookings autonomously. If you are not an authorized booker, the agent will prompt you to seek confirmation from the designated account holder. Always double-check venue cancellation policies, as this skill does not monitor or report them automatically. For complex queries involving date ranges, stick to the YYYY-MM-DD format to ensure the underlying CLI parses your request correctly.