open-pr

Opens a GitHub Pull Request with the standard PR template: Description, Staging Links, and JIRA ticket. Infers the ticket from the branch name and generates staging preview URLs from changed files after the PR is created. TRIGGER when: user asks to open, create, submit, make, update, or edit a PR or pull request, or wants to refresh staging links on an existing PR.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

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 well-structured, highly actionable skill with clear sequential steps, concrete commands, and good decision-point handling. Its main strengths are workflow clarity and actionability — every step has explicit commands and conditions. Minor weaknesses include slightly verbose prose in places and the lack of bundle files to support referenced resources like the staging-preview skill or PR templates.

Suggestions

Consider trimming explanatory text in steps where the commands are self-documenting (e.g., Step 1's dash descriptions could be removed since the git commands are clear)

Include the staging-preview skill or at minimum document its expected interface/output format so the reference in Step 6 is fully self-contained

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and avoids explaining concepts Claude already knows, but some steps could be tightened. For example, Step 4b's full list of template options with paths is necessary context, but the overall document is somewhat lengthy for what could be a more streamlined workflow. The prose is generally purposeful though.	2 / 3
Actionability	The skill provides concrete, executable bash commands throughout (git commands, gh pr create, gh api calls), specific URL patterns, exact file paths for templates, and clear examples like the PR title format. The guidance is copy-paste ready and leaves little ambiguity about what to execute.	3 / 3
Workflow Clarity	The 10-step workflow is clearly sequenced with explicit decision points (existing PR vs new PR, template vs no template, HAS_DOC_FILES flag), conditional branching is well-defined, and there's a validation step checking for existing PRs before creating new ones. The flow handles edge cases like missing JIRA tickets (asks user) and the GraphQL deprecation workaround.	3 / 3
Progressive Disclosure	The skill references a `staging-preview` skill in Step 6 which is good delegation, and references template files at specific paths. However, all content is inline in a single file with no references to supplementary documentation. The template options listing could potentially be externalized, and there are no bundle files to support the references made.	2 / 3
	Total	10 / 12 Passed

Description

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 articulates specific capabilities (PR creation with template, JIRA inference, staging URL generation), provides comprehensive trigger terms covering multiple natural phrasings, and explicitly separates the 'what' from the 'when'. The description is concise, uses third person voice, and carves out a distinct niche that would be easy to differentiate from other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: opens a GitHub PR with a standard template (Description, Staging Links, JIRA ticket), infers ticket from branch name, generates staging preview URLs from changed files, and can refresh staging links on existing PRs.	3 / 3
Completeness	Clearly answers both 'what' (opens a GitHub PR with standard template, infers JIRA ticket, generates staging URLs) and 'when' (explicit TRIGGER clause listing multiple verb variations and the staging link refresh scenario).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'open', 'create', 'submit', 'make', 'update', 'edit', 'PR', 'pull request', 'refresh staging links'. These are terms users would naturally use when requesting this action.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: GitHub PR creation with a specific template including JIRA ticket inference and staging URL generation. The combination of PR + JIRA + staging links makes it very unlikely to conflict with generic git or code review skills.	3 / 3
	Total	12 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: mongodb/docs
Commit: be9d4af

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.