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

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.

A well-structured, highly actionable playbook with explicit validation checkpoints and clean progressive disclosure into reference files. Its only weakness is conciseness — some motivational framing and the metrics section could be trimmed without losing value.

Suggestions

Trim interpretive framing like 'because each phase has its own failure modes and the most common mistake is doing the right thing at the wrong phase' to keep the overview lean.

Move the 'Key metrics for a high-quality PR' section into a reference file, or compress it to the few numbers that drive decisions, since most are soft targets rather than actionable gates.

Consider condensing the intro paragraph after the title — the phase list is already enumerated in the Phase sections that follow.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it delegates detail to reference files and uses executable commands — but it carries motivational framing ('because each phase has its own failure modes') and a 'Key metrics' quick-reference section that could be tightened; it sits between the lean anchor 3 and the mostly-efficient anchor 2.

2 / 3

Actionability

Provides copy-paste-ready executable commands throughout — `gh pr list ...`, `git switch -c`, fixup/autosquash, `gh api ... -F in_reply_to=`, rebase sequences — plus concrete templates and coverage-matrix tables, matching the fully-executable anchor.

3 / 3

Workflow Clarity

Clearly sequenced phases 0–5 with numbered steps and explicit validation checkpoints (push-time checklist, self-audit 'what's my evidence?', mergeability check) and feedback loops for destructive ops (force-push requires --force-with-lease), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep references to real files in references/ (verified to exist) and a clear Reference Files navigation table; no nested-reference indirection, matching the clear-overview anchor.

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.

A strong description: concrete capabilities, explicit natural-language triggers in both English and Chinese, and clear what/when guidance. It is on the verbose side but the detail is all trigger-relevant rather than filler.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction' — matching the anchor that lists several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what ('End-to-end playbook for shipping high-quality pull requests...') and when ('Use whenever creating, editing, or pushing a PR...'), with explicit triggers; not capped at 2 because an explicit 'Use when...' clause is present.

3 / 3

Trigger Term Quality

Includes natural phrases users actually say in quotes ('submit a PR', 'open a PR', 'fix this upstream', 'rebase against main', 'respond to the bot review') plus bilingual variants and an owner/repo target signal — strong coverage, clearly above the 'some relevant keywords' anchor.

3 / 3

Distinctiveness Conflict Risk

Narrow niche — PRs to third-party repos you don't maintain — with distinct triggers and an owner/repo signal, making conflict with unrelated skills unlikely.

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.

Validation16 / 16 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.