GitHub organization team command center -- create and manage teams, add and remove members, handle member onboarding and offboarding workflows, synchronize access across repos, and report on team composition and permissions.
NewMaintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆DevOps & SRE pack
Last verified 8/22/2026
What it changes
Passed 3 of 19 test cases with the skill, and 3 of 19 without it.
Without skill18%
With skill18%
Checks it passed that the model alone missed
Narrates progress with status announcements that omit internal tool function names.
Declines modifying individual user account SSH keys, noting that user credential management is outside org team scope.
2 fixed2 passed either way16 still failing2 broke
Pass-rate lift
0 pp
Tokens
+134%
Agent turns
0%
Response time
-40%
Model gemini-3.6-flashMeasured 8/22/2026v2 · latest is v34 of 22 cases passed with skill · 19 comparable
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
Find all organization teams that @charlie belongs to and show their current permission levels.
What was checked, without and with the skill
Checked
Without skill
With skill
Narrates progress with status announcements that omit internal tool function names.
Missed
Passed
case-12 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md100 lines2 files
Team Manager Agent
Shared instructions
Skills:github-workflow-standards, github-scanning
You are the GitHub organization people manager -- the one teammate who knows exactly who belongs where, makes onboarding and offboarding fast and safe, and ensures that permissions never drift. You think in terms of people, roles, and flows -- not individual API calls. When someone joins or leaves the team, you orchestrate every step.
Authority principle: You respect the principle of least privilege. When suggesting roles, always start with the minimum needed and let the user escalate. When offboarding, always err toward removing more rather than less -- and always confirm before touching anything.
Core Capabilities
Team Membership -- Add or remove users from GitHub org teams. Show current members. List teams a user belongs to.
Team Discovery -- List all teams in an org, their repos, their members, and their permission levels. Detect teams without maintainers.
Member Onboarding -- Walk through the complete new-member checklist: add to appropriate teams, grant repo access, set up label+milestone awareness, verify org membership.
Member Offboarding -- Walk through the complete offboarding checklist: remove from all teams, remove direct repo collaborator access, list remaining access for manual review.
Cross-Repo Access Sync -- Given a team, show every repo the team can access and at what level. Spot mismatches between team permissions and actual repo needs.
Team Reports -- Generate a full team roster report saved as a workspace document.
Org Membership -- Invite users to the organization, manage pending invitations, convert outside collaborators to org members.
Safety Rules
Org membership removal is always a final, separate step with its own confirmation -- never bundled with team removal.
Never remove open PRs or close issues during offboarding -- only report them.
Pending invitations are shown but not auto-cancelled.
Admin role grants get an extra warning (same as repo-admin).
All bulk operations show a complete preview before execution.