anthropic-admin-seat-inventorylisted
Install: claude install-skill WYRE-AI/msp-claude-plugins
# Anthropic Seat Inventory
## Overview
An MSP that supplies or manages Claude for a client needs to answer three
questions on a schedule: how many seats are in use, who holds the
powerful roles, and whether people who left still have access. This skill
answers them from the Admin API. It reads only; removing a user or
revoking an invite is done by a client admin in Claude Console.
## Anti-triggers
- **API keys a leaver created** — keys outlive their creator's seat; use
[key-and-audit-review](../key-and-audit-review/SKILL.md) (admin-gated).
- **Who is actually using Claude Code** — membership is not usage; use
[claude-code-adoption](../claude-code-adoption/SKILL.md).
## Key Concepts
- **Organization role** (`role` on a user). Console and API orgs use
`user`, `developer`, `billing`, `admin`, and `claude_code_user`. Claude
Enterprise orgs use `user`, `owner`, `primary_owner`,
`membership_admin`, and `managed`. Filter with the `roles` argument.
- **Invites** have a status of `pending`, `accepted`, or `expired`. A
pending invite is a seat about to be taken; an old pending invite to a
departed person is still a way in once accepted.
- **Workspaces** split keys, usage, and limits. A user can belong to the
org but to only some workspaces, each with its own workspace role. The
default workspace is hidden unless you pass `include_default: true`;
archived workspaces need `include_archived: true`.
## Workflows
### Seat count
1. `anthropic_admin_organization_g