CtrlK
BlogDocsLog inGet started
Tessl Logo

github-contributor

End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain. Use whenever the user is creating, editing, or pushing a PR to a third-party GitHub repo — even if they just say "submit a PR", "open a PR", "fix this upstream", "rebase against main", "respond to the bot review", or names a target repo in the form `owner/repo`. Covers project discovery, CONTRIBUTING.md compliance, PR-size sanity check, minimal-diff implementation, isolated GUI E2E verification, PR description writing with AI-assisted disclosure, conflict resolution with fixup + autosquash, and post-submission bot/maintainer interaction. Also triggers on Chinese phrases like "提 PR"、"上游 PR"、"贡献代码"、"rebase 冲突"、"PR 描述写不好"、"回应维护者"、"AI 贡献声明".

75

Quality

92%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

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 an excellent skill description that hits all the marks. It provides highly specific capabilities (from project discovery to post-submission interaction), includes a comprehensive set of natural trigger terms in both English and Chinese, explicitly states when to use it with a 'Use whenever' clause, and carves out a clear niche (open-source contributions to third-party repos) that distinguishes it from other git/GitHub skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: project discovery, CONTRIBUTING.md compliance, PR-size sanity check, minimal-diff implementation, isolated GUI E2E verification, PR description writing with AI-assisted disclosure, conflict resolution with fixup + autosquash, and post-submission bot/maintainer interaction.

3 / 3

Completeness

Clearly answers both 'what' (end-to-end playbook covering discovery through post-submission interaction) and 'when' (explicit 'Use whenever...' clause with multiple trigger scenarios and phrases). The 'Use whenever' clause is explicit and detailed.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'submit a PR', 'open a PR', 'fix this upstream', 'rebase against main', 'respond to the bot review', 'owner/repo' format, plus Chinese equivalents like '提 PR' and '贡献代码'. These are highly natural phrases.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — scoped specifically to contributing PRs to third-party/open-source repos you don't maintain, which clearly differentiates it from general git skills, general PR skills for your own repos, or generic GitHub workflows.

3 / 3

Total

12

/

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 high-quality, comprehensive skill that excels at actionability and workflow clarity with its five-phase structure, executable commands, and explicit validation checkpoints. Progressive disclosure is well-handled with a clear reference file table. The main weakness is moderate verbosity — some motivational/explanatory prose could be trimmed to respect token budget, though the content is generally well-justified and specific rather than generic.

Suggestions

Trim motivational/explanatory sentences that Claude doesn't need (e.g., 'The most common reason PRs get closed is...', 'Maintainers' trust is built by evidence, not by claims', 'A great PR description does three jobs') — these add context window cost without changing behavior.

DimensionReasoningScore

Conciseness

The skill is comprehensive and mostly well-written, but it's quite long (~300+ lines) with some unnecessary explanatory prose that Claude doesn't need (e.g., explaining why scope creep is bad, why trust matters, what a scope contract is). Phrases like 'The most common reason PRs get closed is...' and 'Maintainers' trust is built by evidence, not by claims' are motivational rather than instructional. However, most content does earn its place with concrete commands and specific guidance.

2 / 3

Actionability

Excellent actionability throughout — real executable `gh` CLI commands, concrete git workflows with exact flags (`--force-with-lease`, `--fixup`, `--autosquash`), a complete PR description template with markdown skeleton, specific bot-reply API calls with field names, and a test coverage matrix example. Nearly everything is copy-paste ready.

3 / 3

Workflow Clarity

The five-phase structure (Discovery → Implementation → Quality Gates → Description → Post-Submission) is clearly sequenced with explicit validation checkpoints. Phase 3 includes self-audit steps, Step 3.3 is an explicit verification gate before proceeding, and the rebase workflow includes `--force-with-lease` as a safety check. The anti-patterns section adds error-recovery awareness. Feedback loops are present (fix → re-validate, filter findings → respond).

3 / 3

Progressive Disclosure

The skill has a clear overview structure with well-signaled one-level-deep references to 10 reference files, each mapped to a specific use case in a summary table. The main SKILL.md contains enough actionable content to be useful standalone while pointing to detailed materials for deeper workflows. References are consistently formatted with relative paths and descriptive labels.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
daymade/claude-code-skills
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.