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".
72
88%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted description that concisely communicates what the skill does (push and create a PR against docker/docs), when to use it (after changes are committed and reviewed), and includes natural trigger phrases. The specificity of the target repository and the inclusion of multiple user-facing trigger terms make it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Push the current branch' and 'create a pull request against docker/docs'. The target repository is explicitly named, adding specificity. | 3 / 3 |
Completeness | Clearly answers both 'what' (push branch and create PR against docker/docs) and 'when' ('Use after changes are committed and reviewed') with explicit trigger examples. | 3 / 3 |
Trigger Term Quality | Includes natural trigger phrases users would actually say: 'create a PR', 'submit the fix', 'open a pull request for this'. These are realistic user utterances with good variation coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a specific repository (docker/docs) and a specific workflow (push + PR creation), making it clearly distinguishable from general git skills or other PR-related skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable skill with excellent workflow clarity and concrete, executable commands throughout. The sequencing includes thoughtful validation steps like duplicate PR detection and reviewer verification with fallbacks. Minor weaknesses include some verbosity in the optional Learnings section and the PR body template explanation, which could be tightened without losing clarity.
Suggestions
Trim the optional Learnings section — remove the explanation about the 'weekly PR learnings scanner' and reduce to a brief note with the markdown template only.
Consider tightening the duplicate PR check explanation to just the command and a one-line instruction (e.g., 'If this returns results, stop and report the existing PR').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete commands, but includes some unnecessary explanation (e.g., the optional Learnings section is quite verbose, and the explanation about the weekly PR learnings scanner is context Claude doesn't need). The duplicate PR check section is thorough but slightly wordy. | 2 / 3 |
Actionability | Every step includes fully executable, copy-paste-ready bash commands. The gh CLI commands are specific with proper flags, the FORK_OWNER derivation is a real working sed command, and even edge cases like label application via the Issues API are covered with concrete commands. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced (verify → push → create PR → label/review → report) with explicit validation checkpoints: checking for unstaged changes, verifying remote URL, checking for duplicate PRs before creating one, and verifying reviewer assignment with a fallback API call. The feedback loop for reviewer assignment is well-handled. | 3 / 3 |
Progressive Disclosure | The content is well-structured with numbered sections and clear headings, but it's all inline in a single file. The optional Learnings section and the detailed duplicate-PR-check logic could potentially be split out. However, for a skill of this size (~100 lines), the inline approach is reasonable, just slightly long. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- docker/docs
- Commit
2ea4a02
- Reviewed
Table of Contents
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.