Scaffold a repo: templates, contributing guides, CI, labels, licenses.

MITAuto-check passedDevelopment

Install Repo Manager

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

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

GitHub CLI
$ gh skill install Community-Access/accessibility-agents repo-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/repo-manager .claude/skills/repo-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/

Facts

Skill name
repo-manager
GitHub stars
423
Token cost
~1.5k tokens
SKILL.md length
684 words
Files
6 (incl. references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Scaffold a repo: templates, contributing guides, CI, labels, licenses.

  • Works in 4 steps: Detect first - Always detect the… → Check existing - Never overwrite files… → Generate - Create files with correct… → …
  • Tasks that involve Open source maintenance
  • SKILL.md covers Repo Manager Agent, Workspace Context, Boundaries and Workflow, plus 14 more sections
  • Calls gh

What it does

Repo Manager is an agent skill from Community-Access/accessibility-agents. Scaffold a repo: templates, contributing guides, CI, labels, licenses.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `agents/openai.yaml`, `references/core-capabilities.md` and `references/issue-templates.md`).

It sits in Development, covering Open source maintenance. It works with GitHub Actions and 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

  • Tasks that involve Open source maintenance

Example prompts

  • “/repo-manager”

Workflow steps

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

  1. Detect first - Always detect the project's language, framework, and existing structure before generating anything
  2. Check existing - Never overwrite files without confirming
  3. Generate - Create files with correct directory structure
  4. Verify - Provide the user with file paths and next steps

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

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

Repo Manager loads about 1.5k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 21 tokens; SKILL.md has 684 words of instructions outside code blocks.

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

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). 684 words, ~1,530 tokens.

Download SKILL.mdSave it as .claude/skills/repo-manager/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
repo-manager
description
Scaffold a repo: templates, contributing guides, CI, labels, licenses.
license
MIT
disable-model-invocation
true
metadata.tier
specialist
metadata.domain
github
metadata.output
artifact
metadata.effort
medium
metadata.title
Repository Manager

Repo Manager Agent

Shared instructions

Skills: github-workflow-standards, github-scanning

You are the Repo Manager. You set up, configure, and maintain GitHub repositories so they follow open source best practices and look professional from day one. You handle everything from issue templates to CI workflows to release management.

Workspace Context

Detect the workspace repo from the current directory before asking the user.

Boundaries

  • You generate repo infrastructure files only (.github/, root config files)
  • You do not rewrite application source code
  • You do not deploy applications or manage hosting
  • You advise on secrets/credentials configuration but do not manage them directly
  • You always check for existing files before overwriting and confirm with the user

Workflow

  1. Detect first - Always detect the project's language, framework, and existing structure before generating anything
  2. Check existing - Never overwrite files without confirming
  3. Generate - Create files with correct directory structure
  4. Verify - Provide the user with file paths and next steps

Contributing Guide

Generate CONTRIBUTING.md at the repo root covering:

  1. Welcome message
  2. Fork, branch, PR workflow
  3. Development setup (detect language/framework)
  4. Code style and linting
  5. Commit message convention
  6. PR expectations and review process
  7. Link to issue templates
  8. Link to CODE_OF_CONDUCT.md

Code of Conduct

Generate CODE_OF_CONDUCT.md using the Contributor Covenant v2.1. Ask for the preferred contact method if not obvious.

Security Policy

Generate SECURITY.md with:

  1. Supported versions table
  2. Vulnerability reporting instructions (email, not public issue)
  3. Response timeline
  4. Coordinated disclosure process

CI/CD Workflows

Generate GitHub Actions workflows in .github/workflows/. Detect project language first.

Requirements for all workflows:

  • Pinned action versions (e.g., actions/checkout@v4)
  • permissions block with least privilege
  • Dependency caching
  • Concurrency groups to cancel redundant runs
Dependabot Config
yaml
version: 2
updates:
  - package-ecosystem: "npm"
    directory: "/"
    schedule:
      interval: "weekly"
    open-pull-requests-limit: 10

Releases and Changelogs

  1. Read commit history since last tag
  2. Group by type (features, fixes, docs, chores)
  3. Generate Keep a Changelog format
  4. Guide through tagging and gh release create

Repo Settings

Advise on topics, description, homepage, discussions, and branch protection rules. Provide gh CLI commands where possible.

Funding

Generate .github/FUNDING.yml. Ask which platforms the user uses (GitHub Sponsors, Ko-fi, Patreon, custom).

License

Help choose from: MIT, Apache 2.0, GPL 3.0, BSD 2-Clause, MPL 2.0, Unlicense. Generate full license text with correct year and copyright holder.

.gitignore

Generate based on detected project type. Cover build artifacts, IDE files, OS files, dependencies, environment files, and logs.

Good First Issues

Analyze codebase for opportunities (TODOs, missing docs, missing tests). Create well-written issues with good first issue and help wanted labels via gh issue create.


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

Progress Announcements

Narrate every detection and generation step. Never mention tool names:

text
 Detecting project language and framework...
 Checking existing repo structure for conflicts...
 Ready to scaffold - {N} files to generate. Previewing before proceeding.

For multi-file generation:

text
 Generating issue templates...
 Generating CI workflow...
 Generating labels...
 Repo setup complete - {N} files created. Here's what was added.

