pr
Creates and updates GitHub pull requests for cloudflare-docs changes. Load when asked to open, create, submit, update, edit, or write a title or description for a PR. Covers title conventions, PR body structure, and the documentation checklist template.
90
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 skill description that clearly communicates specific capabilities (PR creation, title conventions, body structure, checklist template), provides explicit trigger guidance with natural user terms, and is scoped to a distinct niche (cloudflare-docs PRs). It follows third-person voice and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates and updates PRs, covers title conventions, PR body structure, and documentation checklist template. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates/updates GitHub PRs for cloudflare-docs, covers title conventions, body structure, checklist template) and 'when' (explicit 'Load when asked to open, create, submit, update, edit, or write a title or description for a PR'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'open', 'create', 'submit', 'update', 'edit', 'write a title or description', 'PR', 'pull requests'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to GitHub pull requests for cloudflare-docs, with clear triggers around PR creation and formatting. Unlikely to conflict with general coding or documentation 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 that provides clear, executable guidance for creating and editing GitHub PRs in the cloudflare-docs repository. Its main strengths are the concrete CLI commands, real-world title examples, and well-sequenced workflow with appropriate decision points. The primary weakness is its length — at ~200 lines in a single file, it could benefit from splitting detailed reference material (title examples, checklist rules) into supporting bundle files.
Suggestions
Consider extracting the detailed title examples and product bracket inference rules into a separate reference file (e.g., TITLE_CONVENTIONS.md) to reduce the main skill's token footprint.
The --body-file pattern and temp file cleanup instructions are repeated in both the editing and creating sections — consolidate into a single referenced technique to reduce duplication.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-written and avoids explaining basic concepts, but it's quite long (~200 lines) with some sections that could be tightened. The extensive title examples and detailed checklist guidance, while useful, add bulk. Some instructions are repeated (e.g., the --body-file pattern appears in both the editing and creating sections). | 2 / 3 |
Actionability | Highly actionable throughout — provides exact CLI commands, specific file paths, concrete title format examples from real PRs, precise rules for inferring product brackets, and step-by-step instructions for both creating and editing PRs. The fallback guidance when gh CLI is unavailable is also concrete with specific URLs. | 3 / 3 |
Workflow Clarity | The workflow is clearly sequenced into 4 numbered steps with explicit decision points (e.g., checking diff size before running full diff, reading the template fresh from disk, handling empty vs non-empty PR descriptions). The editing workflow has clear guard rails ('follow these rules strictly — then stop'). Validation is addressed through the draft-first requirement and deploy preview verification. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and headers, but everything is in a single file with no references to supporting documents. The PR template is read dynamically from disk which is good, but the extensive title examples, checklist guidance, and anti-patterns could potentially be split into referenced files. For a skill of this length (~200 lines), some progressive disclosure into bundle files would improve scannability. | 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
- cloudflare/cloudflare-docs
- Commit
9a170b9
- 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.