// Full Google Calendar control across all accounts. Use for viewing agenda, creating events, updating, deleting, checking availability, finding conflicts, and managing RSVPs.
Fill opportunity forms (jobs, scholarships, grants, fellowships) with strategically crafted, research-backed, human-sounding answers that maximize the chance of getting the opportunity. Trigger when Enrique says "Fill this: [LINK]", "Apply to [LINK]", or "Llena esta postulacion: [LINK]".
Social media content lifecycle — draft, schedule, publish, and analyze posts across X, LinkedIn, Instagram, TikTok with voice matching.
Gmail API integration with managed OAuth. Read, send, and manage emails, threads, labels, and drafts. Use this skill when users want to interact with Gmail. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).
Email across all accounts (Gmail, SpaceMail) — send, search, read, reply, forward, label, delete.
Delegate simple sub-tasks to a fast model (GLM-5). Use for fetch, extract, query, and tool-heavy work that needs minimal reasoning.
Escalate complex tasks to Opus. Use when a task needs deep reasoning, multi-step execution, scoring, creative drafting, or coordination across multiple tools.
| name | calendar |
| description | Full Google Calendar control across all accounts. Use for viewing agenda, creating events, updating, deleting, checking availability, finding conflicts, and managing RSVPs. |
Unified calendar access via calendar_cli tool. Wraps gog calendar for Google Calendar operations.
Uses the same accounts configured in gog. Primary accounts:
| Account | Type |
|---|---|
enriquefft2001@gmail.com | Personal |
enrique.flores@utec.edu.pe | UTEC |
All commands output JSON. Use --account <email> to target a specific account.
calendar_cli calendars [--account <email>]
calendar_cli events [--account <email>] [--calendar <id>] [--from <date>] [--to <date>] [--max <n>]
Default: next 7 days, primary calendar, 20 events max.
calendar_cli get <calendarId> <eventId> [--account <email>]
calendar_cli create --account <email> --calendar <id> --summary <title> --from <datetime> --to <datetime> [--location <loc>] [--description <desc>] [--attendees <email1,email2>]
calendar_cli update --account <email> --calendar <id> --event <eventId> [--summary <title>] [--from <datetime>] [--to <datetime>] [--location <loc>] [--description <desc>]
calendar_cli delete --account <email> --calendar <id> --event <eventId>
calendar_cli search <query> [--account <email>] [--calendar <id>]
calendar_cli freebusy --account <email> --calendars <id1,id2> --from <datetime> --to <datetime>
calendar_cli conflicts [--account <email>] [--from <date>] [--to <date>]
calendar_cli rsvp --account <email> --calendar <id> --event <eventId> --status <accepted|declined|tentative>
calendar_cli focus --account <email> --from <datetime> --to <datetime> # Focus time block
calendar_cli ooo --account <email> --from <datetime> --to <datetime> # Out of office
echo '<json_array>' | calendar_cli batch
Use batch for 2+ create/update/delete operations. Executes sequentially with automatic rate-limit backoff. One call instead of many.
Each operation in the array:
[
{"op": "update", "account": "email", "event": "eventId", "summary": "New Title", "description": "..."},
{"op": "create", "account": "email", "summary": "Title", "from": "2024-03-15T10:00", "to": "2024-03-15T11:00"},
{"op": "delete", "account": "email", "event": "eventId"}
]
Optional fields per op: calendar (default: primary), plus any flags the individual command accepts.
Output: array of {"index": N, "op": "...", "ok": true/false, "result": {...}}.
YYYY-MM-DD (e.g., 2024-03-15)YYYY-MM-DDTHH:MM or YYYY-MM-DD HH:MM (e.g., 2024-03-15T14:30)today, tomorrow, +3d, +1w (where supported)primaryprimary as calendar ID for the main calendar