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

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable PR-creation workflow with executable commands and clear sequencing. Tightening the few explanatory passages and adding a post-update verification step would round it out.

Suggestions

Trim the explanatory sentences in Step 1c (e.g. 'Reviews get harder past ~10 files...') to keep only the load-bearing recommendation.

Add an explicit verification step after Step 8 (e.g. re-fetch the PR body or confirm the PATCH response) to close the workflow with a checkpoint.

Consolidate the template-path list in Step 4b into a compact table to reduce visual repetition.

Dimension	Reasoning	Score
Conciseness	Mostly lean with copy-paste commands and short directives, but Step 1c and a few explanatory 'why' clauses could be trimmed; no padding of Claude-known concepts.	4 / 5
Actionability	Provides fully executable git/gh commands with real flags and a real repo path, plus a heredoc body assembly; the few placeholders (<PR_NUMBER>, <title from Step 3>) are clearly signaled.	5 / 5
Workflow Clarity	Nine explicitly sequenced steps with decision checkpoints (size-gate ask, existing-PR detection) and an error workaround for gh pr edit, but lacks explicit post-update verification.	4 / 5
Progressive Disclosure	Single self-contained file with no bundle references, organized into clear numbered steps; the one delegation (staging-preview skill) is by name rather than a nested file reference.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with concrete actions and explicit, comprehensive trigger guidance. Minor room to tighten trigger-term coverage toward an extension-equivalent token.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the PR lifecycle — 'Opens a GitHub Pull Request', 'Infers the ticket from the branch name', 'generates staging preview URLs from changed files' — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both WHAT ('Opens a GitHub Pull Request with the standard PR template...') and WHEN ('TRIGGER when: user asks to open, create, submit, make, update, or edit...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Rich natural triggers including both 'PR' and 'pull request' synonyms plus six action verbs users would say, but lacks an extension-like token equivalent to the anchor's comprehensive synonym set.	4 / 5
Distinctiveness Conflict Risk	The MongoDB-docs-internal niche with DOCSP JIRA tickets and 'refresh staging links on an existing PR' is a clear, distinct trigger space with minimal overlap risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: mongodb/docs
Path: .claude/skills/open-pr/SKILL.md
Commit: d9cb237

Reviewed: 3 days 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.