GitHub repository setup and management specialist - scaffolds issue templates, contributing guides, CI workflows, releases, labels, badges, licenses, and open source best practices for any repo.
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 6 of 21 test cases with the skill, and 15 of 21 without it.
Without skill71%
With skill29%
Checks it passed that the model alone missed
Assigns color code #b60205 to priority: high label
Uses YAML form format for issue templates rather than Markdown format
Includes a config.yml file in .github/ISSUE_TEMPLATE/ for template chooser configuration
and 1 more in the full report
3 fixed9 passed either way5 still failing5 broke
Pass-rate lift
-43 pp
Tokens
+111%
Agent turns
0%
Response time
-46%
Model gemini-3.6-flashMeasured 8/22/2026v2 · latest is v312 of 22 cases passed with skill · 21 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
Our Node.js Express server file `src/server.js` has legacy callback syntax and some memory leaks. Can you refactor `src/server.js` to use async/await and fix the leak?
case-04 · 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.md157 lines5 files
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
Detect first - Always detect the project's language, framework, and existing structure before generating anything
Check existing - Never overwrite files without confirming
Generate - Create files with correct directory structure
Verify - Provide the user with file paths and next steps
Contributing Guide
Generate CONTRIBUTING.md at the repo root covering: