LISTENINGPOST

People & organization

Team Roster Snapshot

List the verified membership of a team at a cutoff.

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 ↓ 
Morning Brief

Build a prioritized brief for today from the caller's calendar, messages, documents and project records, using Keep MCP. Read only.

1. Read today's calendar events, open assigned tasks, direct requests since the last brief and unresolved commitments.
2. Separate active incidents, decisions waiting on the caller, external deadlines and routine work. Check for replies before calling an item outstanding. Rank by consequence and time remaining.
3. Fit proposed actions around fixed meetings and flag conflicting commitments.

Result: a dated brief with urgent changes, commitments, meeting preparation and a feasible next-action list, each tied to its source.

When to use it

List the verified membership of a team at a cutoff.

What it covers

Inputs

Team ID and cutoff

Result

Dated roster and membership exceptions.

What it uses

People recordsCalendarEmailDocumentsSlackRead 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.

Procedure

  1. Call keep_status and report freshness for: Rippling, Google Workspace, Slack. If a required connector for Team Roster Snapshot is disconnected or stale, say so up front.
  2. Resolve inputs for Team Roster Snapshot: person, team, system_name, project_key. Default time window: current org context (refresh if >30d stale) (override if caller provides time_window). Ask only for missing.
  3. Run keep_search with these skill-specific intents (keep meaning; adjust wording to corpus):

Related skills

People & organization →
Weekly People Pulse→Prepare a weekly people/ownership update. Uses person, team, system name, project key.Who Owns This System→Locate accountable ownership for a system.Working Style Notes→Summarize explicitly stated work preferences.