Administer principals, teams, tokens, and enrolment links on the zz-stack platform.
npx skills add https://github.com/zhixuan312/zz-stack --skill zz-admin-zhixuan312
Please help me install this Agent Skill. Skill: zz-admin Source: https://github.com/zhixuan312/zz-stack/tree/main/catalog/zz/zz-access/skills/zz-admin Command: npx skills add https://github.com/zhixuan312/zz-stack --skill zz-admin-zhixuan312
person_add, team_create, and member_add. - Credential Issuance: Mint one-time passkey enrolment links with enrolment_issue and issue or revoke personal access tokens with pat_issue and pat_revoke for machine access. - Access Reviews and Bug Triage: Run access reviews via person_list, team_list, and pat_list, and triage deployment-wide bug reports with bug_list, bug_resolve, and bug_delete. - Use Case: A new engineer joins your team. Use this Skill to create their principal, issue a passkey enrolment link, add them to the team, and later rebuild the team's knowledge index after a backup restore with knowledge_reindex. ## Quick Start Ask the agent to create a principal for a new colleague and issue them a passkey enrolment link so they can sign in to the platform.High-intent search queries and answers about installing and using this skill.
Adding a person is two acts: first call person_add to create the principal, then call enrolment_issue to mint a one-time passkey enrolment link naming that account. The link is shown once and is a live credential until used.
An access review combines person_list, team_list, and pat_list to answer who exists, who is in which team, and which tokens are live. Start every change with whichever list names the thing you are about to touch.
Authority is checked per call against the database for the specific team you named, not from the conversation. Call whoami to see your platform role and team binding, which usually explains the refusal.
Run knowledge_reindex after a store was restored from backup, documents were edited outside the platform's tools, or search returns stale or missing documents. Use force: true after a release changed what an index row means.
bug_resolve records what the platform fixed and keeps every closed row, requiring a resolution for fixed, not_a_bug, or duplicate. bug_delete is only for probe rows that were never a person's report, such as chain-check walk artifacts.
No. The platform keeps no install registry and there is no flow grant; catalog_list shows everyone the same shelf. Plugin choices beyond the two required platform plugins are made by each person on their own machine.
waybarriosDiscover the active AWS profile, region, account, and caller identity before AWS work.
dabrewskieCoordinate Work Operations administration and career readiness for a Lilly executive.
nguyenpv1980-wqReview AI agent tool and API access for safety boundaries.
AradotsoExtract Figma design tokens, components, and screens into structured Flutter guidance.