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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

100%

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

The content is a tight, fully-actionable PR-creation workflow with explicit sequencing and validation checkpoints, and no unnecessary explanation. It is self-contained and well-organized with no need for external references. No meaningful weaknesses to flag.

Dimension	Reasoning	Score
Conciseness	The body is lean and instructional — concrete git/gh/python commands with no padding or explanation of concepts Claude already knows; every line advances the workflow.	3 / 3
Actionability	Provides fully executable commands throughout (`git log`, `gh pr create`, `gh api ... --method PATCH`, `python3 .claude/hooks/pr-size-check.py --report`) with clearly defined placeholders, copy-paste ready.	3 / 3
Workflow Clarity	A clearly sequenced Step 0–9 workflow with explicit checkpoints and feedback loops: PR-size check with a split/proceed decision, existing-PR detection, ticket-presence guard, and a ready-for-review confirmation.	3 / 3
Progressive Disclosure	No bundle files exist, so the single self-contained body is scored on its own organization; sections are well-structured and linear with no nested references, appropriate for a cohesive single-purpose workflow.	3 / 3
	Total	12 / 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.

The description is third-person, specific, and provides explicit trigger guidance covering a wide range of natural user phrasings. It clearly distinguishes this skill from others via its niche workflow. No meaningful weaknesses to flag.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Opens a GitHub Pull Request with the standard PR template', 'Infers the ticket from the branch name', and 'generates staging preview URLs from changed files' — rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' (opens a PR with template/ticket/staging links) and 'when' via a clearly marked 'TRIGGER when:' clause with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'open, create, submit, make, update, or edit a PR or pull request, or wants to refresh staging links' — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (GitHub PR with a specific template, JIRA ticket inference, and staging preview generation) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: e765459

Reviewed: about 23 hours 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.