From wework
Operate the WeWork CLI for workspace booking workflows, including authentication setup with `WEWORK_USERNAME` / `WEWORK_PASSWORD`, location and desk discovery, booking creation, booking listing, and calendar export. Use when requests mention `wework` commands or the npm package `wework-cli`, especially for command construction, flag troubleshooting, and safe pre-book checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wework:weworkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to run `wework` safely and produce exact commands for location lookup, desk availability checks, booking, and calendar export.
Use this skill to run wework safely and produce exact commands for location lookup, desk availability checks, booking, and calendar export.
Prefer read-only commands first and only run booking once location and date are validated.
Read references/commands.md when you need full command and flag coverage.
Read references/example-output.md when you need concrete output shapes for desks, locations, and bookings.
locations).desks).book).bookings) and optionally export calendar (calendar).Install the CLI:
npm install -g wework-cli
Use environment variables by default:
export WEWORK_USERNAME="your_username"
export WEWORK_PASSWORD="your_password"
For installed CLI usage with env credentials:
wework bookings
Use --username and --password only when explicitly requested.
Use these as canonical examples:
# list locations in Tokyo
wework locations --city "tokyo"
# list available desks in Bangkok for a date
wework desks --city "Bangkok" --date 2025-12-09
# list available desks for one location UUID
wework desks --location-uuid YOUR_LOCATION_UUID --date 2026-03-01
# create booking range with city + space name
wework book --city "Tokyo" --name "Shibuya Scramble Square" --date 2026-02-18~2026-02-20
# list upcoming bookings
wework bookings
# write ICS file for calendar import
wework calendar --calendar-path ./wework_bookings.ics
For single-day bookings, keep --date in YYYY-MM-DD.
For multi-day booking ranges, use YYYY-MM-DD~YYYY-MM-DD.
Use default CLI output for interactive use.
This CLI does not currently expose a JSON output flag in --help, so for automation treat output as text and parse conservatively.
Before book operations:
locations).desks).--date in YYYY-MM-DD format.bookings after booking.If authentication fails, re-check WEWORK_USERNAME and WEWORK_PASSWORD values, or explicitly pass --username / --password.
/Users/david/src/wework-cli/README.md includes older examples that use positional date arguments and a me command.
Current live CLI help (checked via wework --help and subcommand --help) uses --date flags for book/desks and does not expose me.
Prefer live command help when the README and binary behavior differ.
npx claudepluginhub dvcrn/skills --plugin weworkProvides API patterns for querying and managing Wix Bookings: filter by status/date/service, list services/staff, track appointments/revenue/metrics. For Wix integrations.
Automates Cal.com tasks via Rube MCP (Composio): manage bookings, check availability, configure webhooks, handle teams. Requires active connection and tool schema search.
Automates Cal.com scheduling: list/create bookings, check availability/slots, manage teams via Rube MCP (Composio) tools. Requires active Cal.com connection.