Name: create-pr
Rating: 71.2 (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

87%

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

96%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.

An exemplary operational skill: fully executable commands, explicit stop-conditions and verification loops at every risky step, and no wasted tokens. The only structural note is that optional preview/label detail could be offloaded to a reference file as the skill grows.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — every sentence conveys docker/docs-specific procedure knowledge (fork remote handling, label API quirks, @netlify stanza mapping) with zero padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Guidance is fully executable: concrete git checks, a complete gh api timeline query with jq filter, a heredoc PR body template, and fallback API calls — copy-paste ready apart from inherent variables like branch name and issue number.	5 / 5
Workflow Clarity	A numbered five-step sequence with explicit validation checkpoints (branch must not be main, clean porcelain output, duplicate-PR timeline check, reviewer-assignment verification) and feedback loops with stop conditions and API fallbacks for error recovery.	5 / 5
Progressive Disclosure	The single file is well organized with clear numbered sections, but at ~170 lines with optional detail (Netlify entry path, preview links, reviewer-API fallbacks) inlined, content that could sit in a reference file is not split out — good structure, minor organization gap.	4 / 5
	Total	19 / 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.

A tight, well-formed description with an explicit use-when clause and natural trigger phrases. Its only weakness is modest action coverage and generic trigger phrasing that could overlap a general PR skill.

Suggestions

Add one or two more concrete actions (e.g., applying repo labels and requesting team review) to lift specificity beyond two actions.

Include a docker/docs-anchored trigger variant (e.g., "submit the docs fix") to reduce overlap with generic PR-creation skills.

Dimension	Reasoning	Score
Specificity	The description names the domain (PRs against docker/docs) and exactly two concrete actions — "Push the current branch and create a pull request" — matching the anchor for 1-2 concrete actions without comprehensive coverage of what the skill body actually does (labels, review requests, previews).	3 / 5
Completeness	It explicitly answers both what ("Push the current branch and create a pull request against docker/docs") and when ("Use after changes are committed and reviewed") with concrete quoted trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Quoted natural phrases "create a PR", "submit the fix", "open a pull request for this" are exactly what users would say, but common variants like "open a PR" or "make a PR" are missing, placing it just below comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The docker/docs scoping gives it a clear niche, but the trigger phrases are generic PR-creation terms that would also fire for any general PR-creation skill, leaving minor overlap risk rather than minimal.	4 / 5
	Total	16 / 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: 4d3cbcd

Reviewed: 1 day 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.