CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

github-contributor

Ships pull requests to open-source projects you don't maintain — CONTRIBUTING compliance, PR-size/scope checks, minimal-diff implementation, AI-disclosure PR descriptions, and rebase or bot-review replies. Use for 提 PR / 上游 PR / 贡献代码, "open a PR", "fix this upstream", "rebase against main", "respond to the bot review". Not for reviewing PRs as maintainer (use github-review-pr) or general GitHub CRUD (use github-ops).

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary phase-based playbook: concrete commands, explicit validation gates, and a well-structured one-level reference bundle that matches the files actually present. The only weakness is minor verbosity in the Step 3.3 policy prose and some duplication between the Phase 2 and Phase 5 fixup/rebase sections.

Suggestions

Rewrite Step 3.3's behavioral-impact-review paragraphs as 2–3 terse bullets and move the resolution/fallback rules into a reference file — the hedging prose ('This does not invoke an independent review or grant maintainer authority...') is the densest non-actionable text in the skill.

De-duplicate the fixup/autosquash workflow: Phase 2.3 and Step 5.2 both describe it — keep one canonical inline treatment and make the other a pointer to references/phase2_implementation.md.

Clarify or delete the 'never stop another session's service to make a test pass' clause in Step 3.1 — as written it is cryptic and reads as boilerplate rather than instruction.

DimensionReasoningScore

Conciseness

The body is mostly lean, command-driven, and assumes Claude's competence (no padding explaining what PRs or CI are), but a few passages don't earn their place: Step 3.3's dense policy hedging ("Resolve that reference through the installed github-review-pr Skill when contributing outside this marketplace... This does not invoke an independent review or grant maintainer authority"), Phase 3.1's odd "never stop another session's service to make a test pass" clause, and the fixup/autosquash workflow appearing in both Phase 2.3 and Step 5.2. Not 5: those trimmable spots exist; not 3: everything else is concrete and tightly written.

4 / 5

Actionability

Fully executable throughout — copy-paste-ready commands with real flags (gh pr list --jq filter, gh api ... -F in_reply_to for bot replies, git -c sequence.editor=: rebase -i --autosquash, --force-with-lease), a complete PR-body skeleton, a disclosure template, and a worked test-coverage matrix. Specific examples cover the common cases (baseline sizing, conflict rebase, screenshot placeholders).

5 / 5

Workflow Clarity

Phases 0–5 are clearly sequenced with explicit validation checkpoints and feedback loops: the Step 3.3 "What's my evidence?" self-audit, the Step 3.4 push-time checklist (visibility, mergeability, no --no-verify), conflict-resolution recovery, and --force-with-lease semantics for the destructive force-push step. Anchor 5's checklist-and-recovery pattern is met; the destructive-operation validation cap does not apply because validation is present.

5 / 5

Progressive Disclosure

A clear overview playbook pointing to 12 one-level-deep reference files, each inline-signaled ("See references/X for...") and indexed in a Reference Files table with per-file purpose; all in-bundle referenced paths resolve against the actual references/ listing. The one out-of-bundle path (../github-review-pr/references/behavioral-impact-review.md) is explicitly scoped with fallback behavior for when it is unavailable, so navigation is never broken.

5 / 5

Total

19

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete lifecycle capabilities, bilingual natural trigger phrases, and explicit negative boundaries naming the sibling skills to route to instead. The only deduction is the second-person clause 'you don't maintain' under the rubric's third-person voice rule.

Suggestions

Rewrite the opening clause in third person (e.g., 'Ships pull requests to open-source projects the contributor does not maintain') to fully satisfy the third-person voice rule and recover the specificity point.

DimensionReasoningScore

Specificity

"Ships pull requests to open-source projects you don't maintain — CONTRIBUTING compliance, PR-size/scope checks, minimal-diff implementation, AI-disclosure PR descriptions, and rebase or bot-review replies" lists five concrete lifecycle actions with comprehensive coverage, which anchors at 5 — but the rubric's voice rule penalizes second person ("projects you don't maintain"), reducing it by one point to 4. Not 3: far more than 1–2 concrete actions; the −1 is the only reason it is not a 5.

4 / 5

Completeness

Explicitly answers both questions: what — ships PRs to unmaintained open-source projects with the five named capability areas; when — "Use for 提 PR / 上游 PR / 贡献代码, 'open a PR', 'fix this upstream', 'rebase against main', 'respond to the bot review'" with concrete trigger phrases, plus explicit negative scope. Matches the anchor-5 example's structure exactly.

5 / 5

Trigger Term Quality

Natural trigger phrasings users would actually say are comprehensively covered with synonym variants across two languages: "open a PR", "fix this upstream", "rebase against main", "respond to the bot review", plus 提 PR / 上游 PR / 贡献代码. Not 4: unlike 'a few natural terms missing', the synonym coverage (bilingual variants, multiple phrasings) is comprehensive.

5 / 5

Distinctiveness Conflict Risk

A clear contributor-side niche with explicit disambiguation: "Not for reviewing PRs as maintainer (use github-review-pr) or general GitHub CRUD (use github-ops)." Minimal conflict risk; not 4: it does not merely reduce overlap, it names the sibling skills and routes away from them.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

daymade/claude-code-skills

Path

github-contributor/SKILL.md

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.