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

72

Quality

89%

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.

A well-structured, highly actionable PR-creation workflow with executable commands, a strict template, and explicit validation checkpoints. Minor conciseness trims and the long inline template keep it just shy of top marks on two dimensions.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no basic concept explanations), but contains a few trimmable clauses such as parentheticals like "(usually main or master)" and qualifying phrases in the step-4 bullets, fitting 'minor instances of over-explanation that could be trimmed' rather than the lean level-5 anchor.

4 / 5

Actionability

Concrete executable commands (git status, git log, gh pr create) and a complete copy-paste heredoc template cover the common cases and are ready to run.

5 / 5

Workflow Clarity

A 7-step numbered workflow includes explicit validation/approval checkpoints (ask before commit/push in steps 2-3) and a pre-submit checklist feedback loop (step 6), satisfying validation for the outward-facing PR operation.

5 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references, but the skill is over 50 lines with a large inline template block, so the simple-skill level-5 exception does not apply; structure is good with minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

90%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, third-person description that clearly states what the skill does and gives rich, natural trigger phrasing including indirect ones. Its only weakness is specificity: it describes a single action rather than a fuller set of capabilities.

DimensionReasoningScore

Specificity

"Creates GitHub pull requests with auto-generated summaries" names the domain and one concrete action, but coverage is not comprehensive (no mention of updating, commenting, or reviewing PRs), matching the level-3 anchor rather than level 4's 'several specific actions'.

3 / 5

Completeness

It explicitly answers both what ("Creates GitHub pull requests with auto-generated summaries") and when ("Use this skill whenever the user wants to...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"create a PR, open a pull request, submit changes for review, push their branch for review" plus "even if they don't explicitly say 'PR'" gives comprehensive natural-term coverage including synonyms and indirect phrasings.

5 / 5

Distinctiveness Conflict Risk

The PR-creation niche with specific triggers (PR, pull request, submit for review, push branch) is clearly distinct from other skills with minimal overlap risk.

5 / 5

Total

18

/

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

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.