pr

Open a draft pull request on GitHub and drive CI review rounds until it is ready. MUST use when you want to create/open a PR.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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 PR workflow with strong validation gates and feedback loops, built almost entirely from non-obvious repo-specific operational detail. The main weakness is that several large sections are inlined rather than split into reference files.

Suggestions

Move the Screenshots hosting procedure and EE Companion PR workflow into separate reference files (e.g. references/screenshots.md, references/ee-pr.md) and link to them one level deep, leaving SKILL.md as a tighter overview.

Tighten the 'Flip, or ask first' and 'When rounds stop converging' prose into shorter checklists to trim tokens without losing the judgment guidance.

Consider extracting the review-round marker-comment rules into a short reference so the exact marker formats live alongside the verdict taxonomy rather than inline in the main flow.

Dimension	Reasoning	Score
Conciseness	The body is dense and almost entirely non-obvious operational knowledge (review-round.sh, marker-comment rules, EE symlink behavior, base64-stdin gotcha) rather than concepts Claude already knows; not a 5 because prose in 'Flip, or ask first' and 'When rounds stop converging' could be tightened.	4 / 5
Actionability	Provides copy-paste-ready commands throughout — `gh pr create --draft`, the full base64-to-GitHub screenshot script, `gh pr ready`, conflict-resolution merges — plus a concrete PR body/title template covering the common cases.	5 / 5
Workflow Clarity	Execution Steps 1-10 and Review rounds 1-3 give a clearly sequenced process with explicit validation gates ('run both reviews, do not skip', 'Never run gh pr ready before [a clean round]'), feedback loops (fix -> commit -> new round), and error-recovery guidance for conflicts and non-converging rounds.	5 / 5
Progressive Disclosure	Well-organized with clear section headers and one-level-deep deferrals to repo docs (e.g. 'Follow the full EE PR workflow in docs/enterprise.md'); not a 5 because substantial sections (Screenshots, EE Companion PR, Review rounds) are inlined in a single SKILL.md with no skill-bundle files to offload them.	4 / 5
	Total	18 / 20 Passed

Description

82%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 concise, well-targeted description that explicitly states both capability and trigger condition using natural synonyms. It is slightly light on enumerated concrete actions, but otherwise strong.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions — 'Open a draft pull request on GitHub' and 'drive CI review rounds until it is ready' — matching the anchor that lists 1-2 concrete actions without comprehensive coverage; not a 4 because it does not enumerate several specific actions.	3 / 5
Completeness	Explicitly answers both 'what' (open a draft PR and drive CI review rounds to ready) and 'when' with a concrete trigger phrase 'MUST use when you want to create/open a PR'; not below 5 because the trigger guidance is explicit rather than weakly implied.	5 / 5
Trigger Term Quality	Includes natural synonyms users actually say — 'pull request', 'PR', and 'create/open a PR' — giving good keyword coverage; not a 5 because common variations like 'merge request' or 'code review' are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (GitHub draft PR creation + CI review driving) with distinct triggers ('PR', 'pull request', 'create/open a PR') and minimal overlap with other skills; the [ee]/companion-PR specialization further narrows it.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: windmill-labs/windmill
Path: .agents/skills/pr/SKILL.md
Commit: 7915540

Reviewed: 3 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.