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.
69
61%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./github-contributor/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is structurally sound with a clear 'Use when' clause and covers the domain adequately. However, it reads more like a table of contents for a guide than a precise skill description—the listed capabilities are topic areas rather than concrete actions. Adding more specific trigger terms and concrete actions would improve its ability to be selected accurately from a large skill set.
Suggestions
Replace abstract topic areas with concrete actions, e.g., 'Identifies good-first-issue opportunities, guides forking and branching workflows, helps craft PR descriptions and commit messages, builds contributor reputation.'
Expand trigger terms in the 'Use when' clause to include natural user phrases like 'first pull request,' 'good first issue,' 'how to contribute to open source,' 'fork a repo,' or 'open source beginner.'
| 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 more like topic areas than concrete, specific actions (e.g., no mention of forking repos, writing commit messages, addressing review feedback). | 2 / 3 |
Completeness | Clearly answers both 'what' (strategic guide covering opportunity discovery, project selection, PR creation, reputation building) and 'when' (explicit 'Use when' clause with three trigger scenarios: contributing to open-source, building GitHub presence, or learning contribution best practices). | 3 / 3 |
Trigger Term Quality | Includes some natural keywords like 'open-source projects,' 'GitHub presence,' 'contribution best practices,' and 'PR creation,' but misses common variations users might say such as 'pull request,' 'first contribution,' 'good first issue,' 'open source beginner,' or 'how to contribute.' | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to GitHub contribution strategy, but could overlap with general Git skills, PR review skills, or open-source project management skills. The broad framing as a 'strategic guide' makes boundaries somewhat fuzzy. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
54%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has excellent workflow structure and progressive disclosure, with clear phases, validation checkpoints, and well-organized references to supporting files. However, it suffers significantly from verbosity and repetition—the same concepts (minimal PRs, separation of concerns, ~50 line descriptions) are restated 3-4 times across different sections. Much of the strategic advice about reputation building and contribution types is general knowledge that doesn't need to be spelled out for Claude.
Suggestions
Eliminate repetition: the PR description template, 'separation of concerns' guidance, and 'keep PRs minimal' advice each appear 2-3 times—consolidate into a single authoritative section.
Remove strategic/motivational content Claude already knows (contribution ladder, 'why contribute' rationale, professional communication basics) to cut the skill by ~40%.
Convert the 'Contribution Types' section into a compact table or brief list rather than four expanded subsections with 'opportunity signals' blocks.
Make the Evidence Loop section more actionable by providing a concrete, real example rather than placeholder commands like `[command that triggers bug]`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~350+ lines, with significant repetition. The PR description template appears twice, the 'separation of concerns' section restates what was already covered, the do/don't lists repeat earlier content, and much of the strategic advice (reputation building, contribution ladder) is general knowledge Claude already possesses. Many sections could be cut by 50%+. | 1 / 3 |
Actionability | The skill provides some concrete CLI commands and PR templates, but much of the content is strategic/philosophical rather than executable. The code blocks are mostly illustrative rather than copy-paste ready, and many sections use plain text checklists rather than concrete commands. The 'Evidence Loop' section has good structure but uses placeholder commands. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced with explicit phases (Investigation → Implementation → Validation → Submission → Review), includes validation checkpoints (reproduce bug, validate fix, ensure CI passes), and has a comprehensive checklist template with feedback loops for error recovery during the review phase. | 3 / 3 |
Progressive Disclosure | The skill has a clear overview structure with well-signaled references to external files (pr_checklist.md, project_evaluation.md, communication_templates.md, case study). Content is organized into logical sections with a quick reference at the end, and detailed materials are appropriately pointed to rather than inlined. | 3 / 3 |
Total | 9 / 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
- daymade/claude-code-skills
- Commit
80e94fd
- 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.