clickmax-team-members
Use when the user asks who is on the workspace team, how a specific teammate is doing (open opportunities, recent activity, last access), or needs to resolve a person to the right id before acting on
SKILL.mdskills/clickmax-team-members/SKILL.md
GitHubWhen this applies
Questions about PEOPLE of the workspace: the roster (roles, pending invitations, deactivated seats), one person's profile and work volume, and turning a name into the id another tool needs.
Not this skill:
- the team's task/appointment queue itself ->
clickmax-activities - assigning cards or routing rules ->
clickmax-pipelines - inviting, removing or changing a person's role/job roles -> web app only (Members screen); no tool does it
Key assumptions
- one person, four ids — never interchange them:
- user id =
idinmcp__plugin_clickmax_clickmax__workspace_members_list=userIdofmcp__plugin_clickmax_clickmax__workspace_members_get,mcp__plugin_clickmax_clickmax__drive_people_get, Drive shares/members =personIdinmcp__plugin_clickmax_clickmax__attendants_list - attendant id =
attendantIdfrommcp__plugin_clickmax_clickmax__workspace_members_get=idinmcp__plugin_clickmax_clickmax__attendants_list-> the only idcards_list/tasks_list/activities_listaccept (attendantIds) - seat id =
seatId, only identifies the seat
- user id =
attendantId = null(pending invitation, or management-only person) -> that person has no opportunities/tasks to look up; say sostatus:pending= invited, not accepted |active|removed= deactivated (reactivable in the app); people removed for good are not listed at allroleowner | admin | member;permissionGroups= job roles, power = union; empty is normal for owner/admin, "reaches nothing" for a member- profile
stats:opportunities= OPEN cards where the person is the responsible attendant;leads= distinct contacts on them;activities= timeline actions in the last 8 weeks;activitySeries= 8 rolling 7-day buckets, oldest first, last = most recent 7 days - permissions: roster needs
workspaceread; profile andwithStatsneedseatsread (403 otherwise) -> fall back to the plain roster and say the numbers need the Members permission
Thought process
- Name ->
mcp__plugin_clickmax_clickmax__workspace_members_listwithsearch(name, then e-mail if nothing). Several matches -> ask. - Headline about one person ->
mcp__plugin_clickmax_clickmax__workspace_members_get; go deeper only withattendantIdin the CRM tools. - Team comparison ->
mcp__plugin_clickmax_clickmax__workspace_members_listwithwithStats: true, reading EVERY pagemeta.countPagesreports (raiseperPageto cut round-trips, never to skip pages) — not N profile calls. Compare only after the last page.
Execute guide
- Roster:
mcp__plugin_clickmax_clickmax__workspace_members_list(statusto filter pending/active/removed;meta.countItens= total). Read every pagemeta.countPagesreports before saying someone is missing. - One person:
mcp__plugin_clickmax_clickmax__workspace_members_getwithuserId-> role, member since, invited by, job roles, last access, stats. - Their work:
attendantId->mcp__plugin_clickmax_clickmax__cards_list(attendantIds,status = open),mcp__plugin_clickmax_clickmax__tasks_list/mcp__plugin_clickmax_clickmax__activities_list(attendantIds, plusoverduefor what is late). - Their files:
mcp__plugin_clickmax_clickmax__drive_people_getwith the user id (numbers limited to what the caller can see).
Report
- Person header: name, role, status, "no workspace desde" date, last access (or "sem acesso registrado").
- Work volume: open opportunities, contacts, actions in 8 weeks with the trend of the series (rising/falling, current week vs average); never invent targets.
- Roster: group by status (active, pending, deactivated), up to 20 names,
+N more. - Follow-up actions (reassigning cards, closing tasks) are opt-in only.
Warnings
activitiesin stats is timeline volume, not the tasks/appointments ofactivities_list; do not mix the two numbers.- Stats only cover CRM work; automations, pages and funnels have no author tracking.
- A plain attendant session sees only its own items in the CRM tools even with another person's
attendantId.
Anti-patterns
- Passing a user id as
attendantIds, or an attendant id asuserId. - Concluding "not in the workspace" from
attendants_listalone (admins and pending invitations have no attendant profile). - Calling
workspace_members_getper row to rank a whole team.
Clickmax skill revision: 30bc1243c2ed