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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

100%

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 tight, executable five-step workflow with concrete git/gh commands, explicit validation checkpoints, and well-organized sections requiring no external references. It avoids concept explanations and every token earns its place.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence; sections like '## 1. Verify the branch' deliver only the needed commands with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	All guidance is fully executable copy-paste-ready commands (e.g. 'gh pr create --repo docker/docs --head "${FORK_OWNER}:<branch-name>"') with concrete flags and a heredoc body template.	3 / 3
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints ('git diff --quiet', duplicate-PR check, reviewer-assignment verification) and feedback loops for error recovery.	3 / 3
Progressive Disclosure	A single self-contained SKILL.md with well-organized numbered sections and no external references; per the simple-skill scoring note, this warrants the top score without bundle files.	3 / 3
	Total	12 / 12 Passed

Description

90%

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 concise and third-person, with strong natural trigger terms and explicit 'what' and 'when' guidance scoped to docker/docs PRs. Its only weakness is a slightly narrow action list, keeping specificity at the middle anchor.

Dimension	Reasoning	Score
Specificity	Quotes 'Push the current branch and create a pull request against docker/docs' name two concrete actions, but the action set is narrow rather than a comprehensive list of multiple specific actions.	2 / 3
Completeness	Explicitly answers what ('Push the current branch and create a pull request') and when ('Use after changes are committed and reviewed' plus trigger phrases), satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	Quotes "'create a PR', 'submit the fix', 'open a pull request for this'" are natural phrases a user would actually say, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to 'a pull request against docker/docs', giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: 67d0999

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