People ops
Attrition Hotspots
Describe observed aggregate attrition patterns.
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
Describe observed aggregate attrition patterns.
What it covers
Inputs
Team/cohort, period, denominator definition, reporting policy.
Result
Aggregate attrition patterns, denominator/coverage and evidenced contributing context.
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 Attrition Hotspots is disconnected or stale, say so up front.
- Resolve inputs for Attrition Hotspots: 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 inputs.
- keep_memory_read for open tasks, decisions, and handoffs relevant to Attrition Hotspots (filter out unrelated day-plan noise).