Padel

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's instructions, installation guidance, and requested artifacts are consistent with its stated purpose (using the padel-tui CLI to search and book Playtomic courts); nothing appears disproportionate or unrelated.

Purpose & Capability

The name/description describe CLI-based Playtomic bookings and the SKILL.md and INSTALLATION.md exclusively reference installing and running the padel-tui CLI, searching, booking, listing matches, and canceling matches. No unrelated credentials, services, or binaries are requested.

Instruction Scope

Runtime instructions limit the agent to checking for the CLI, asking for explicit consent before installing, instructing interactive login (user runs `padel-tui auth login`), running search/book/match commands, and only performing user-impacting actions after explicit intent. The skill does not instruct the agent to read arbitrary system files or exfiltrate data. It does reference the default session file (~/.config/padel-tui/session.json) as the place where the CLI stores sessions, which is expected for a CLI that maintains sessions.

Install Mechanism

This is an instruction-only skill (no automated install); INSTALLATION.md documents three user-approved install options: a Homebrew tap (philipp-eisen/tap), GitHub releases (download archive), or running from source (bun). Those are reasonable for a community CLI, but the Homebrew tap is a third-party tap and the prebuilt archive download requires trusting the GitHub release artifacts—users should verify release provenance/checksums. Running from source requires bun; the instructions correctly require explicit user approval before installing.

Credentials

The skill declares no required environment variables or credentials. It explicitly instructs interactive login and says not to ask users for email/password inline. The presence of a default session file (~/.config/padel-tui/session.json) is expected for a CLI that stores sessions; the skill does not instruct reading or exporting that file.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request permanent presence, modify other skills, or ask for cross-skill credentials. Autonomous invocation remains enabled (platform default) but is not combined with other red flags.

Assessment

This skill is coherent for using the padel-tui CLI to book Playtomic courts. Before installing: (1) confirm you want the agent to run install commands (the skill requires explicit user approval before installing), (2) verify the Homebrew tap and GitHub release you download come from a trusted source (check publisher and checksums/signatures when available), and (3) be aware the CLI stores session tokens at ~/.config/padel-tui/session.json — do not paste credentials into chat; use the interactive `padel-tui auth login` flow as instructed. If you prefer, you can install the CLI yourself and let the skill use your existing binary. If you have any doubt about the third-party Homebrew tap or release provenance, install from source or skip installation and perform bookings manually.

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.