github-contributor
Strategic guide for becoming an effective GitHub contributor. Covers opportunity discovery, project selection, high-quality PR creation, and reputation building. Use when looking to contribute to open-source projects, building GitHub presence, or learning contribution best practices.
88
83%
Does it follow best practices?
Impact
97%
1.22xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description that clearly communicates both purpose and usage triggers. The main weakness is that the capabilities listed are somewhat abstract categories rather than concrete actions, and there's potential overlap with related Git/code review skills. The explicit 'Use when...' clause with multiple trigger scenarios is a strength.
Suggestions
Replace abstract categories with more concrete actions (e.g., 'find good-first-issues, evaluate project health, write PR descriptions, respond to maintainer feedback')
Add distinguishing terms to reduce conflict risk with related skills (e.g., 'first-time contributor', 'maintainer communication', 'issue triage')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub contribution) and lists some actions like 'opportunity discovery, project selection, high-quality PR creation, and reputation building', but these are somewhat abstract categories rather than concrete specific actions like 'fork repositories, write commit messages, submit pull requests'. | 2 / 3 |
Completeness | Clearly answers both what ('Strategic guide for becoming an effective GitHub contributor. Covers opportunity discovery, project selection, high-quality PR creation, and reputation building') and when ('Use when looking to contribute to open-source projects, building GitHub presence, or learning contribution best practices'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'contribute to open-source', 'GitHub presence', 'contribution best practices', 'PR creation'. These align well with how users would naturally phrase requests about contributing to projects. | 3 / 3 |
Distinctiveness Conflict Risk | While focused on GitHub contribution specifically, there could be overlap with general Git skills, code review skills, or open-source documentation skills. The 'PR creation' aspect might conflict with commit message or code review skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, actionable skill with excellent workflow clarity and progressive disclosure. The main weakness is some unnecessary motivational and explanatory content that Claude doesn't need (the 'why contribute' framing). The concrete elements—CLI commands, checklists, templates, and commit formats—are strong and immediately usable.
Suggestions
Remove or significantly trim 'The Strategy' section explaining why contributing is valuable—Claude doesn't need motivation, just instructions.
Condense the 'Building Reputation' section which explains concepts Claude can infer; keep only the actionable 'Contribution Ladder' and consistency guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some explanatory content Claude already knows (e.g., why contributing is valuable, basic concepts like 'build contributor reputation'). The strategy section and motivation explanations could be trimmed. | 2 / 3 |
Actionability | Provides concrete, executable guidance throughout: specific GitHub CLI commands, exact commit message formats, structured PR templates, and copy-paste ready checklists. The workflow template and quick reference sections are immediately usable. | 3 / 3 |
Workflow Clarity | Clear sequential workflows with explicit checklists (Pre-PR Checklist, Contribution Workflow). The contribution ladder provides a clear progression path. Steps are well-sequenced with logical checkpoints. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from strategy to execution. References section points to one-level-deep external files (pr_checklist.md, project_evaluation.md, communication_templates.md) for detailed content. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- fernandezbaptiste/claude-code-skills
- Commit
4f0eae8
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.