Onboarding
Tooling Access Checklist Context
Identify access required by a role and its actual request path.
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
Identify access required by a role and its actual request path.
What it covers
Inputs
Role/team, systems, current access evidence.
Result
Required/current/pending access checklist with request path and unresolved status.
What it uses
People recordsCalendarEmailDocumentsSlackProject toolsKeep memory
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, Linear, Keep memory.
Procedure
- Call keep_status and report freshness for: Rippling, Google Workspace, Slack, Linear, Keep memory. If a required connector for Tooling Access Checklist Context is disconnected or stale, say so up front.
- Resolve inputs for Tooling Access Checklist Context: person, role, project_key, day_n. Default time window: ramp plan window (first 30/60/90 days) (override if caller provides time_window). Ask only for missing.
- keep_memory_read for open tasks, decisions, and handoffs relevant to Tooling Access Checklist Context (filter out unrelated day-plan noise).