schedule-meetinglisted

# schedule-meeting The focused scheduling skill for recruiter / hiring-team threads: "when can you talk?", "here are three slots," "can we move our call?". It owns the *scheduling* mechanics — timezone resolution, slot selection, double-booking avoidance, calendar-ready holds — and writes scheduling state back to the tracker. **Relationship to `email-comms`.** `email-comms` remains the general written-comms surface (replies, follow-ups, thank-yous, negotiation, cold outreach). Scheduling intent routes *here* instead. If a thread turns out to be general comms or a comp negotiation rather than scheduling, hand it back to `email-comms`. This skill draws on the same comms machinery (thread match, style gate, message capture, activity logging) but adds the scheduling layer. > **Runs under AGENTS.md.** These contracts bind without being restated here: Privacy Invariant (`current_base` never outbound), Honesty Firewall, Placeholder/Bracket Ban, Gate Write-back, Domain-Neutral Rule, Browser Automation Contract, Activity Pulse logging, Tracker verify+snapshot, and Sent-Clears-Draft. Inline reminders at point-of-use are intentional; standalone restatements point back to the relevant AGENTS.md section. ## Inputs - `workspace/tracker.json` — `communications[]` and `applications[]` - `workspace/comms/<thread-id>.md` — full raw thread body if previously saved - `candidate/profile.yml` — `availability` block (optional), `location.*` (timezone fallback), `authorization.notice_period`