pr-create
Create a GitHub pull request from the current branch. Validates preconditions, generates title and description, and opens the PR as draft. Use when the user asks to create a PR, open a pull request, or submit changes for review.
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
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 an excellent skill description that clearly communicates what the skill does (create GitHub PRs with validation, title/description generation, and draft mode) and when to use it (explicit trigger phrases). It uses third person voice, includes natural trigger terms with good variation, and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: validates preconditions, generates title and description, opens the PR as draft. These are clear, actionable steps. | 3 / 3 |
Completeness | Clearly answers both what ('Create a GitHub pull request... validates preconditions, generates title and description, opens the PR as draft') and when ('Use when the user asks to create a PR, open a pull request, or submit changes for review'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'create a PR', 'open a pull request', 'submit changes for review', 'GitHub pull request'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to GitHub PR creation from the current branch, with distinct triggers like 'pull request', 'PR', and 'submit changes for review'. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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, well-structured skill with clear workflow sequencing, executable commands, and appropriate delegation to other skills. The main weakness is moderate redundancy around the 'Definition of Ready For Review' concept, which is referenced four times with the same link. Overall it provides excellent actionable guidance for creating a GitHub PR.
Suggestions
Consolidate the repeated 'Definition of Ready For Review' references — state it once prominently (e.g., in the Rules section) and refer back to it briefly elsewhere instead of repeating the full link and explanation four times.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the 'Definition of Ready For Review' concept is repeated four times with the same link, and the rules section partially restates workflow constraints already covered. The Slack message templates and fallback approach are justified, but the overall content could be tightened. | 2 / 3 |
Actionability | Provides fully executable commands for precondition checks, gh CLI invocation with exact flags, and a complete MCP tool fallback with JSON arguments. The Slack message templates are copy-paste ready, and the AskQuestion tool usage is specific with exact option text and defaults. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation checkpoints (precondition checks with specific abort conditions), user consent gates via AskQuestion, parallelization noted for independent steps, and a well-defined output format. Error recovery is handled via abort conditions and user prompts. | 3 / 3 |
Progressive Disclosure | The skill is well-structured as an overview that references other skills (pr-description, pr-codeowners, pr-review-queue) and external docs (ready-for-review.md) at one level deep. Content is appropriately scoped to this skill's responsibility with clear signposting to related resources. | 3 / 3 |
Total | 11 / 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
- MetaMask/metamask-mobile
- Commit
dedb5dd
- 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.