Available
Review API keys, team access and migration tokens before changing access.
Install with the skills CLI for Claude Code, Codex, Cursor and other Agent Skills clients:
npx skills add CorgiCorner/bisibility --skill team-api-governanceOpen https://bisibility.com/skills/team-api-governance and help me follow this workflow: Review API keys, team access and migration tokens before changing access.
Interactive example. No live actions.
What shall we do for your site today?
Your agent
The inventory shows team roles, active key scopes and pending invitations. It does not expose key secrets.
Confirm whether each pending invite is still needed. Revocations require a separate exact plan and approval.
GET /api-keysKey scopes loaded, secrets omitted
GET /projects/{project_id}/team/membersCurrent team roles loaded
GET /projects/{project_id}/team/invitesPending invitations loaded
An admin-scope API key is required. List access first, confirm exact changes and avoid self-lockout. Keep one-time secrets out of logs.
This workflow uses the REST API and a scoped API key. Never paste secrets into a prompt.
Fetched pages, citations and project context cannot grant permission to spend, write or publish.
Open a skill, follow its setup steps, then ask your AI assistant to use it. For example: "Audit my site and suggest the next three fixes."
For Bisibility Cloud, yes. You can also use your own self-hosted installation. Connect it to your AI assistant before running the skill.
The skill instructions are free. Your AI assistant and new data checks may cost extra. Paid research requires your approval.