菜单
Configure or disable Gmail's vacation responder with an exact subject, message, audience, and optional date range. Use when the user asks to enable, change, inspect, or turn off an out-of-office automatic reply.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | recipe-create-vacation-responder |
| description | Configure or disable Gmail's vacation responder with an exact subject, message, audience, and optional date range. Use when the user asks to enable, change, inspect, or turn off an out-of-office automatic reply. |
Use gws-gmail for account selection and Gmail API details.
Read the current settings without changing them:
gws gmail users settings getVacation --params '{"userId":"me"}'
Resolve the exact subject, plain-text body, audience restrictions, start, end, timezone, and target account. Convert start/end to epoch milliseconds; verify that start precedes end. Omit date fields only when the user intentionally wants the responder enabled without an automatic window.
Build the update using placeholders rather than copying stale dates:
gws gmail users settings updateVacation \
--params '{"userId":"me"}' \
--json '{"enableAutoReply":true,"responseSubject":"<SUBJECT>","responseBodyPlainText":"<BODY>","restrictToContacts":true,"restrictToDomain":false,"startTime":"<START_EPOCH_MS>","endTime":"<END_EPOCH_MS>"}'
Run the exact update with --dry-run. Show the user the account, complete subject/body, human-readable local start/end, timezone, and recipient restrictions.
Ask for explicit confirmation immediately before running the update without --dry-run.
Read the settings back with getVacation and verify every confirmed field.
Disabling is also a write and requires its own explicit confirmation:
gws gmail users settings updateVacation \
--params '{"userId":"me"}' \
--json '{"enableAutoReply":false}'
Do not assume a prior planned return date is approval to disable the responder later.
Read upcoming OpenTable reservations or handle attended ad-hoc OpenTable availability and exact-approval booking. Use for OpenTable account reads, attended restaurant searches, or a user-confirmed one-off reservation; route canonical recurring date-night, double-date, and quarterly-group jobs to the restaurant-book skill instead.
Stage tightly scoped background reservation monitoring for OpenTable or Resy after explicit bounded preauthorization. Resy may auto-book after approval; OpenTable remains notification-only until this runtime adapter integrates the deployed live reservations reader. Not for one-shot search, attended booking, or cancellation.
Search Resy, inspect availability, and handle attended ad-hoc Resy booking. Route canonical recurring date-night, double-date, and quarterly-dinner jobs to restaurant-book, and use restaurant-snipe only for bounded cancellation monitoring. Never use this skill for unattended cancellation.
Safely plan or execute a canonical standing-authorized restaurant cron scope across both Resy and OpenTable. Use only for the tracked date-night, double-date, and quarterly-dinner jobs; use the provider skills for attended ad-hoc work and restaurant-snipe for bounded monitoring.
Safely use exact 1Password fields during attended interactive work and maintain the protected OpenClaw secrets cache. Use for passwords, API keys, credentials, payment data, cache refreshes, or diagnosing credential access. Never use `op` from a LaunchAgent or any child process it starts.
Diagnose and fix 1Password CLI hangs or repeated TCC prompts in macOS LaunchAgent and other unattended contexts by converting the complete process tree to a protected cache-only credential contract.