CtrlK
BlogDocsLog inGet started
Tessl Logo

create-github-pr

Create GitHub pull requests using the gh CLI. Use when the user wants to create a new PR, submit code for review, or open a pull request. Trigger keywords - create PR, pull request, new PR, submit for review, code review.

72

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

82%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 well-sequenced, executable guide to opening PRs with concrete commands, a complete worked example, and validation checks. Its main weaknesses are minor redundancy in branch-naming guidance and a few inlined reference-style sections that could be split out.

Suggestions

Consolidate the branch-naming convention so it is stated once (either in Prerequisites or Verify Branch State) to remove the duplicated prose.

Add an explicit post-creation feedback loop, e.g., verify the PR opened (check the returned URL/number) and confirm CI triggered before considering the task done.

Consider moving the full options table and PR template block into a one-level-deep reference file, keeping SKILL.md as a lean overview with a pointer.

DimensionReasoningScore

Conciseness

The body is mostly lean with executable commands and project-specific conventions rather than explanations of concepts Claude already knows, but the branch-naming convention is restated in both Prerequisites and Verify Branch State, leaving minor tightening possible; fits the score-4 'efficient; minor instances that could be trimmed' anchor better than score-5's 'every token earns its place'.

4 / 5

Actionability

Provides copy-paste ready, fully executable `gh pr create` invocations covering the common cases (basic, with title/body, draft, labels, base branch) plus a complete worked example with a real body, matching the score-5 anchor.

5 / 5

Workflow Clarity

A clear sequence (Prerequisites → pre-commit → verify branch → push → create) with validation checkpoints (auth status, not-on-main check, pre-commit run, conventional-commit title) is present, but it lacks an explicit post-push/CI feedback loop for the batch-ish PR-opening operation, so it sits at score-4 'clear sequence with most checkpoints; minor validation gaps' rather than the score-5 explicit-feedback-loop anchor.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized sections and no bundle files to reference, so structure is appropriate; it lands at score-4 'good structure; most content appropriately placed; minor organization gaps' rather than score-5 because some inlined material (the full options table, complete PR template) reads as reference content that could live in a one-level-deep file.

4 / 5

Total

17

/

20

Passed

Description

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

The description is strong: it states a concrete capability tied to a specific tool and pairs it with an explicit 'Use when' clause and natural trigger keywords. It clearly communicates both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Names a concrete action ("Create GitHub pull requests using the gh CLI") tied to a specific tool, with several concrete triggering scenarios; just short of comprehensive multi-action coverage, fitting the 'several specific actions; minor gaps' anchor rather than the score-5 'multiple concrete actions' bar.

4 / 5

Completeness

Explicitly answers both what ("Create GitHub pull requests using the gh CLI") and when ("Use when the user wants to create a new PR, submit code for review, or open a pull request") with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

Lists natural phrases users actually say ("create PR", "pull request", "new PR", "submit for review", "code review"), giving comprehensive coverage of natural synonyms, matching the score-5 anchor.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (PR creation via the gh CLI) with distinct trigger keywords and minimal overlap risk, matching the score-5 'clear niche with distinct triggers' anchor rather than the score-4 'minor overlap risk' anchor.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
NVIDIA/OpenShell
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.