Agent skill

Team Manager

by Community-Access in Community-Access/accessibility-agents

GitHub org teams: create, staff, onboard, offboard and audit access.

Install Team Manager

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill team-manager -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents team-manager --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/team-manager .claude/skills/team-manager && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "team-manager" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/team-manager into .claude/skills/team-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-manager", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/team-manager

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill team-manager -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents team-manager --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/team-manager .agents/skills/team-manager && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "team-manager" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/team-manager into .agents/skills/team-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-manager", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill team-manager -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents team-manager --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/team-manager .cursor/skills/team-manager && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "team-manager" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/team-manager into .cursor/skills/team-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-manager", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/team-manager

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill team-manager -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents team-manager --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/team-manager .gemini/skills/team-manager && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "team-manager" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/team-manager into .gemini/skills/team-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-manager", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents team-manager

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill team-manager -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/team-manager .github/skills/team-manager && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "team-manager" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/team-manager into .github/skills/team-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-manager", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill team-manager -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents team-manager --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/team-manager .opencode/skills/team-manager && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "team-manager" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/team-manager into .opencode/skills/team-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-manager", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: team-manager
GitHub stars: 422
Token cost: ~1.4k tokens
SKILL.md length: 623 words
Files: 3 (incl. references)
Skills in repo: 108
Repo updated: Sep 23, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

GitHub org teams: create, staff, onboard, offboard and audit access.

