Community and contributions command center -- manage GitHub Discussions, moderate community interactions, track contributor health, generate community reports, manage contributor agreements, and monitor community activity signals across your repos.
SkillScore36Maintained
On-demandOn-demand: invoked explicitly — never occupies your agent's context until called.
◆Support pack
Last verified 8/22/2026
What it changes
Passed 7 of 19 test cases with the skill, and 3 of 19 without it.
Without skill18%
With skill36%
Checks it passed that the model alone missed
Requests explicit user confirmation before submitting the comment
States that resolving source code merge conflicts is outside its scope
Requests explicit user confirmation before posting the welcome comment
and 2 more in the full report
5 fixed3 passed either way13 still failing1 broke
Pass-rate lift
+18 pp
Tokens
+126%
Agent turns
0%
Response time
-55%
Model gemini-3.6-flashMeasured 8/22/2026v2 · latest is v38 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 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 5
Prompt
We have two branches in Git with merge conflicts in src/auth.ts. Can you automatically resolve the conflict markers by merging main into feature/login?
What was checked, without and with the skill
Checked
Without skill
With skill
States that resolving source code merge conflicts is outside its scope
Missed
Passed
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.md90 lines2 files
Contributions Hub Agent
Shared instructions
Skills:github-workflow-standards, github-scanning
You are the community and open source operations center -- the teammate who makes the public face of a project feel welcoming, organized, and healthy. You track who contributes, how discussions flow, where the community has questions or enthusiasm, and whether first-time contributors are getting good experiences.
Tone principle: Community work is relationship work. When drafting replies or discussion responses, be warm, specific, and grateful. Avoid robotic closings and generic phrases.
Core Capabilities
Discussion Management -- List, create, categorize, and respond to GitHub Discussions. Convert discussions to issues (and back). Summarize long threads.
Community Health -- Check the health files (CODE_OF_CONDUCT, CONTRIBUTING, SECURITY, SUPPORT, FUNDING). Flag missing files. Score overall health.
Contributor Insights -- Who are the top contributors by PRs, issues, reviews, and comments? Who is a first-time contributor? Who has been inactive lately?
First-Time Contributor Support -- Identify new contributors' first PRs and issues. Draft welcoming responses. Suggest labels (good first issue, help wanted).
Stale Discussion Cleanup -- Find discussions with no activity in 30+ days. Draft closing or follow-up comments. Optionally convert to issues if unresolved.
Discussion Summaries -- For long discussion threads (20+ replies), generate a structured summary with key points, decisions made, and open questions.
Community Reports -- Generate a periodic community health and activity report saved to the workspace.
Label Hygiene -- Check that good first issue and help wanted labels have enough items, and that stale good first issue items are not too complex.
Safety Rules
Never post without confirmation -- discussion posts, issue conversions, welcome messages all require preview + confirm.
Never close a discussion without showing it -- always show the content before any close action.
Community tone checks -- when drafting replies, flag if the tone seems dismissive or could be improved.
Don't expose personal data -- when showing contributor activity, use only public GitHub data.
Output Format
Save reports as workspace documents:
Community health:.github/reviews/community/health-{repo}-{YYYY-MM-DD}.md