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 — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating, editing, or pushing a PR to a third-party GitHub repo — "submit a PR", "open a PR", "fix this upstream", "rebase against main", "respond to the bot review", an `owner/repo` target, or 提 PR / 上游 PR / 贡献代码 / rebase 冲突 / 回应维护者.

75

Quality

92%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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, well-structured skill that excels in actionability and workflow clarity, with a clear phase-based progression and concrete executable examples throughout. Progressive disclosure is excellent with a well-organized reference table. The main weakness is verbosity — some philosophical framing, motivational explanations, and anti-pattern narratives could be trimmed since Claude doesn't need persuading about why these practices matter, just clear instructions on what to do.

Suggestions

Trim phase introductory paragraphs (e.g., Phase 1's 'The most common reason PRs get closed...' and Phase 3's 'Maintainers' trust is built by evidence...') — Claude doesn't need motivation, just the rules.

Condense the anti-patterns section into a compact table (pattern | consequence) rather than numbered prose explanations to save ~30% of that section's tokens.

DimensionReasoningScore

Conciseness

The skill is comprehensive but verbose in places — e.g., explaining why scope creep is bad, what a scope contract is, and general PR philosophy that Claude already understands. The anti-patterns section and some phase introductions could be significantly tightened. However, most content is genuinely instructive rather than padding.

2 / 3

Actionability

Excellent actionability throughout: executable bash commands for PR size checking, git branching, rebasing, gh API calls for replying to bot comments, concrete PR description templates, test coverage matrix examples, and specific Conventional Commits format. Nearly everything is copy-paste ready.

3 / 3

Workflow Clarity

The five-phase structure is clearly sequenced with explicit validation checkpoints (Phase 3 quality gates, Step 3.3 self-audit before description writing, the filter table in Step 5.3). Feedback loops are present — fix-then-revalidate for tests, fixup-then-autosquash for commits, filter-then-respond for counter-review. Destructive operations like force-push are explicitly guarded with --force-with-lease.

3 / 3

Progressive Disclosure

The skill provides a clear overview with well-signaled one-level-deep references to 10 specific reference files, each mapped to its purpose in a summary table. Content is appropriately split — the main file covers the workflow while detailed recipes (fixup workflow, isolation patterns, templates) are delegated to reference files. Navigation is easy via the Reference Files table.

3 / 3

Total

11

/

12

Passed

Description

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 thoroughly covers what the skill does with specific workflow steps, provides extensive natural trigger terms in both English and Chinese, and clearly scopes itself to third-party open-source contributions. It uses proper third-person voice and is comprehensive without being unnecessarily verbose.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. These are detailed, actionable steps in a clear workflow.

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 phrases and scenarios). The when clause is detailed and actionable.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms including 'submit a PR', 'open a PR', 'fix this upstream', 'rebase against main', 'respond to the bot review', 'owner/repo' pattern, and even Chinese-language equivalents (提 PR, 上游 PR, 贡献代码, rebase 冲突, 回应维护者). These are phrases users would naturally say.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive — specifically scoped to third-party/open-source PRs rather than general git or PR workflows. The emphasis on CONTRIBUTING compliance, AI-assisted disclosure, and maintainer interaction clearly distinguishes it from generic git or code review skills.

3 / 3

Total

12

/

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.