Works in 7 steps: Team Membership -- Add or remove users… → Team Discovery -- List all teams in an… → Member Onboarding -- Walk through the… → …
Frontend & Design work in your project
SKILL.md covers Team Manager Agent, Core Capabilities, Safety Rules and Output Format, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Team Manager is an agent skill from Community-Access/accessibility-agents. GitHub org teams: create, staff, onboard, offboard and audit access.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/workflow.md`).

It sits in Frontend & Design. It works with GitHub. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.

When your agent uses it

Frontend & Design work in your project

Example prompts

“/team-manager”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

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…
Member Offboarding -- Walk through the complete offboarding checklist: remove from all teams, remove direct repo collaborator access, list…
Cross-Repo Access Sync -- Given a team, show every repo the team can access and at what level. Spot mismatches between team permissions…
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.

What it can do on your machine

Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Team Manager loads about 1.4k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 20 tokens; SKILL.md has 623 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~20
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 623 words, ~1,359 tokens.

Download SKILL.mdSave it as .claude/skills/team-manager/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: team-manager
description: GitHub org teams: create, staff, onboard, offboard and audit access.
license: MIT
disable-model-invocation: true
metadata.tier: specialist
metadata.domain: github
metadata.output: guidance
metadata.effort: medium
metadata.title: Team Manager

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.

Output Format

Save multi-step reports as workspace documents:

Onboarding record: .github/reviews/admin/onboarding-{username}-{YYYY-MM-DD}.md
Offboarding record: .github/reviews/admin/offboarding-{username}-{YYYY-MM-DD}.md
Team report: .github/reviews/admin/team-report-{YYYY-MM-DD}.md

Follow the dual output and accessibility standards in shared-instructions.md.

After any people management operation, offer:

"Use @repo-admin to also check direct repo collaborator access for this user."
"Want to run a full access audit after this change?"
"Use /repo-audit to generate a complete permissions snapshot."

Progress Announcements

Narrate every step. Never mention tool names:

text

 Looking up team membership for {org}...
 Checking existing repo access for @{username}...
 Ready to onboard @{username} - previewing changes before confirming.

For offboarding:

text

 Scanning all org teams and repos for @{username}...
 Checking for open PRs, assigned issues, and pending invitations...
 Offboarding checklist ready - {N} access entries to remove. Review before proceeding.

Show full SKILL.md (244 more words)Show less

Behavioral Rules

Check workspace context first. Look for scan config files (.a11y-*-config.json) and previous audit reports in the workspace root.
Narrate every step with / announcements during membership lookup, access scan, and change execution.
Least privilege always. Suggest the minimum required role; let the user escalate deliberately.
Confirm before any access change. Add, remove, or modify membership only after explicit user approval.
Org removal is always a final, separate step. Never bundle with team removal.
Never remove open PRs or close issues during offboarding - report them, let the user decide.
Show full offboarding checklist before executing any step - no partial executions without a complete preview.
Admin role grants get an extra warning. Admin access is harder to audit after the fact.
Pending invitations shown but not auto-cancelled. User decides.
Dual output for multi-step reports. Onboarding and offboarding records saved as both .md and .html.
Audit log reference. After any operation, tell the user the audit log path.
Proactive follow-up. After onboarding, suggest running a repo-admin access audit for the same user.

Reference files

Read one only when the task reaches it. Do not read them all up front.

references/workflow.md - Workflow

Output contract

Answer the question. Keep the answer to what was asked, cite the criterion or API by name, and stop. Do not append a checklist that was not requested.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

Files

SKILL.md and 2 other files (references) in skills/team-manager of Community-Access/accessibility-agents.

SKILL.md
agents/openai.yaml
references/workflow.md

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Team Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Team Manager compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Team Manager this skillCommunity-Access/accessibility-agents	422	—	~1.4k	Automated safety check: Pass	MIT	15 days ago
Scraps Reviewgetsentry/sentry	46k	—	~1.2k	Automated safety check: Notes	Custom licence	today
Readme I18nY80/bmm	344	2 repos	~1.9k	Automated safety check: Pass	MIT	4 mo ago
Uncodixfypdsuwwz/chatgpt-vue3-light-mvp	578	2 repos	~3k	Automated safety check: Pass	MIT	2 mo ago
Paper2htmlQuZhan51496/paper2anything	468	—	~3.3k	Automated safety check: Notes	Apache-2.0	2 mo ago
Fumadocsbetter-notify/better-notify	313	—	~2.3k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Scraps Review
getsentry/sentry
Official
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…
46k GitHub stars~1.2k tokensUpdated today
Frontend & DesignAuto-check: notes
Readme I18n
Y80/bmm
A skill your agent uses when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized…
344 GitHub starsUsed in 2 repos~1.9k tokens
Frontend & DesignAuto-check passed
Uncodixfy
pdsuwwz/chatgpt-vue3-light-mvp
Prevents generic AI/Codex UI patterns when generating frontend code.
578 GitHub starsUsed in 2 repos~3k tokens
Frontend & DesignAuto-check passed
Paper2html
QuZhan51496/paper2anything
Convert an academic paper PDF into a publish-ready, self-contained single-page project homepage (a self-contained index.html) — the kind of paper landing page researchers host on GitHub Pages.
468 GitHub stars~3.3k tokensUpdated 2 mo ago
Frontend & DesignAuto-check: notes
Fumadocs
better-notify/better-notify
A skill your agent uses when writing MDX documentation pages for a Fumadocs project — frontmatter, meta.json, page ordering, and fumadocs-ui React components available inside MDX content.
313 GitHub stars~2.3k tokensUpdated 1 mo ago
Frontend & DesignAuto-check passed
Great Docs
pymc-labs/pathmc
Generate documentation sites for Python packages with Great Docs.
132 GitHub stars~2.7k tokensUpdated 5 days ago
Frontend & DesignAuto-check passed

Questions about Team Manager

What does Team Manager do?

GitHub org teams: create, staff, onboard, offboard and audit access. Team Manager is an agent skill from Community-Access/accessibility-agents. GitHub org teams: create, staff, onboard, offboard and audit access.

When should I use Team Manager?

Team Manager fits situations like: frontend & Design work in your project.

How do I install Team Manager in Claude Code?

Run `npx skills add Community-Access/accessibility-agents --skill team-manager -a claude-code`. Or copy the skill folder (skills/team-manager in Community-Access/accessibility-agents) into .claude/skills/team-manager in your project. Claude Code loads it when a task matches its description.

How do I install Team Manager in Codex?

Run `npx skills add Community-Access/accessibility-agents --skill team-manager -a codex`. Or copy the skill folder (skills/team-manager in Community-Access/accessibility-agents) into .agents/skills/team-manager in your project. Codex loads it when a task matches its description.

Can I use Team Manager in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill team-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-manager, .gemini/skills/team-manager, .github/skills/team-manager and .opencode/skills/team-manager in your project.

What does Team Manager need to run?

SKILL.md names no scripts, command-line tools or credentials: Team Manager is instructions for the agent only.

Does Team Manager access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Team Manager safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Team Manager use?

Team Manager is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Team Manager use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Team Manager?

Skills that share tags, products or a category with Team Manager: Scraps Review (getsentry/sentry, 46k stars), Readme I18n (Y80/bmm, 344 stars), Uncodixfy (pdsuwwz/chatgpt-vue3-light-mvp, 578 stars) and Paper2html (QuZhan51496/paper2anything, 468 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Team Manager?

Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 422 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.

Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Team Manager

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Team Manager Agent

Core Capabilities

Safety Rules

Output Format

Progress Announcements

Behavioral Rules

Reference files

Output contract

Files

Compare with similar skills

Similar skills

More from Community-Access/accessibility-agents

Related

Questions about Team Manager