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

Low

Low-risk findings worth noting

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-validated workflow document: every step has a concrete command, explicit checkpoints, and defined failure paths. The main cost is token efficiency — repeated issue-acceptance policy and a redundant options table inflate the body without adding guidance Claude does not already have.

Suggestions

State the issue-acceptance rule (and its dependency-update/flaky-test exceptions) once in a single section and reference it elsewhere instead of restating it in Prerequisites, 'Verify Contributor Access and Issue Acceptance', and 'Link to an Issue'.

Drop or trim the 'Useful Options' table, since Claude already knows standard gh pr create flags; keep only project-specific notes such as the conventional-commit title requirement.

Move the repo-specific policy detail (vouch requirements, security disclosure, config-doc cross-checks) into a short reference file and keep SKILL.md to the core PR-creation workflow.

DimensionReasoningScore

Conciseness

The body is mostly lean commands and directives with no explanation of concepts Claude already knows, but the issue-acceptance policy is restated three times in overlapping forms (Prerequisites, 'Verify Contributor Access and Issue Acceptance', 'Link to an Issue') and the 'Useful Options' table re-lists standard gh flags, so it could be meaningfully tightened.

3 / 5

Actionability

Fully executable guidance throughout: concrete gh/git commands, a copy-paste-ready example PR with heredoc body covering the common case, exact title formats, and a populated description template.

5 / 5

Workflow Clarity

Clear sequenced workflow (verify access/issues, check docs and infra, verify branch state, push, create, post-create) with explicit validation gates ('Should NOT be main', gh repo view/gh issue view checks, 'Resolve failed lookups before proceeding') and recovery paths ('preserve local work and report which issue needs acceptance'; re-run acceptance after label changes).

5 / 5

Progressive Disclosure

A single, well-sectioned file that correctly delegates project policy to existing repo artifacts (CONTRIBUTING.md, .github/PULL_REQUEST_TEMPLATE.md, the sync-agent-infra skill) instead of duplicating them, but at roughly 270 lines the dense project-policy prose is a candidate for a separate reference file.

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: third-person voice, explicit what-and-when, and a concrete tool-specific capability. The main weaknesses are the single-action capability list and the 'code review' trigger term, which risks mis-triggering against review-focused skills.

DimensionReasoningScore

Specificity

Names the domain, tool, and one concrete action ('Create GitHub pull requests using the gh CLI'); the remaining phrases ('create a new PR, submit code for review, or open a pull request') are variations of that single action rather than additional capabilities, matching the domain-plus-1-2-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

Explicitly answers 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.

5 / 5

Trigger Term Quality

Natural phrases like 'create PR', 'pull request', 'new PR', and 'submit for review' are listed, but common variations such as 'open a PR' or a bare 'PR' are missing, which fits the good-but-not-comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The PR-creation-via-gh niche is distinct, but the 'code review' trigger keyword overlaps with review/critique skills and could fire this skill for users asking to review a PR rather than create one.

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

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.