Name: create-pr
Rating: 69.6 (1 reviews)
Author: docker

create-pr

Push the current branch and create a pull request against docker/docs. Use after changes are committed and reviewed. "create a PR", "submit the fix", "open a pull request for this".

Quality

85%

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

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 well-structured, actionable workflow with strong validation checkpoints and executable commands throughout. The main improvement space is trimming optional prose and considering whether the lengthy preview-link subsections belong inline.

Suggestions

Trim explanatory asides such as "Reviewers need to know what changed and why — nothing else" that restate obvious review norms.

Consider moving the Optional Netlify preview entry path and Preview links subsections into a separate reference file, since they are conditional detail that inflates the main body.

The actionability placeholders (<branch-name>, <pr-number>) are clear; add a one-line note on deriving <pr-number> from the gh pr create output to close the only minor gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command blocks with short guardrail prose, but sections like the optional Netlify/preview stanzas and explanatory asides could be trimmed slightly, fitting the efficient-with-minor-overexplanation anchor.	4 / 5
Actionability	It provides fully executable gh/git commands with clearly marked placeholders covering the common cases (verify, push, create, label, review, report), reaching copy-paste-ready guidance.	5 / 5
Workflow Clarity	Five numbered sections are explicitly sequenced with validation checkpoints and stop conditions (branch check, clean tree, duplicate-PR check, reviewer verification), plus feedback loops for error recovery.	5 / 5
Progressive Disclosure	No bundle files exist and none are needed; the single file is well-organized into numbered sections and clearly marked optional subsections, though at ~180 lines it is somewhat long to keep fully inline.	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 strong description that concisely states a specific niche, an explicit use condition, and natural trigger phrases. The only soft spot is specificity, which lists just two actions rather than a comprehensive set.

Dimension	Reasoning	Score
Specificity	"Push the current branch and create a pull request against docker/docs" names the domain plus two concrete actions (push, create PR), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states the what (push branch + create PR against docker/docs), an explicit when ("Use after changes are committed and reviewed"), and concrete trigger phrases, satisfying both what and when explicitly.	5 / 5
Trigger Term Quality	Quoted triggers "create a PR", "submit the fix", "open a pull request for this" are natural phrases users would say, giving good keyword coverage though a few synonyms (e.g. "make a PR") are missing.	4 / 5
Distinctiveness Conflict Risk	The narrow niche of creating PRs specifically against docker/docs with distinct trigger phrases gives a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: docker/docs
Path: .agents/skills/create-pr/SKILL.md
Commit: ff96ad1

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.