CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pr

Creates GitHub pull requests with auto-generated summaries. Use this skill whenever the user wants to create a PR, open a pull request, submit changes for review, or push their branch for review - even if they don't explicitly say "PR".

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary procedural skill: concrete commands at every step, a clearly sequenced workflow with explicit validation checkpoints and approval gates for risky operations, and no filler. The only refinement opportunity is moving the 8-section PR body template into a reference file to slim the main body.

DimensionReasoningScore

Conciseness

The body is efficient — exact commands, no re-teaching of concepts Claude knows — but the ~50-line inlined PR-body template carries inline coaching commentary (e.g., "Aim for what a reviewer would draw on a whiteboard") that adds minor bulk; anchor 5 demands every token earn its place.

4 / 5

Actionability

Fully executable guidance throughout: `gh auth status` prerequisite check, exact parallel git probes, a complete `gh pr create` heredoc invocation, and the `--base` edge case — copy-paste ready with the common cases covered.

5 / 5

Workflow Clarity

A 7-step numbered workflow with a prerequisite check, approval gates before any commit/push, and an explicit pre-submit checklist with a fix-before-submit feedback loop — matching the anchor for clear sequence with validation and error recovery.

5 / 5

Progressive Disclosure

Good single-file structure with clear section headers and no nested references, but the large PR-body template is inlined in a 157-line body rather than split into a one-level reference file; anchor 5 expects content appropriately split across files.

4 / 5

Total

18

/

20

Passed

Description

86%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: it clearly states what the skill does and when to use it, with natural trigger synonyms and an explicit catch for unstated "PR" phrasing. The only weakness is modest action coverage and a slight trigger-overlap risk around push/review wording.

DimensionReasoningScore

Specificity

"Creates GitHub pull requests with auto-generated summaries" names the domain and 1-2 concrete actions but is not a comprehensive action list; anchor 4 requires several specific actions listed, which this doesn't reach.

3 / 5

Completeness

Explicitly answers what ("Creates GitHub pull requests with auto-generated summaries") and when ("Use this skill whenever the user wants to create a PR, open a pull request...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers the natural phrasings users would say — "create a PR", "open a pull request", "submit changes for review", "push their branch for review" — plus explicit instruction to trigger even without the word "PR".

5 / 5

Distinctiveness Conflict Risk

The GitHub PR niche is clear and mostly distinct, but the triggers "push their branch for review" and "submit changes for review" carry minor overlap risk with plain git-push or review-request intents; anchor 5 demands minimal conflict risk.

4 / 5

Total

17

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
coralogix/cx-cli
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.