eBusy Courts Skill

This skill wraps a small Python client (ebusy_api.py) to log into
eBusy-based booking systems and fetch reservations for a given
court-module and date.

It is designed to work with multiple halls by switching
configuration via environment variables. All hall- and user-specific
values are provided by the environment, not hard-coded in the skill.

Important: No usernames/passwords should be committed into this
skill folder. Keep real credentials in a local .env, your shell
environment, or OpenClaw's gateway config.

Files

• - skills/ebusy-courts/ebusy_api.py – core Python client
• INLINECODE3 – this documentation

Optional (local-only, do not publish):

• - skills/.env – local environment file with hall-specific credentials

Python client: ebusy_api.py

The client is written to be generic; it reads all hall-specific
config from environment variables:

CODEBLOCK0

Usage (in a venv with requests + beautifulsoup4 installed):

CODEBLOCK1

The script will:

1. 1. Log into the configured eBusy instance using the configured

1. 2. Fetch the reservations JSON for the given date.
2. Print a sorted list of reservations:

CODEBLOCK2

Example hall profiles

This section shows example configurations for two real halls in
Germany. Other users can copy the pattern and plug in their own club
URLs and module IDs.

Example: Medenhalle Wiesbaden-Medenbach

• - Base URL: INLINECODE7
• INLINECODE8
• INLINECODE9
• Credentials typically provided via:

Example shell setup:

CODEBLOCK3

Example: KTEV Kelkheim

• - Base URL: INLINECODE12
• INLINECODE13
• INLINECODE14
• Credentials typically provided via:

Example shell setup:

CODEBLOCK4

How an agent can use this skill

When a user asks for availability in a given hall (e.g. "Suche freie
Zeiten in der Tennishalle XYZ am Sonntag"), an OpenClaw agent can:

1. 1. Map the hall name to a profile (base URL, module id, first-court-no),

1. 2. Ensure the environment variables EBUSY_* are set for that hall

1. 3. Call ebusy_api.py for the relevant date, parse the JSON, and build

The decision logic (which profile to choose for which user request)
should live in the agent and/or TOOLS.md, not in this skill's code.

Publishing considerations

• - Do not publish skills/.env or any file containing real

• - Ensure .gitignore excludes skills/.env and similar secret-bearing

• - The skill itself (this SKILL.md + ebusy_api.py) contains only