pr-review-queue
Add a pull request to the MetaMask PR review queue project board. Use when the user asks to add a PR to the review queue, submit a PR for review tracking, or add to the MetaMask project board.
96
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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 solid skill description with clear 'what' and 'when' clauses, good trigger term coverage, and a highly distinctive niche. The main weakness is that it describes only a single action, which may be appropriate given the narrow scope of the skill but limits the specificity score slightly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a specific domain (MetaMask PR review queue project board) and one action (add a pull request), but it only describes a single concrete action rather than listing multiple specific capabilities. | 2 / 3 |
Completeness | Clearly answers both 'what' (add a pull request to the MetaMask PR review queue project board) and 'when' (explicit 'Use when...' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'pull request', 'PR', 'review queue', 'submit a PR', 'review tracking', 'MetaMask project board'. Good coverage of variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of MetaMask, PR review queue, and project board. Very unlikely to conflict with other skills given the narrow, well-defined niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, well-crafted skill that provides a complete, executable workflow for adding PRs to a MetaMask project board. It is concise, assumes Claude's competence with CLI tools and GraphQL, and sequences all steps clearly with explicit data dependencies between them. The inclusion of dynamic field fetching rather than hardcoded values makes it robust against project configuration changes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. Every section serves a purpose — no explanation of what GitHub Projects are, no unnecessary context about GraphQL or the `gh` CLI. The only potentially unnecessary detail is the date format examples, but those prevent ambiguity and earn their place. | 3 / 3 |
Actionability | Every step includes fully executable `gh` CLI commands and GraphQL mutations with clear placeholder variables. The commands are copy-paste ready with specific flags, JSON paths, and mutation structures. Instructions for extracting field IDs from JSON responses are concrete. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced with logical dependencies (fetch fields first, then add PR, then get project ID, then set fields). Each step's output feeds into subsequent steps, and the data flow is explicit. The instruction to dynamically fetch priority options rather than hardcode them serves as a validation/correctness checkpoint. | 3 / 3 |
Progressive Disclosure | For a single-purpose skill with no need for external references, the content is well-organized with clear sections (Input, Method with numbered steps, Output). The structure is appropriate for the complexity level — splitting this into multiple files would be unnecessary. | 3 / 3 |
Total | 12 / 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.