[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7778TKHWWNMNK7R0SBPXVSW":3,"skill-same:01M7778TKHWWNMNK7R0SBPXVSW":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":58},"01M7778TKHWWNMNK7R0SBPXVSW","meeting-coordinator",null,"Executive scheduling assistant for meeting coordination (email, calendar, venues, confirmations).","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvoshawn\u002Fmeeting-coordinator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: meeting-coordinator\ndescription: Executive scheduling assistant for meeting coordination (email, calendar, venues, confirmations).\nmetadata:\n  openclaw:\n    emoji: \"📅\"\n    requires:\n      bins:\n        - gog\n        - goplaces\n        - python3\n      env:\n        - GOG_ACCOUNT\n        - GOOGLE_PLACES_API_KEY\n    primaryEnv: GOG_ACCOUNT\n    homepage: https:\u002F\u002Fgithub.com\u002Fvoshawn\u002Fmeeting-coordinator-skill\n---\n\n# Meeting Coordinator\n\nOperate as a high-precision executive assistant for scheduling.\n\n## Use This Skill When\n\nUse this skill when the human asks to:\n\n- Schedule a new meeting\n- Reschedule or cancel an existing meeting\n- Respond to or manage a forwarded scheduling email thread\n- Find venues for in-person meetings\n- Send meeting confirmations or follow-ups\n\n## Objective\n\nMinimize scheduling friction while protecting the human's time and reputation:\n\n- Propose high-quality options quickly\n- Prevent calendar conflicts and duplicate bookings\n- Keep every external message on-brand and approved\n- Maintain a complete tracking record\n\n## Required Context\n\n### `USER.md` must provide\n\n- Human full name\n- Human email\n- Calendar ID (may not match email)\n- Home timezone (IANA, e.g. `America\u002FNew_York`)\n- Preferred scheduling windows (days + hours)\n- Default meeting durations by type\n- Travel and post-meeting buffer preferences\n- Location\u002Ftransit preferences\n- Venue preferences\n\n### `SOUL.md` or `IDENTITY.md` must provide\n\n- Assistant tone guidelines\n- Email signature block\n\n### Tools\n\n- `gog` CLI with calendar and Gmail access\n- `goplaces` CLI for venue lookup\n- Local scripts:\n  - `scripts\u002Fcheck-availability.py`\n  - `scripts\u002Ffind-venue.py`\n\nIf required context is missing, ask concise clarification questions before taking action.\n\n## Runtime + Credential Model\n\nThis skill relies on local CLI authentication and local config state.\n\n- Required binaries: `gog`, `goplaces`, `python3`\n- Required environment variables:\n  - `GOG_ACCOUNT`: agent Gmail account identity used by `gog`\n  - `GOOGLE_PLACES_API_KEY`: API key used by `goplaces`\n- Required local config directories:\n  - `$HOME\u002F.config\u002Fgog`\n  - `$HOME\u002F.config\u002Fgoplaces`\n- If `GOG_ACCOUNT` or `GOOGLE_PLACES_API_KEY` is unset, stop and ask the human to configure credentials before continuing.\n\nCredential handling expectations:\n\n- `gog` uses OAuth credentials\u002Ftokens tied to the account selected by `GOG_ACCOUNT`.\n- `goplaces` uses `GOOGLE_PLACES_API_KEY`.\n- Never assume default account selection. Resolve and display the active account before running scheduling actions.\n\nPreflight checks (required before first mutation in a session):\n\n1. Verify account binding: `echo \"$GOG_ACCOUNT\"` and confirm it matches the intended agent Gmail account.\n2. Verify `gog` auth state: `gog auth list`.\n3. Verify `goplaces` key is present: `test -n \"$GOOGLE_PLACES_API_KEY\"`.\n4. Verify target calendar access with a read action before writes.\n\n## Non-Negotiable Rules\n\n### Approval gates\n\n- Always get explicit human approval before:\n  - Sending any email\n  - Creating, updating, or deleting any counterparty-visible calendar event\n  - Cancelling or rescheduling confirmed meetings\n  - Making or modifying reservations\n  - Moving existing events that create conflicts\n- For every mutating action, present the exact command(s) first and wait for explicit approval tied to that action. Prior approvals do not carry forward if details change.\n- **Draft Review Checklist:** When presenting a draft for approval, you must explicitly highlight and confirm:\n    1. **Recipients:** Who exactly is on the To: and CC: lines.\n    2. **Dates & Times:** The specific proposed or confirmed dates and times (clearly labeled with timezones).\n    3. **Location:** The venue name and full address for in-person, or the virtual link for remote meetings.\n\n### Data integrity\n\n- Never fabricate attendee emails, addresses, reservation details, or message IDs.\n- Never use `primary` calendar unless the human explicitly instructs it.\n- Always use timezone-aware timestamps.\n- Always capture and track event IDs after create\u002Fupdate\u002Fdelete actions.\n\n### Calendar construction\n\n- In-person event: include full street address in `--location`.\n- Virtual event: use `--meet` to auto-generate a Google Meet link and leave `--location` unset.\n- Never include both physical location and virtual link for the same event.\n- Travel and buffer blocks are private events with no attendees.\n- **CRITICAL:** Ensure all Travel and Buffer blocks are marked as **Busy** (Opaque) so they block availability. Use the `--transparency busy` flag in the `gog` CLI.\n\n### Communication\n\n- Draft first, then get approval, then send.\n- CC the human on outgoing scheduling messages.\n- Reply in-thread when a thread exists.\n- Match tone and signature from `SOUL.md`\u002F`IDENTITY.md`.\n- Send outbound emails as HTML using `gog gmail send --body-html`.\n- For email time display, use standard US labels (`ET`, `CT`, `MT`, `PT`) instead of IANA timezone IDs.\n- If the counterparty is in a different timezone, include both in one line (example: `3:00 PM ET \u002F 12:00 PM PT`).\n\n## Canonical Meeting Record\n\nTracking file: `memory\u002Fscheduling\u002Fin-progress.md`\nArchive file: `memory\u002Fscheduling\u002Farchive.md`\n\nCreate one entry per meeting and update on every state change.\nNever delete active entries from `in-progress.md`.\n\nRequired fields:\n\n- `meeting_id` (stable local identifier)\n- `counterparty_name`\n- `counterparty_email`\n- `meeting_type` (`virtual` | `coffee` | `lunch` | `dinner` | `other`)\n- `purpose`\n- `timezone`\n- `status`\n- `proposed_options`\n- `selected_option`\n- `calendar_event_ids_active`:\n  - `tentative`\n  - `main`\n  - `travel_to`\n  - `buffer_post`\n  - `travel_home`\n- `calendar_event_ids_deleted` (list of `{event_id, deleted_at, reason}`)\n- `venue` (name + full address, if in-person)\n- `reservation` (`none` | details\u002Fconfirmation code | `phone-needed` | `walk-in`)\n- `thread_context` (subject + message\u002Fthread identifiers when available)\n- `created_at`\n- `updated_at`\n- `activity_log` (append-only)\n\nStatus lifecycle:\n`intake` -> `awaiting-human-approval` -> `awaiting-counterparty` -> `confirmed` -> `completed`\nAlternative terminal states: `cancelled`, `closed-no-response`\n\nAllowed transitions:\n\n- `intake` -> `awaiting-human-approval` | `cancelled`\n- `awaiting-human-approval` -> `awaiting-counterparty` | `cancelled`\n- `awaiting-counterparty` -> `confirmed` | `awaiting-human-approval` | `closed-no-response` | `cancelled`\n- `confirmed` -> `completed` | `awaiting-human-approval` | `cancelled`\n- `completed` | `cancelled` | `closed-no-response` -> eligible for archive move after retention window\n\n### Tracking Entry Template\n\nUse this structure for each meeting entry:\n\n```markdown\n## \u003Cmeeting_id> — \u003Ccounterparty_name>\n- meeting_id: \u003Cmeeting_id>\n- counterparty_name: \u003Cname>\n- counterparty_email: \u003Cemail>\n- meeting_type: \u003Cvirtual|coffee|lunch|dinner|other>\n- purpose: \u003Cshort text>\n- timezone: \u003CIANA timezone>\n- status: \u003Cstatus>\n- proposed_options: \u003Clist or none>\n- selected_option: \u003Coption or none>\n- calendar_event_ids_active:\n  - tentative: []\n  - main: []\n  - travel_to: []\n  - buffer_post: []\n  - travel_home: []\n- calendar_event_ids_deleted: []\n- venue: \u003Cname + full address or none>\n- reservation: \u003Cnone|details>\n- thread_context: \u003Csubject + ids or none>\n- created_at: \u003CISO 8601 timestamp with offset>\n- updated_at: \u003CISO 8601 timestamp with offset>\n\n### Activity Log\n- \u003Ctimestamp> Entry created.\n```\n\n### Editing Protocol (Strict)\n\n1. Locate existing entry by `meeting_id`. If missing, create a new entry.\n2. Update only the relevant entry. Do not rewrite, reorder, or remove unrelated entries.\n3. On every change, update `updated_at` and append a one-line `Activity Log` entry.\n4. Never erase event IDs after calendar deletions.\n5. When an event is deleted\u002Fcancelled, move its ID from `calendar_event_ids_active` to `calendar_event_ids_deleted` with timestamp and reason.\n6. Keep terminal entries in `in-progress.md` until retention rules permit archival.\n\n### Retention and Cleanup Policy (14-Day Rule)\n\nRetention is based on `updated_at`.\n\n- Only remove an entry from `in-progress.md` when BOTH conditions are true:\n  - Status is terminal: `completed` | `cancelled` | `closed-no-response`\n  - `updated_at` is at least 14 days old\n- Preferred action is move (not delete) to `memory\u002Fscheduling\u002Farchive.md`.\n- Non-terminal entries are never auto-deleted, regardless of age.\n- If a non-terminal entry is stale for 14+ days, ask the human what to do; do not auto-close and do not delete.\n\n## Standard Workflow\n\n### 1. Intake\n\n- Extract: who, purpose, meeting type, deadline\u002Furgency, constraints, location context.\n- Resolve missing essentials before proceeding:\n  - Counterparty email\n  - Preferred date range\n  - Meeting type (virtual or in-person)\n- Apply defaults from `USER.md` only when the human has not specified values.\n\n### 2. Availability Search\n\n- Determine duration by meeting type (from request or `USER.md` defaults).\n- Check multiple candidate dates inside preferred windows.\n\n```bash\npython3 scripts\u002Fcheck-availability.py \\\n  --calendar \u003Ccalendar_id> \\\n  --date YYYY-MM-DD \\\n  --duration \u003Cminutes> \\\n  --start-hour \u003C0-23> \\\n  --end-hour \u003C1-24> \\\n  --tz \u003Ciana_timezone>\n```\n\n- Conflict triage:\n  - Hard conflict: multi-attendee commitments, immovable commitments\n  - Soft conflict: personal\u002Ffocus blocks that may be moved\n- Never move conflicts without explicit approval.\n\n### 3. Venue Search (In-Person Only)\n\n```bash\npython3 scripts\u002Ffind-venue.py \\\n  --location \"Neighborhood, City\" \\\n  --type coffee|lunch|dinner \\\n  --min-rating \u003Coptional>\n```\n\n- Generate 2-3 strong venue options.\n- Validate full street address before using it in invites\u002Femails.\n- Filter by transit convenience and stated preferences.\n\n### 4. Build Approval Packet For Human\n\nPresent a concise options table including:\n\n- Date\u002Ftime with display timezone labels (`ET`, `CT`, `MT`, `PT`)\n- Dual-time display when counterparty timezone differs (example: `3:00 PM ET \u002F 12:00 PM PT`)\n- Duration\n- Venue + full address (if in-person)\n- Travel\u002Fbuffer impact\n- Known conflicts and required moves\n- Reservation feasibility\n\nDo not contact the counterparty until the human approves.\n\n### 5. Create Tentative Holds (After Human Approves Options)\n\n- Create one tentative hold per approved option.\n- Use color `8` for tentative.\n- Record every hold event ID immediately.\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"HOLD: \u003CCounterparty Name> (\u003COption Label>)\" \\\n  --from \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --to \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --event-color 8\n```\n\n### 6. Outreach Email\n\n- Use templates in `references\u002Femail-templates.md`.\n- Draft message for approval first.\n- After approval, send and store thread\u002Fmessage identifiers in tracking.\n- Use `--body-html` when sending email.\n\n### 7. Handle Counterparty Response\n\n- `accepted`: move to confirmation workflow.\n- `counter-proposed`: re-run availability and return to human for approval.\n- `declined without alternatives`: ask human whether to close or send fresh options.\n- No response after 2 business days: ask human whether to send follow-up.\n\n### 8. Confirm Meeting\n\n1. Delete unused tentative holds.\n\n```bash\ngog calendar delete \u003Ccalendar_id> \u003Cevent_id> --force\n```\n\nRecord each deleted hold in `calendar_event_ids_deleted` with timestamp and reason.\nDo not delete the meeting entry.\n\n1. Create confirmed main event.\n\nIn-person:\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"\u003CHuman Name> \u002F\u002F \u003CCounterparty Name>\" \\\n  --from \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --to \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --location \"\u003CVenue Name>, \u003CFull Street Address>\" \\\n  --description \"\" \\\n  --attendees \u003Ccounterparty_email>\n```\n\nVirtual:\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"\u003CHuman Name> \u002F\u002F \u003CCounterparty Name>\" \\\n  --from \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --to \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --attendees \u003Ccounterparty_email> \\\n  --meet\n```\n\n1. Add travel and post-meeting blocks when required by preferences.\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"Travel: Home -> \u003CVenue>\" \\\n  --from \"\u003Cstart minus travel>\" \\\n  --to \"\u003Cstart>\" \\\n  --event-color 10\n```\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"Buffer: Post-meeting\" \\\n  --from \"\u003Cmeeting end>\" \\\n  --to \"\u003Cmeeting end plus buffer>\" \\\n  --event-color 10\n```\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"Travel: \u003CVenue> -> Home\" \\\n  --from \"\u003Cbuffer end>\" \\\n  --to \"\u003Cbuffer end plus travel>\" \\\n  --event-color 10\n```\n\n1. Reservation handling (in-person):\n\n- Try online booking first.\n- If online booking unavailable, ask human whether to call.\n- Add reservation details to main event description when confirmed.\n\n1. Send confirmation follow-up email (after approval).\n2. Update tracking record with final event IDs and status `confirmed`.\n\n### 9. Reschedule\n\n1. Get explicit human approval.\n2. Propose new options via Steps 2-4.\n3. Send approved reschedule outreach.\n4. On acceptance: update or recreate events, then move obsolete event IDs to `calendar_event_ids_deleted`.\n5. Do not delete the meeting entry from `in-progress.md`.\n6. Update reservation and tracking.\n\n### 10. Cancel\n\n1. Get explicit human approval.\n2. Cancel or delete all related events.\n3. Cancel reservation when applicable.\n4. Send approved cancellation email.\n5. Mark tracking entry `cancelled` with reason and timestamp.\n6. Keep the cancelled entry in `in-progress.md` until 14-day retention threshold is met, then archive it.\n\n### 11. Day-Before Confirmation\n\nFor in-person or high-stakes meetings:\n\n1. Draft confirmation message.\n2. Get approval and send.\n3. Re-verify reservation details (if any).\n\n## Command Usage Notes\n\n- Prefer absolute timestamps with explicit UTC offsets (`-05:00`, `-08:00`, etc.).\n- Always read command output and capture created\u002Fupdated event IDs.\n- If a command fails, report the error and request next instruction; do not guess.\n- Use IANA timezones internally for calculations and API calls; use `ET`\u002F`CT`\u002F`MT`\u002F`PT` labels in outbound email copy.\n\n## Email Template Reference\n\nUse `references\u002Femail-templates.md` for:\n\n- Initial proposals\n- Invite follow-ups\n- Day-before confirmations\n- Reschedule and cancellation messages\n- No-response nudges\n\n## Quality Bar\n\nBefore finishing any scheduling task, verify:\n\n- Human approvals are documented for every outbound action\n- Calendar is conflict-checked and internally consistent\n- Counterparty communications are concise, accurate, and timezone-clear\n- Tracking file is updated with status, IDs, and timestamps\n- No non-terminal tracking entries were removed from `in-progress.md`\n","# Meeting Coordinator\n\nOperate as a high-precision executive assistant for scheduling.\n\n## Use This Skill When\n\nUse this skill when the human asks to:\n\n- Schedule a new meeting\n- Reschedule or cancel an existing meeting\n- Respond to or manage a forwarded scheduling email thread\n- Find venues for in-person meetings\n- Send meeting confirmations or follow-ups\n\n## Objective\n\nMinimize scheduling friction while protecting the human's time and reputation:\n\n- Propose high-quality options quickly\n- Prevent calendar conflicts and duplicate bookings\n- Keep every external message on-brand and approved\n- Maintain a complete tracking record\n\n## Required Context\n\n### `USER.md` must provide\n\n- Human full name\n- Human email\n- Calendar ID (may not match email)\n- Home timezone (IANA, e.g. `America\u002FNew_York`)\n- Preferred scheduling windows (days + hours)\n- Default meeting durations by type\n- Travel and post-meeting buffer preferences\n- Location\u002Ftransit preferences\n- Venue preferences\n\n### `SOUL.md` or `IDENTITY.md` must provide\n\n- Assistant tone guidelines\n- Email signature block\n\n### Tools\n\n- `gog` CLI with calendar and Gmail access\n- `goplaces` CLI for venue lookup\n- Local scripts:\n  - `scripts\u002Fcheck-availability.py`\n  - `scripts\u002Ffind-venue.py`\n\nIf required context is missing, ask concise clarification questions before taking action.\n\n## Runtime + Credential Model\n\nThis skill relies on local CLI authentication and local config state.\n\n- Required binaries: `gog`, `goplaces`, `python3`\n- Required environment variables:\n  - `GOG_ACCOUNT`: agent Gmail account identity used by `gog`\n  - `GOOGLE_PLACES_API_KEY`: API key used by `goplaces`\n- Required local config directories:\n  - `$HOME\u002F.config\u002Fgog`\n  - `$HOME\u002F.config\u002Fgoplaces`\n- If `GOG_ACCOUNT` or `GOOGLE_PLACES_API_KEY` is unset, stop and ask the human to configure credentials before continuing.\n\nCredential handling expectations:\n\n- `gog` uses OAuth credentials\u002Ftokens tied to the account selected by `GOG_ACCOUNT`.\n- `goplaces` uses `GOOGLE_PLACES_API_KEY`.\n- Never assume default account selection. Resolve and display the active account before running scheduling actions.\n\nPreflight checks (required before first mutation in a session):\n\n1. Verify account binding: `echo \"$GOG_ACCOUNT\"` and confirm it matches the intended agent Gmail account.\n2. Verify `gog` auth state: `gog auth list`.\n3. Verify `goplaces` key is present: `test -n \"$GOOGLE_PLACES_API_KEY\"`.\n4. Verify target calendar access with a read action before writes.\n\n## Non-Negotiable Rules\n\n### Approval gates\n\n- Always get explicit human approval before:\n  - Sending any email\n  - Creating, updating, or deleting any counterparty-visible calendar event\n  - Cancelling or rescheduling confirmed meetings\n  - Making or modifying reservations\n  - Moving existing events that create conflicts\n- For every mutating action, present the exact command(s) first and wait for explicit approval tied to that action. Prior approvals do not carry forward if details change.\n- **Draft Review Checklist:** When presenting a draft for approval, you must explicitly highlight and confirm:\n    1. **Recipients:** Who exactly is on the To: and CC: lines.\n    2. **Dates & Times:** The specific proposed or confirmed dates and times (clearly labeled with timezones).\n    3. **Location:** The venue name and full address for in-person, or the virtual link for remote meetings.\n\n### Data integrity\n\n- Never fabricate attendee emails, addresses, reservation details, or message IDs.\n- Never use `primary` calendar unless the human explicitly instructs it.\n- Always use timezone-aware timestamps.\n- Always capture and track event IDs after create\u002Fupdate\u002Fdelete actions.\n\n### Calendar construction\n\n- In-person event: include full street address in `--location`.\n- Virtual event: use `--meet` to auto-generate a Google Meet link and leave `--location` unset.\n- Never include both physical location and virtual link for the same event.\n- Travel and buffer blocks are private events with no attendees.\n- **CRITICAL:** Ensure all Travel and Buffer blocks are marked as **Busy** (Opaque) so they block availability. Use the `--transparency busy` flag in the `gog` CLI.\n\n### Communication\n\n- Draft first, then get approval, then send.\n- CC the human on outgoing scheduling messages.\n- Reply in-thread when a thread exists.\n- Match tone and signature from `SOUL.md`\u002F`IDENTITY.md`.\n- Send outbound emails as HTML using `gog gmail send --body-html`.\n- For email time display, use standard US labels (`ET`, `CT`, `MT`, `PT`) instead of IANA timezone IDs.\n- If the counterparty is in a different timezone, include both in one line (example: `3:00 PM ET \u002F 12:00 PM PT`).\n\n## Canonical Meeting Record\n\nTracking file: `memory\u002Fscheduling\u002Fin-progress.md`\nArchive file: `memory\u002Fscheduling\u002Farchive.md`\n\nCreate one entry per meeting and update on every state change.\nNever delete active entries from `in-progress.md`.\n\nRequired fields:\n\n- `meeting_id` (stable local identifier)\n- `counterparty_name`\n- `counterparty_email`\n- `meeting_type` (`virtual` | `coffee` | `lunch` | `dinner` | `other`)\n- `purpose`\n- `timezone`\n- `status`\n- `proposed_options`\n- `selected_option`\n- `calendar_event_ids_active`:\n  - `tentative`\n  - `main`\n  - `travel_to`\n  - `buffer_post`\n  - `travel_home`\n- `calendar_event_ids_deleted` (list of `{event_id, deleted_at, reason}`)\n- `venue` (name + full address, if in-person)\n- `reservation` (`none` | details\u002Fconfirmation code | `phone-needed` | `walk-in`)\n- `thread_context` (subject + message\u002Fthread identifiers when available)\n- `created_at`\n- `updated_at`\n- `activity_log` (append-only)\n\nStatus lifecycle:\n`intake` -> `awaiting-human-approval` -> `awaiting-counterparty` -> `confirmed` -> `completed`\nAlternative terminal states: `cancelled`, `closed-no-response`\n\nAllowed transitions:\n\n- `intake` -> `awaiting-human-approval` | `cancelled`\n- `awaiting-human-approval` -> `awaiting-counterparty` | `cancelled`\n- `awaiting-counterparty` -> `confirmed` | `awaiting-human-approval` | `closed-no-response` | `cancelled`\n- `confirmed` -> `completed` | `awaiting-human-approval` | `cancelled`\n- `completed` | `cancelled` | `closed-no-response` -> eligible for archive move after retention window\n\n### Tracking Entry Template\n\nUse this structure for each meeting entry:\n\n```markdown\n## \u003Cmeeting_id> — \u003Ccounterparty_name>\n- meeting_id: \u003Cmeeting_id>\n- counterparty_name: \u003Cname>\n- counterparty_email: \u003Cemail>\n- meeting_type: \u003Cvirtual|coffee|lunch|dinner|other>\n- purpose: \u003Cshort text>\n- timezone: \u003CIANA timezone>\n- status: \u003Cstatus>\n- proposed_options: \u003Clist or none>\n- selected_option: \u003Coption or none>\n- calendar_event_ids_active:\n  - tentative: []\n  - main: []\n  - travel_to: []\n  - buffer_post: []\n  - travel_home: []\n- calendar_event_ids_deleted: []\n- venue: \u003Cname + full address or none>\n- reservation: \u003Cnone|details>\n- thread_context: \u003Csubject + ids or none>\n- created_at: \u003CISO 8601 timestamp with offset>\n- updated_at: \u003CISO 8601 timestamp with offset>\n\n### Activity Log\n- \u003Ctimestamp> Entry created.\n```\n\n### Editing Protocol (Strict)\n\n1. Locate existing entry by `meeting_id`. If missing, create a new entry.\n2. Update only the relevant entry. Do not rewrite, reorder, or remove unrelated entries.\n3. On every change, update `updated_at` and append a one-line `Activity Log` entry.\n4. Never erase event IDs after calendar deletions.\n5. When an event is deleted\u002Fcancelled, move its ID from `calendar_event_ids_active` to `calendar_event_ids_deleted` with timestamp and reason.\n6. Keep terminal entries in `in-progress.md` until retention rules permit archival.\n\n### Retention and Cleanup Policy (14-Day Rule)\n\nRetention is based on `updated_at`.\n\n- Only remove an entry from `in-progress.md` when BOTH conditions are true:\n  - Status is terminal: `completed` | `cancelled` | `closed-no-response`\n  - `updated_at` is at least 14 days old\n- Preferred action is move (not delete) to `memory\u002Fscheduling\u002Farchive.md`.\n- Non-terminal entries are never auto-deleted, regardless of age.\n- If a non-terminal entry is stale for 14+ days, ask the human what to do; do not auto-close and do not delete.\n\n## Standard Workflow\n\n### 1. Intake\n\n- Extract: who, purpose, meeting type, deadline\u002Furgency, constraints, location context.\n- Resolve missing essentials before proceeding:\n  - Counterparty email\n  - Preferred date range\n  - Meeting type (virtual or in-person)\n- Apply defaults from `USER.md` only when the human has not specified values.\n\n### 2. Availability Search\n\n- Determine duration by meeting type (from request or `USER.md` defaults).\n- Check multiple candidate dates inside preferred windows.\n\n```bash\npython3 scripts\u002Fcheck-availability.py \\\n  --calendar \u003Ccalendar_id> \\\n  --date YYYY-MM-DD \\\n  --duration \u003Cminutes> \\\n  --start-hour \u003C0-23> \\\n  --end-hour \u003C1-24> \\\n  --tz \u003Ciana_timezone>\n```\n\n- Conflict triage:\n  - Hard conflict: multi-attendee commitments, immovable commitments\n  - Soft conflict: personal\u002Ffocus blocks that may be moved\n- Never move conflicts without explicit approval.\n\n### 3. Venue Search (In-Person Only)\n\n```bash\npython3 scripts\u002Ffind-venue.py \\\n  --location \"Neighborhood, City\" \\\n  --type coffee|lunch|dinner \\\n  --min-rating \u003Coptional>\n```\n\n- Generate 2-3 strong venue options.\n- Validate full street address before using it in invites\u002Femails.\n- Filter by transit convenience and stated preferences.\n\n### 4. Build Approval Packet For Human\n\nPresent a concise options table including:\n\n- Date\u002Ftime with display timezone labels (`ET`, `CT`, `MT`, `PT`)\n- Dual-time display when counterparty timezone differs (example: `3:00 PM ET \u002F 12:00 PM PT`)\n- Duration\n- Venue + full address (if in-person)\n- Travel\u002Fbuffer impact\n- Known conflicts and required moves\n- Reservation feasibility\n\nDo not contact the counterparty until the human approves.\n\n### 5. Create Tentative Holds (After Human Approves Options)\n\n- Create one tentative hold per approved option.\n- Use color `8` for tentative.\n- Record every hold event ID immediately.\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"HOLD: \u003CCounterparty Name> (\u003COption Label>)\" \\\n  --from \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --to \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --event-color 8\n```\n\n### 6. Outreach Email\n\n- Use templates in `references\u002Femail-templates.md`.\n- Draft message for approval first.\n- After approval, send and store thread\u002Fmessage identifiers in tracking.\n- Use `--body-html` when sending email.\n\n### 7. Handle Counterparty Response\n\n- `accepted`: move to confirmation workflow.\n- `counter-proposed`: re-run availability and return to human for approval.\n- `declined without alternatives`: ask human whether to close or send fresh options.\n- No response after 2 business days: ask human whether to send follow-up.\n\n### 8. Confirm Meeting\n\n1. Delete unused tentative holds.\n\n```bash\ngog calendar delete \u003Ccalendar_id> \u003Cevent_id> --force\n```\n\nRecord each deleted hold in `calendar_event_ids_deleted` with timestamp and reason.\nDo not delete the meeting entry.\n\n1. Create confirmed main event.\n\nIn-person:\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"\u003CHuman Name> \u002F\u002F \u003CCounterparty Name>\" \\\n  --from \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --to \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --location \"\u003CVenue Name>, \u003CFull Street Address>\" \\\n  --description \"\" \\\n  --attendees \u003Ccounterparty_email>\n```\n\nVirtual:\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"\u003CHuman Name> \u002F\u002F \u003CCounterparty Name>\" \\\n  --from \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --to \"YYYY-MM-DDTHH:MM:SS\u003Coffset>\" \\\n  --attendees \u003Ccounterparty_email> \\\n  --meet\n```\n\n1. Add travel and post-meeting blocks when required by preferences.\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"Travel: Home -> \u003CVenue>\" \\\n  --from \"\u003Cstart minus travel>\" \\\n  --to \"\u003Cstart>\" \\\n  --event-color 10\n```\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"Buffer: Post-meeting\" \\\n  --from \"\u003Cmeeting end>\" \\\n  --to \"\u003Cmeeting end plus buffer>\" \\\n  --event-color 10\n```\n\n```bash\ngog calendar create \u003Ccalendar_id> \\\n  --summary \"Travel: \u003CVenue> -> Home\" \\\n  --from \"\u003Cbuffer end>\" \\\n  --to \"\u003Cbuffer end plus travel>\" \\\n  --event-color 10\n```\n\n1. Reservation handling (in-person):\n\n- Try online booking first.\n- If online booking unavailable, ask human whether to call.\n- Add reservation details to main event description when confirmed.\n\n1. Send confirmation follow-up email (after approval).\n2. Update tracking record with final event IDs and status `confirmed`.\n\n### 9. Reschedule\n\n1. Get explicit human approval.\n2. Propose new options via Steps 2-4.\n3. Send approved reschedule outreach.\n4. On acceptance: update or recreate events, then move obsolete event IDs to `calendar_event_ids_deleted`.\n5. Do not delete the meeting entry from `in-progress.md`.\n6. Update reservation and tracking.\n\n### 10. Cancel\n\n1. Get explicit human approval.\n2. Cancel or delete all related events.\n3. Cancel reservation when applicable.\n4. Send approved cancellation email.\n5. Mark tracking entry `cancelled` with reason and timestamp.\n6. Keep the cancelled entry in `in-progress.md` until 14-day retention threshold is met, then archive it.\n\n### 11. Day-Before Confirmation\n\nFor in-person or high-stakes meetings:\n\n1. Draft confirmation message.\n2. Get approval and send.\n3. Re-verify reservation details (if any).\n\n## Command Usage Notes\n\n- Prefer absolute timestamps with explicit UTC offsets (`-05:00`, `-08:00`, etc.).\n- Always read command output and capture created\u002Fupdated event IDs.\n- If a command fails, report the error and request next instruction; do not guess.\n- Use IANA timezones internally for calculations and API calls; use `ET`\u002F`CT`\u002F`MT`\u002F`PT` labels in outbound email copy.\n\n## Email Template Reference\n\nUse `references\u002Femail-templates.md` for:\n\n- Initial proposals\n- Invite follow-ups\n- Day-before confirmations\n- Reschedule and cancellation messages\n- No-response nudges\n\n## Quality Bar\n\nBefore finishing any scheduling task, verify:\n\n- Human approvals are documented for every outbound action\n- Calendar is conflict-checked and internally consistent\n- Counterparty communications are concise, accurate, and timezone-clear\n- Tracking file is updated with status, IDs, and timestamps\n- No non-terminal tracking entries were removed from `in-progress.md`\n",{"name":5,"metadata":24,"description":7},{"openclaw":25},{"emoji":26,"homepage":27,"requires":28,"primaryEnv":30},"📅","https:\u002F\u002Fgithub.com\u002Fvoshawn\u002Fmeeting-coordinator-skill",{"env":29,"bins":32},[30,31],"GOG_ACCOUNT","GOOGLE_PLACES_API_KEY",[33,34,35],"gog","goplaces","python3","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fvoshawn\u002Fmeeting-coordinator",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill meeting-coordinator",{"tool":51,"command":52},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill meeting-coordinator",{"tool":54,"command":55},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill meeting-coordinator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fvoshawn\u002Fmeeting-coordinator\u002FSKILL.md",true,[],[60,67,74,81,88,95],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]