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".

87

1.35x
Quality

87%

Does it follow best practices?

Impact

84%

1.35x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, actionable skill body with concrete commands, a clear workflow, and an explicit user-confirmation checkpoint before the outward-facing PR creation. Minor coaching prose and placeholder bodies keep it just short of top marks.

Suggestions

Trim soft coaching lines ('Think about what a reviewer unfamiliar with this part of the codebase would need.', 'Read the full diff carefully.') to tighten token efficiency.

Add a brief error-recovery note for when `gh pr create` fails (e.g., auth errors, branch-not-pushed) to complete the feedback loop.

Fill the HEREDOC body example with one short representative snippet instead of bare '...' placeholders to make the template fully copy-paste ready.

DimensionReasoningScore

Conciseness

Largely lean with executable commands and tight per-section guidance, but includes a few trimmable coaching lines such as 'Think about what a reviewer unfamiliar with this part of the codebase would need.' and 'Read the full diff carefully.'

4 / 5

Actionability

Provides concrete, executable bash commands (git log/diff, gh pr list, gh pr create with HEREDOC) and specific per-section instructions, but the HEREDOC body uses '...' placeholders leaving minor gaps for the author to fill.

4 / 5

Workflow Clarity

Clear three-phase sequence (Gathering Context → Filling In the Template → Creating the PR) with an explicit confirmation checkpoint ('Ready to create?' before gh pr create), satisfying the destructive-operation validation requirement; lacks an error-recovery loop for a failed gh pr create.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and cohesive content that appropriately lives in one file (no bundle files present); exceeds the simple-skill line count but nothing here clearly belongs in a separate file.

4 / 5

Total

16

/

20

Passed

Description

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

An excellent description: third-person voice, concrete actions, explicit 'Use when' clause with multiple natural trigger phrases, and a clearly distinct niche. It scores at the top of every dimension.

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"' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (create PR, analyze diff, populate template sections) and 'when' ('Use this skill whenever the user wants to create a PR...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and phrasings users 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'.

5 / 5

Distinctiveness Conflict Risk

Clear niche (GitHub PR creation with template population) with distinct triggers; minimal conflict risk with other skills since the trigger terms are specific to PR creation.

5 / 5

Total

20

/

20

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.