CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pull-request

Create a GitHub Pull Request from the current or specified branch. Use when: opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes to a repository.

79

Quality

100%

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

100%

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

A well-structured, concise skill body with an executable tool-call example, concrete git commands, and a clearly sequenced workflow with decision checkpoints. It assumes Claude's intelligence and avoids concept padding.

DimensionReasoningScore

Conciseness

The body is lean and actionable throughout, assuming Claude's competence without explaining what a PR or git is; every section earns its place, with only minor restatement in Best Practices.

3 / 3

Actionability

Provides a complete, executable tool call with labeled parameters plus concrete git commands (`git push --set-upstream origin <branch>`) and exact VS Code URI examples — copy-paste ready.

3 / 3

Workflow Clarity

A clearly numbered five-step procedure with explicit decision checkpoints for uncommitted/unpushed changes ("If yes", "only proceed if there are already commits"), meeting the validation-checkpoint expectation.

3 / 3

Progressive Disclosure

A single well-organized file (~98 lines) with clear section headings and no nested references; per the simple-skills note this warrants a 3 without external bundle files.

3 / 3

Total

12

/

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, third-person description that states concrete capabilities and pairs them with an explicit "Use when" trigger list, covering what and when clearly and distinctly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "opening a PR, submitting code for review, creating a draft PR, publishing a branch as a pull request, proposing changes" — matching the score-3 anchor of multiple specific actions.

3 / 3

Completeness

Explicitly answers what ("Create a GitHub Pull Request") and when via a clear "Use when:" clause with several triggers, matching the score-3 anchor.

3 / 3

Trigger Term Quality

Includes natural phrasings users would say ("open a PR", "submit for review", "pull request"), giving good coverage of real-world terms rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The GitHub PR niche is distinct with specific triggers unlikely to fire for unrelated skills; it would not conflict with general git or document skills.

3 / 3

Total

12

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
microsoft/vscode-pull-request-github
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.