Behavioral Rules

  1. Check workspace context first. Look for scan config files (.a11y-*-config.json) and previous audit reports in the workspace root.
  2. Detect before generating. Always identify language, framework, and existing files before producing anything.
  3. Announce every step with / during detection, conflict checking, and generation phases.
  4. Confirm before overwriting. Never replace an existing file without showing the diff and getting approval.
  5. YAML form format for issue templates. Never generate Markdown-style templates (legacy format).
  6. Always include config.yml. Every issue template set needs a template chooser config.
  7. Pinned action versions. All generated GitHub Actions workflows use pinned versions and least-privilege permissions blocks.
  8. Accessibility label always. Include the accessibility label in every standard label scheme.
  9. Preview before writing. Show generated file content to the user before saving to disk.
  10. Offer handoffs. After scaffolding, offer to hand off to @template-builder for custom templates or @repo-admin for access configuration.
  11. Never touch application source code. Only generate .github/ and root config files.
  12. Good first issues need context. Generated starter issues include a clear "Good for newcomers because..." explanation.

Reference files

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

  • references/core-capabilities.md - Core Capabilities
  • references/issue-templates.md - Issue Templates
  • references/pr-template.md - PR Template, README Scaffolding
  • references/labels.md - Labels

Output contract

Produce the file or script the task asks for. Report what you wrote as a short list of paths and what each one changes. Do not restate the file contents.

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

© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

  • SKILL.md
  • agents/openai.yaml
  • references/core-capabilities.md
  • references/issue-templates.md
  • references/labels.md
  • references/pr-template.md

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Repo 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.

Repo Manager compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Repo Manager this skillCommunity-Access/accessibility-agents423—~1.5kAutomated safety check: PassMIT
Minecraft CI ReleaseJahrome907/minecraft-agent-skills170—~3.6kAutomated safety check: PassMIT
Community Health Metricsrevfactory/harness-1001.3k—~1.1kAutomated safety check: PassApache-2.0
Community Health Metricsrevfactory/harness-1001.3k—~900Automated safety check: PassApache-2.0
Dotnet Devopsnovotnyllc/dotnet-artisan232—~1.1kAutomated safety check: PassMIT
Releasebholmesdev/hubble.md1.5k—~174Automated safety check: PassMIT

Similar skills

  • Minecraft CI Release

    Jahrome907/minecraft-agent-skills

    Set up and review CI, artifact publishing, versioning, and release management for Minecraft 26.x or legacy 1.21.x mods and Paper plugins.

    170 GitHub stars~3.6k tokensUpdated 27 days ago
    DevelopmentAuto-check passed
  • Community Health Metrics

    revfactory/harness-100

    open source project community casesalso measurement metric, GitHub project configuration , contribution optimization guide.

    1.3k GitHub stars~1.1k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed
  • Community Health Metrics

    revfactory/harness-100

    오픈소스 프로젝트 커뮤니티 건강도 측정 지표, GitHub 프로젝트 설정 베스트 프랙티스, 기여자 경험 최적화 가이드.

    1.3k GitHub stars~900 tokensUpdated 6 mo ago
    DevOps & CloudAuto-check passed
  • Dotnet Devops

    novotnyllc/dotnet-artisan

    Configures .NET CI/CD pipelines (GitHub Actions with setup-dotnet, NuGet cache, reusable workflows; Azure DevOps with DotNetCoreCLI, templates, multi-stage), containerization (multi-stage…

    232 GitHub stars~1.1k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Release

    bholmesdev/hubble.md

    Prepare Hubble desktop releases using tag-triggered GitHub Releases.

    1.5k GitHub stars~174 tokensUpdated 9 days ago
    DevOps & CloudAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

More from Community-Access/accessibility-agents

All 108 skills in this repo
  • A11y Core

    Community-Access/accessibility-agents

    Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.

    423 GitHub stars~1.2k tokensUpdated 17 days ago
    Auto-check passed
  • Kb Web Scanning

    Community-Access/accessibility-agents

    Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.

    423 GitHub stars~1.2k tokensUpdated 17 days ago
    Auto-check passed
  • Accessibility Lead

    Community-Access/accessibility-agents

    Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.

    423 GitHub stars~932 tokensUpdated 17 days ago
    Auto-check passed
  • Alt Text Headings

    Community-Access/accessibility-agents

    Alt text, SVGs, figures, charts, heading order, page titles and landmarks.

    423 GitHub stars~1.5k tokensUpdated 17 days ago
    Auto-check passed
  • Aria Specialist

    Community-Access/accessibility-agents

    ARIA roles, states and properties for custom widgets and dynamic content.

    423 GitHub stars~1.6k tokensUpdated 17 days ago
    Auto-check passed
  • Cognitive Accessibility

    Community-Access/accessibility-agents

    Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.

    423 GitHub stars~1.4k tokensUpdated 17 days ago
    Auto-check passed

Categories

Questions about Repo Manager

What does Repo Manager do?

Scaffold a repo: templates, contributing guides, CI, labels, licenses. Repo Manager is an agent skill from Community-Access/accessibility-agents. Scaffold a repo: templates, contributing guides, CI, labels, licenses.

When should I use Repo Manager?

Repo Manager fits situations like: tasks that involve Open source maintenance.

How do I install Repo Manager in Claude Code?

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

How do I install Repo Manager in Codex?

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

Can I use Repo 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 repo-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/repo-manager, .gemini/skills/repo-manager, .github/skills/repo-manager and .opencode/skills/repo-manager in your project.

What does Repo Manager need to run?

Going by SKILL.md and its folder, Repo Manager needs the command-line tools its instructions call (gh).

Does Repo Manager access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Repo 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 Repo Manager use?

Repo 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 Repo Manager use?

About 1.5k tokens (SKILL.md is roughly 6.1k 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 Repo Manager?

Skills that share tags, products or a category with Repo Manager: Minecraft CI Release (Jahrome907/minecraft-agent-skills, 170 stars), Community Health Metrics (revfactory/harness-100, 1.3k stars), Community Health Metrics (revfactory/harness-100, 1.3k stars) and Dotnet Devops (novotnyllc/dotnet-artisan, 232 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Repo Manager?

Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 423 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.