People ops
Onsite Interview Day Plan
Build a feasible interview-day itinerary.
Configure this skill
The page and the file follow your answers.
CRM
Email
Chat
Documents
Calendar
Project tools
6 of 6 systems connected
KeepDirectMissing
Your assistantSKILL.md
Download ↓
When to use it
Build a feasible interview-day itinerary.
What it covers
Inputs
Candidate/interviewers, timezone, availability, interview stages.
Result
Proposed itinerary, interviewer responsibilities and unresolved availability.
What it uses
People recordsCalendarEmailDocumentsSlackCRMRead only
For developers
Retrieval instructions
Resolve people, accounts and projects by stable identifiers. Use only the sources this task needs. Cite the source and date for each finding. Keep source systems unchanged.
Data sources
Rippling, Google Workspace, Slack, Attio.
Procedure
- Call keep_status and report freshness for: Rippling, Google Workspace, Slack, Attio. If a required connector for Onsite Interview Day Plan is disconnected or stale, say so up front.
- Resolve inputs for Onsite Interview Day Plan: role, candidate, req_id, time_window. Default time window: open reqs and active interview loops (override if caller provides time_window). Ask only for missing critical.
- keep_memory_read for open tasks, decisions, and handoffs relevant to Onsite Interview Day Plan (filter out unrelated day-plan noise).