What problem does it solve? When a platform access token leaks, gets committed, or stops authenticating, you need to revoke it fast and issue a replacement without touching anyone else's credentials. This Skill guides an agent through managing the access of the person in front of it — tokens, active team, and client install — on the zz-stack platform. ## Core Features & Use Cases - Token lifecycle management: Issue personal access tokens with pat_issue, list them masked with pat_list, and revoke compromised ones immediately with pat_revoke before minting a replacement. - Team context control: Show which team a user is acting as with team_mine and switch it with team_switch, so documents land in the correct team's store. - Client onboarding: Print a per-person Claude Code install with client_setup, pairing it with a token exported as ZZ_TOKEN so the credential never enters a committable file. - Use Case: A developer realizes their token appeared in a screen recording. The agent lists their tokens, revokes the exposed id, confirms it is dead, and issues a replacement under the same label. ## Quick Start Ask the agent to revoke my leaked platform token and issue me a replacement, then show my client setup commands.
