pr-issue-search
Find related GitHub issues for a pull request by extracting from branch name, commit messages, or searching GitHub. Use when the user asks to find related issues, link issues to a PR, or search for GitHub issues to reference.
100
100%
Does it follow best practices?
Impact
Pending
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 well-crafted skill description that clearly communicates what the skill does, how it does it, and when it should be triggered. It uses third-person voice, includes natural trigger terms, and occupies a distinct niche within GitHub-related workflows. The explicit 'Use when...' clause with multiple trigger scenarios makes it easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'extracting from branch name, commit messages, or searching GitHub.' These are clear, concrete methods the skill uses to find related issues. | 3 / 3 |
Completeness | Clearly answers both what ('Find related GitHub issues for a pull request by extracting from branch name, commit messages, or searching GitHub') and when ('Use when the user asks to find related issues, link issues to a PR, or search for GitHub issues to reference'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'related issues', 'pull request', 'link issues to a PR', 'search for GitHub issues', 'branch name', 'commit messages'. These cover common variations of how users would phrase such requests. | 3 / 3 |
Distinctiveness Conflict Risk | Targets a clear niche: finding related GitHub issues for PRs. The combination of PR context, issue linking, and GitHub-specific search makes it distinct and unlikely to conflict with general Git or GitHub skills. | 3 / 3 |
Total | 12 / 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 skill that efficiently guides Claude through a prioritized search strategy for finding related GitHub issues. It's concise, fully actionable with executable commands and concrete examples, and has a clear sequential workflow with appropriate fallback paths. The examples section reinforces the patterns without being redundant.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No unnecessary explanations of what GitHub issues are or how git works. The regex patterns, branch naming conventions, and tool invocations are all novel information Claude needs. The examples are compact and illustrative. | 3 / 3 |
Actionability | Provides executable bash commands, exact regex patterns, a complete MCP tool invocation with JSON arguments, and concrete branch-name-to-issue-number mappings. The output format section gives copy-paste ready templates. | 3 / 3 |
Workflow Clarity | Clear three-step sequential workflow with explicit stop condition ('Stop as soon as you have issue numbers'). Each step has a clear trigger for when to proceed to the next. The fallback chain (gh CLI -> MCP) is well-sequenced. No destructive operations requiring validation checkpoints. | 3 / 3 |
Progressive Disclosure | For a skill under 80 lines with no need for external references, the content is well-organized into logical sections (Strategy with numbered steps, Output Format, Examples). The structure is flat and easy to navigate without needing separate files. | 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
bee9b14
- 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.