CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

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

A highly actionable, well-sequenced skill body with explicit validation checkpoints and a complete worked example. Its weaknesses are duplicated policy statements that hurt token efficiency and policy prose that could be split into a reference file for cleaner progressive disclosure.

Suggestions

State the issue-closing exception once (in the Link to an Issue section) and reference it from Prerequisites instead of repeating it nearly verbatim.

Move the detailed issue-acceptance, vouching, and config-docs policy prose into a reference file (e.g., references/pr-policy.md) and keep a short gate + pointer in SKILL.md.

Tighten the dense policy paragraphs (e.g., Verify Contributor Access) into short bullet rules to reduce token cost without losing the repo-specific constraints.

DimensionReasoningScore

Conciseness

The body is mostly efficient and teaches only repo-specific policy Claude would not know, but the issue-closing exception is stated nearly verbatim twice ("Every PR must close an existing issue, except automated dependency updates and build or flaky-test fixes..." appears in both Prerequisites and Link to an Issue), and several dense policy paragraphs could be tightened. This matches "mostly efficient but includes some unnecessary explanation or could be tightened" rather than the minor-trim level of a 4.

3 / 5

Actionability

Guidance is fully executable with copy-paste-ready commands throughout: "gh pr create --title ... --body ...", "git push -u origin HEAD", "gh repo view OWNER/REPO --json nameWithOwner,viewerPermission", "gh run watch", plus a complete worked example PR with a heredoc body covering the common case. This matches the anchor for fully executable, copy-paste-ready commands with specific examples covering common cases.

5 / 5

Workflow Clarity

The multi-step process is clearly sequenced (verify access → check config docs/agent infra → verify branch state → push → create → monitor) with explicit validation checkpoints ("git branch --show-current" annotated "Should NOT be main", "gh auth status", permission JSON checks), error-recovery guidance ("Resolve failed lookups before proceeding", "Resolve any drift before creating the PR"), and a re-check loop ("Rerun PR Issue Acceptance after linked issue labels change"). PR creation is not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the single file is well-sectioned with one-level-deep, clearly signaled references to CONTRIBUTING.md, SECURITY.md, and the PR template. At ~280 lines it exceeds the simple-skill exemption, and the long inline policy prose (issue acceptance, vouching, config-docs checks) could arguably live in a reference file, matching "good structure; most content appropriately placed; minor organization gaps" rather than the clean overview-plus-references split of a 5.

4 / 5

Total

17

/

20

Passed

Description

78%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 with an explicit what/when structure and a dedicated trigger-keyword list in natural user language. Its main weaknesses are limited enumeration of the skill's concrete capabilities and a trigger term ("code review") that risks collision with other skills.

Suggestions

Enumerate 2-3 more concrete capabilities in the description, e.g., "set conventional-commit titles, link closing issues, create draft PRs, and target non-default base branches".

Remove or qualify the "code review" trigger keyword to avoid conflicting with a dedicated code-review skill; keep triggers focused on PR creation intent (create PR, open a pull request, submit for review).

Add the natural variation "open a PR" / "open a pull request" to the trigger list if not already implied by the when-clause.

DimensionReasoningScore

Specificity

The description names the domain and a single concrete action — "Create GitHub pull requests using the gh CLI" — but does not list the several specific capabilities the skill actually covers (draft PRs, title/body format, issue linking, targeting branches). It matches the anchor for naming the domain with 1-2 concrete actions without comprehensive coverage, and is not generic enough for a 2.

3 / 5

Completeness

It 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 appended — matching the anchor that clearly and explicitly answers both. The when-clause is fully explicit, so it is not a 4.

5 / 5

Trigger Term Quality

"Trigger keywords - create PR, pull request, new PR, submit for review, code review" plus "open a pull request" gives good natural-phrase coverage users would actually say. A few natural variations are missing (e.g., "open a PR", "merge request"), keeping it just below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The niche (GitHub PR creation via gh) is clear with distinct triggers, but the "code review" trigger keyword overlaps with what a code-review skill would claim, creating minor conflict risk. It is well above the broad-overlap anchors but not the minimal-conflict ideal.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 missing, 2 suspicious

Warning

Total

13

/

16

Passed

Repository

NVIDIA/OpenShell

Path

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