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 content is a tight, well-sequenced instruction workflow that respects Claude's competence and avoids padding. Its only notable gap is the lack of an explicit, copy-ready MCP tool invocation and a final pre-creation validation checkpoint.

Suggestions

Add the specific GitHub MCP tool call (e.g. tool name and required fields) for step 6 so the creation action is fully concrete rather than implied.

Insert an explicit review/validation checkpoint between step 5 and step 6 (e.g. 'Confirm title and description are accurate before creating') to strengthen the workflow's feedback loop.

Optionally note how to handle a failed MCP call (retry or surface the error) so error recovery is explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or explanations of concepts Claude already knows; every line carries actionable instruction. Matches the 'every token earns its place' anchor.	5 / 5
Actionability	Provides concrete, specific guidance (named MCP server, explicit `gh` CLI prohibition, example title prefixes, named `/commit` skill) but stops short of specifying the exact MCP tool call to create the PR. Mostly executable with a minor gap; not a 5 because the final creation step lacks a concrete tool invocation.	4 / 5
Workflow Clarity	Six clearly numbered, well-sequenced steps with a feedback loop in step 1 ('fixing any errors'). Creating a draft PR is non-destructive, so the validation cap does not apply; not a 5 because there is no explicit validation checkpoint before final creation and the review step is implicit.	4 / 5
Progressive Disclosure	A simple skill under 50 lines with no need for external references, organized as a titled heading plus a numbered list; per the rubric's simple-skill guidance this qualifies for the top score on well-organized content.	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 clearly states both the capability and an explicit trigger, using appropriate third-person voice and natural terminology. Its main limitation is single-action specificity rather than a comprehensive action list.

Dimension	Reasoning	Score
Specificity	Names the domain (draft PR) and one concrete action ('Create a draft pull request for the current session'), but only covers a single action rather than several specific actions. A score of 4 would require multiple listed actions, which this lacks; 2 would under-credit the clearly stated single concrete action.	3 / 5
Completeness	Explicitly answers both 'what' ('Create a draft pull request for the current session') and 'when' ('Use when the user wants to open a draft PR with the session's changes') with a concrete trigger phrase, matching the anchor's example pattern.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('draft pull request', 'draft PR', 'open a draft PR') with good coverage of the common phrasing. Not a 5 because synonyms and variants are limited (no 'pull request' spelled out alongside 'PR' beyond the title, no acronym variants).	4 / 5
Distinctiveness Conflict Risk	'Draft pull request for the current session' is a clear niche with minimal conflict risk, mostly distinct from related git skills. Not a 5 because there is minor overlap with general commit/PR tooling skills.	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: 9bb0f27

Reviewed: about 23 hours 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.