Playtomic - Book courts using padel-tui

This skill should be used when the user asks to "book a padel court", "find available padel courts", "search padel courts near me", "reserve a Playtomic cour...

Security Scan

The skill is an instruction-only helper for using the padel-tui CLI to book Playtomic courts; its requested actions and install instructions align with that purpose and do not ask for unrelated credentials or privileged access.

Purpose & Capability

The name/description describe Playtomic booking via padel-tui and all runtime instructions focus on running that CLI (search, book, matches, match-cancel). There are no unrelated env vars, binaries, or config paths requested.

Instruction Scope

SKILL.md confines actions to verifying/using the padel-tui binary, prompting the user to authenticate interactively, and performing explicit booking/cancel operations only after user confirmation. It does not instruct reading unrelated system files or exfiltrating data. It documents the default session file (~/.config/padel-tui/session.json) which is expected for a CLI that stores session state.

Install Mechanism

This is instruction-only (no installer executed automatically). Installation guidance references reasonable sources: Homebrew tap (philipp-eisen/tap), GitHub releases (prebuilt tarball), or running from source (bun install). These are typical but the 'run from source' path implies fetching packages (bun/npm) and the tarball path requires user care to verify release integrity. The skill correctly requires explicit user approval before installing.

Credentials

No environment variables or external credentials are requested by the skill. The only config artifact mentioned is the CLI session file (~/.config/padel-tui/session.json), which is appropriate for a CLI that maintains login state. The SKILL.md explicitly prohibits asking the user for credentials and requires interactive auth.

Persistence & Privilege

The skill does not request permanent presence (always:false) and cannot modify other skills or system-wide configs. It only instructs use of a user-local session file for CLI auth, which is normal for such tools.

Assessment

This skill is coherent and limited to driving the padel-tui CLI, but follow these precautions before installing or using it: 1) Only run install steps after you explicitly approve them. 2) Prefer Homebrew or GitHub releases from the official repo; verify release checksums/signatures if available. 3) If running from source, be aware 'bun install' will fetch remote packages—inspect repository/package manifests if you are concerned. 4) Never paste your password into chat; perform 'padel-tui auth login' interactively in your terminal as instructed and confirm completion manually. 5) Confirm any booking/cancel operations before they are executed since they have real user impact.

Book Padel Courts With padel-tui

Use this skill to complete Playtomic booking tasks from a terminal with minimal assumptions about prior setup.

Trigger Examples

• "Find me a padel court in Berlin tonight."
• "Book a Playtomic court for tomorrow at 19:00."
• "Show my active matches and cancel one."
• "Install padel-tui and use it to reserve a court."
• "Use CLI instead of TUI for booking."

When To Use

• Use when the task is to search courts, book a slot, list active matches, or cancel a match.
• Use when the user requests Playtomic actions through CLI commands.
• Do not use for non-Playtomic tasks.

Required Safety Rules

• Ask about installation only if needed (binary missing) or explicitly requested.
• Confirm installation intent before running any install command.
• Ask: "Do you want me to install padel-tui now, or skip installation and use your current setup?"
• If installation is declined, continue with the existing binary/path.
• Do not ask the user for email or password.
• Ask the user to authenticate interactively with <prefix> auth login.
• Treat book and match-cancel as user-impacting operations and run only after explicit user intent.

Setup Check

1. Select a command prefix.
   • Global install: padel-tui
   • Source checkout: ./bin/padel-tui
2. Verify access with <prefix> --version.
3. If command is missing and installation is approved, follow references/INSTALLATION.md.

Terms (Minimal Context)

• tenant_id: venue or club id from search output.
• resource_id: specific court id from search output.
• start: slot datetime in YYYY-MM-DDTHH:mm:ss format.

Minimal Booking Workflow

1. Ask the user to authenticate interactively.
   • Instruct the user to run: <prefix> auth login
   • Wait for user confirmation that login is complete.
2. Search availability (one mode required).
   • <prefix> search --near "<city>" --date YYYY-MM-DD
   • <prefix> search --name "<venue>" --date YYYY-MM-DD
3. Capture booking inputs from search output.
   • Record tenant_id, resource_id, and slot start time.
4. Create booking.
   • <prefix> book --tenant-id <tenant-id> --resource-id <resource-id> --start YYYY-MM-DDTHH:mm:ss --duration 60 --players 4
5. Verify result.
   • <prefix> matches --size 30
6. Cancel only when requested.
   • <prefix> match-cancel --match-id <match-id>

Command Rules

• Require one of --near or --name for search.
• Require --tenant-id, --resource-id, and --start for book.
• Keep authentication interactive; use <prefix> auth login without credential flags.
• Use search and book; avoid legacy availability and payment groups.

Reference Files

• references/INSTALLATION.md - install paths, verification, and first login.