CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

92%

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

85%

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

Highly actionable content with concrete commands, a clear sequenced workflow, and an explicit confirmation checkpoint before creating the PR. The main weakness is redundancy between the workflow steps and the repeated Command Pattern block.

Suggestions

Remove the standalone 'Command Pattern' section or collapse it into the workflow, since it duplicates the heredoc, preview, and `gh pr create` commands already shown in steps 5–7.

If a quick-reference command block is desired, replace the duplicated Workflow commands with a one-line pointer back to the steps rather than re-stating the full heredoc.

DimensionReasoningScore

Conciseness

The body is mostly lean and command-focused, but the 'Command Pattern' section repeats the heredoc/preview/create flow already detailed in workflow steps 5–7, so not every token earns its place.

2 / 3

Actionability

Provides concrete, executable bash — `git push -u`, the heredoc body construction, `cat` preview, and `gh pr create --base ... --head ... --body-file` — copy-paste ready with only sensible parameter placeholders.

3 / 3

Workflow Clarity

A clear 9-step sequence with an explicit preview-and-confirmation checkpoint before the outward-facing PR creation, plus a Constraints checklist; the confirmation step serves as the validation checkpoint for this non-batch operation.

3 / 3

Progressive Disclosure

A single, well-organized file with clearly labeled Workflow, Constraints, and Command Pattern sections, no bundle files, and no nested references — appropriate for a self-contained skill of this size.

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, specific description with concrete actions, natural trigger terms, and an explicit 'Use when' clause tied to a distinct repo-specific workflow. It clearly communicates both capability and invocation context without fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create or update GitHub pull requests', 'reads `.github/pull_request_template.md`, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Create or update GitHub pull requests...') and when ('Use when asked to create/open/update a PR...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — 'create/open/update a PR' and 'GitHub pull requests' — giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — repo-specific PR template compliance with the CherryHQ workflow — making it unlikely to trigger for the wrong skill.

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
CherryHQ/cherry-studio
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.