create-draft-pr

Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 lean, well-sequenced instruction list that assumes Claude's competence and stays within token budget. Its only real gap is actionability detail: the actual PR-creation mechanism (which MCP tool, draft parameter) is not specified.

Suggestions

Name the specific GitHub MCP tool and its draft parameter in step 6 (e.g. call create_pull_request with draft=true) to make the final step fully executable.

Clarify what "the compile and hygiene tasks" are, or point to where they are defined, so step 1 is unambiguous.

Add an explicit pre-flight check before step 6 (e.g. confirm compile and hygiene tasks passed) to close the validation gap.

Dimension	Reasoning	Score
Conciseness	The body is a single directive line plus six terse numbered steps with zero padding and no explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Steps are concrete and executable for an agent with the referenced tooling (/commit skill, example area prefixes), but "Run the compile and hygiene tasks" is left implicit and step 6 does not name the specific GitHub MCP tool or its draft flag, so it is below the fully copy-paste-ready anchor.	4 / 5
Workflow Clarity	The six steps are clearly sequenced with a fix loop ("fixing any errors") and conditional handling of uncommitted changes, but there is no explicit final verification checkpoint before creating the PR, so it fits the 4 anchor rather than the explicit-validation 5 anchor.	4 / 5
Progressive Disclosure	The skill is under 50 lines, single-purpose, requires no external references (no references/scripts/assets files exist), and is well organized, meeting the rubric's simple-skill exception for a top score.	5 / 5
	Total	18 / 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.

The description is strong: it is concise, uses third-person voice, and explicitly covers both what the skill does and when to use it with a natural trigger phrase. Its main weakness is specificity — it names only the headline action while omitting the supporting steps the skill performs.

Suggestions

Add one or two supporting actions to the description (e.g. commits uncommitted changes via /commit and writes the PR title/description) so the what is more comprehensive.

Add a couple more natural trigger variations such as "open a PR for review" or "prepare changes for review" to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	"Create a draft pull request for the current session" names the domain and one concrete action, but does not list the several specific actions (commit, review, title, description) the skill actually performs, so it sits at the 1-2 concrete actions anchor rather than the several-actions anchors.	3 / 5
Completeness	Explicitly answers both what ("Create a draft pull request for the current session") and when with a concrete trigger phrase ("Use when the user wants to open a draft PR with the session's changes"), matching the top anchor and clearly above the 4 anchor where the when-clause could be more explicit.	5 / 5
Trigger Term Quality	Includes natural terms users would say — "draft pull request", "open a draft PR" — with the pull request/PR synonym pair covered, but a few natural variations (e.g. "create a PR", "request review") are missing, matching the good-but-not-comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The draft-PR creation niche is clear and unlikely to trigger for unrelated skills, but there is minor overlap risk with a closely related general PR-creation or commit skill, which fits the 4 anchor rather than the minimal-conflict 5 anchor.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: posit-dev/positron
Path: src/vs/sessions/skills/create-draft-pr/SKILL.md
Commit: b0258bc

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.