CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

77

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

The body is a model procedural skill: lean, fully executable, with an ordered workflow, explicit user-decision checkpoints, and conditional handling for existing PRs, missing tickets, and oversized diffs. No dimension shows meaningful weakness.

DimensionReasoningScore

Conciseness

The body is purely procedural with no explanation of concepts Claude already knows; even the 'avoid gh pr edit' note is non-inferable repo-specific knowledge. The size-threshold sentence ('Reviews get harder past ~10 files / ~300 changed lines') directly informs the split-vs-proceed decision, so every token earns its place — the score-5 anchor.

5 / 5

Actionability

Every step ships copy-paste-ready commands: git context-gathering commands, 'python3 .claude/hooks/pr-size-check.py --report', 'gh pr create --draft --title ... --body ...', and the 'gh api ... --method PATCH --field body="$body"' update. Placeholders like <PR_NUMBER> are parameterization, not pseudocode, matching the fully-executable score-5 anchor.

5 / 5

Workflow Clarity

Steps 0–9 are strictly ordered with explicit checkpoints and error-recovery branches: existing-PR detection before creating, ask-user fallback when the branch lacks a DOCSP ticket, size-verdict branching, wait-for-reply before template use, and the draft-to-ready gate. This matches the score-5 anchor (clear sequence, validation steps, feedback loops).

5 / 5

Progressive Disclosure

There are no bundle files, and the ~140 well-sectioned lines all belong inline as one procedural workflow; nothing here is reference material that should be split out. The external 'staging-preview' skill and template files are one level deep and clearly signaled, matching the score-5 anchor for appropriately placed, easy-to-navigate content.

5 / 5

Total

20

/

20

Passed

Description

96%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 description: third-person, concrete, and comprehensive on both capabilities and triggers. The only weakness is that the 'update or edit a PR' trigger could bleed into a neighboring PR-review/update skill in the same environment.

Suggestions

Narrow the update/edit trigger to clarify it means updating the PR description/body (e.g., 'update or edit a PR description, or refresh staging links on an existing PR') to reduce overlap with PR-review skills.

DimensionReasoningScore

Specificity

The description lists three concrete, comprehensive actions in third person — 'Opens a GitHub Pull Request with the standard PR template', 'Infers the ticket from the branch name', 'generates staging preview URLs from changed files' — fully covering the skill's behavior. It matches the score-5 anchor; nothing is generic or missing for this domain.

5 / 5

Completeness

It explicitly answers both 'what' (opens PR with template, infers ticket, generates staging URLs) and 'when' (an explicit 'TRIGGER when:' clause with concrete trigger phrases), matching the score-5 anchor exactly.

5 / 5

Trigger Term Quality

'TRIGGER when: user asks to open, create, submit, make, update, or edit a PR or pull request, or wants to refresh staging links' gives comprehensive natural-term coverage including synonyms (PR / pull request; open / create / submit / make / update / edit). This is the score-5 anchor; no natural phrasing a user would say is missing.

5 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (repo-specific PR creation with JIRA/staging pipeline) with distinct triggers, but 'update or edit a PR' carries minor overlap risk with closely related PR-review or PR-maintenance skills, so the score-4 anchor ('mostly distinct; minor overlap risk') fits better than score 5.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
mongodb/docs
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.