CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

gh-create-pr

Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads `.github/pull_request_template.md`, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of skipping sections.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

The body is a dense, highly actionable, well-sequenced workflow with explicit validation checkpoints and feedback loops, and no filler. Its only weaknesses are minor duplication between the Workflow, Constraints, and Command Pattern sections, and the inlining of a sizable rulebook that could be split into a reference file.

DimensionReasoningScore

Conciseness

The body contains no padding or explanations of concepts Claude already knows — every line carries repo-specific rules — but the hotfix title grammar is repeated in Workflow steps 7/10 and again in Constraints, and the Command Pattern section restates steps 8-11 nearly verbatim, which is trimmable duplication.

4 / 5

Actionability

Guidance is fully executable: a copy-paste gh/gh-extension preflight block, `pnpm change:scope --base <verified-base-ref>`, a concrete temp-file heredoc pattern, exact `gh pr create` invocations, exact title grammars, and the exact bilingual release-note fence structure cover the common cases.

5 / 5

Workflow Clarity

The 12-step workflow is clearly sequenced with explicit validation checkpoints and feedback loops: "Stop if authentication, installation, or the final verification fails", inspecting the temp body before creation, and verifying the classifier added the `hotfix` label after creation with a defined fix path.

5 / 5

Progressive Disclosure

Sections are well organized (Stack tooling / Workflow / Constraints / Command Pattern) and references to repo files like `.agents/skills/gh-stack/SKILL.md` and `.agents/notes/README.md` are clearly signaled, but the ~125-line body inlines the entire hotfix/backport/release-note rulebook that could plausibly live in a separate reference file.

4 / 5

Total

18

/

20

Passed

Description

83%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 that clearly states concrete capabilities and an explicit use-when trigger, tightly scoped to this repository's PR template compliance. Minor gaps in capability coverage and natural trigger variations keep a couple of dimensions at 4 rather than 5.

Suggestions

Broaden trigger coverage with common phrasings such as "draft PR", "submit a PR", or "PR for review" so the skill fires on the natural variations users say.

Mention one or two more of the skill's concrete capabilities in the description (e.g., base-branch selection rules or hotfix/release-note handling) to make the capability list more comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("reads `.github/pull_request_template.md`", "fills every template section", "preserves markdown structure exactly", "marks missing data as N/A or None"), but omits other core capabilities of the skill such as base-branch determination and the hotfix/release-note workflow, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

It explicitly answers both what ("Create or update GitHub pull requests... fills every template section, preserves markdown structure exactly") and when ("Use when asked to create/open/update a PR") with a concrete trigger phrase, matching the top anchor rather than the merely-adequate 'when' of anchor 4.

5 / 5

Trigger Term Quality

Natural trigger phrases like "create/open/update a PR", "pull requests", and "PR" match what users would actually say, though common variations such as "draft PR", "submit a PR", or "PR for review" are missing.

4 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to repository-required template compliance with a specific template path, giving it a clear niche, but its trigger phrases could still overlap with a generic GitHub/PR-creation skill, matching anchor 4 ("mostly distinct; minor overlap risk with closely related skills").

4 / 5

Total

17

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

CherryHQ/cherry-studio

Path

.agents/skills/gh-create-pr/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.