CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pr

Create a GitHub pull request with the project's PR template fully populated. Analyzes the branch diff, fills in "What changed", "Issue", "How to test", "A11y impact", "Definition of Done", and other sections. Use this skill whenever the user wants to create a PR, open a pull request, submit their branch for review, or says things like "make a PR", "open a PR", "submit this for review", or "I'm ready to create a pull request" — even if they don't use the exact phrase "pull request".

95

1.35x
Quality

Does it follow best practices?

Impact

84%

1.35x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 body is a tight, actionable workflow: concrete git/gh commands, a per-section template-filling guide, and a confirmation gate before the irreversible gh pr create. Organization is clear and self-contained with no unnecessary concept explanation.

DimensionReasoningScore

Conciseness

The body is lean and command-driven with no concept lectures Claude already knows; mild coaching lines ('Think about what a reviewer unfamiliar with this part of the codebase would need') earn their place, keeping it at level 3 rather than the padded level 2.

3 / 3

Actionability

Provides copy-paste-ready executable commands (git log/diff, gh pr list, gh pr create with full HEREDOC), exact checkbox formats, and the concrete template path .github/pull_request_template.md, matching the fully-executable level 3.

3 / 3

Workflow Clarity

Clear Gather → Fill → Create sequence with an explicit validation/confirmation gate ('Ask "Ready to create?" before running gh pr create') and a pre-creation remote-push check, satisfying the explicit-checkpoint level 3 rather than the gap-prone level 2.

3 / 3

Progressive Disclosure

A single, well-organized file with clear section headers and no external bundle references needed; per the simple-skills note this scores 3 with well-organized sections alone.

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.

A high-quality description: third-person, concrete actions, explicit trigger guidance with many natural phrasings, and a distinct niche. It clearly answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create a GitHub pull request', 'Analyzes the branch diff', 'fills in "What changed", "Issue", "How to test", "A11y impact", "Definition of Done"' — matching the score-3 anchor rather than the domain-only level 2.

3 / 3

Completeness

Explicitly answers both what (template population actions) and when via the 'Use this skill whenever the user wants to...' clause, matching the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would actually say — 'create a PR', 'open a pull request', 'submit their branch for review', 'make a PR', 'submit this for review', 'I'm ready to create a pull request' — well beyond the partial-coverage level 2.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (PR creation with template population) with distinct PR-specific triggers, making overlap with unrelated skills unlikely; not the generic level 1 or partly-overlapping level 2.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
HHS/OPRE-OPS
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.