Book and manage tennis/pickleball courts at Bay Club.

This skill appears to implement the advertised booking functionality, but there are a few issues to check before installing: - Credentials: The registry metadata claims no required env vars, yet the code needs BAYCLUB_USERNAME and BAYCLUB_PASSWORD to log into Bay Club. It also optionally uses GOOGLE_CALENDAR_CREDENTIALS (or a local JSON file) and BROWSERBASE_API_KEY/BROWSERBASE_PROJECT_ID in production. Don't install unless you're prepared to provide those secrets. - Least privilege for Google: If you enable calendar integration, create a dedicated service account with only the calendar permissions you need (share a single calendar, not your primary account) and avoid giving overly broad access. - Execution surface: The skill runs TypeScript with npx ts-node (i.e., executes code included in the skill). Run it in an isolated environment (container or throwaway VM / personal server) until you review the code fully—this prevents accidental exposure if something unexpected is added. - Audit dependencies & provenance: package-lock.json includes many dependencies. If you intend to run this on a persistent host, review package.json/lockfile and consider installing in an environment where you control network access. Also, there's no homepage or official source in the registry metadata; prefer skills with a verifiable source or ask the publisher for the repo. - Ask for fixes: Request that the skill metadata / SKILL.md be updated to declare required env vars (BAYCLUB_USERNAME, BAYCLUB_PASSWORD) and to document optional GOOGLE_* and BROWSERBASE_* variables so users know exactly what will be needed. If you cannot verify the author or are uncomfortable providing the credentials, do not install it on a system with sensitive data or long-lived credentials.

Type: OpenClaw Skill Name: bayclub-gateway-booking Version: 1.0.0 The skill automates Bay Club court bookings and integrates with Google Calendar. It requires `BAYCLUB_USERNAME`, `BAYCLUB_PASSWORD`, and optionally Google Calendar service account credentials. While the `SKILL.md` instructions for the AI agent are slightly ambiguous regarding the entry point (`bayclub_skills.ts` vs. `cli.ts`), the underlying TypeScript code (`bayclub_skills.ts`, `BayClubBot.ts`, `GoogleCalendarService.js`) handles user inputs (`sport`, `day`, `time`) with sufficient sanitization (type checking, mapping, string comparisons, date parsing) to prevent shell or XPath injection. The use of `--no-sandbox` for browser automation is a general security vulnerability in the execution environment but is common for such tasks and does not indicate malicious intent by the skill developer. No evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection against the agent was found. The requested Google Calendar scope is appropriate for the stated functionality.