CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-pr

Create pull requests using GitHub CLI with proper templates and formatting

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/git/skills/create-pr/SKILL.md
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.

The skill body is highly actionable with concrete, copy-paste-ready gh commands and a sensible sequenced workflow including a pre-flight validation checkpoint. Its main weakness is mild verbosity — the install prerequisites and a redundant template-creation section could be trimmed for better token efficiency.

Suggestions

Trim the OS-by-OS gh install prerequisites (brew/winget/linux) to a one-line pointer; Claude already knows how to install the CLI.

Remove or fold the "Using Templates for PR Creation" section into the main creation step to eliminate redundancy with the earlier --body-file example.

Add a short post-creation verification step (e.g. `gh pr view` / `gh pr status`) to close the workflow loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient and actionable, but the Prerequisites install block (brew/winget/linux) and the redundant "Using Templates for PR Creation" section pad content Claude largely already knows; it sits at the mostly-efficient-but-could-be-tightened anchor rather than fully lean.

3 / 5

Actionability

It provides copy-paste-ready, fully executable commands throughout — `gh pr create --draft --title ... --body-file ...`, `gh auth login`, plus a complete list of auxiliary commands with real flags — covering the common PR cases comprehensively.

5 / 5

Workflow Clarity

The flow is clearly sequenced (prerequisites → pre-flight checks → create PR) and includes an explicit pre-flight validation checkpoint (run `git status`, commit first), with only a minor gap in that it lacks an explicit post-creation verification step.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with one-level-deep references to the PR template and external docs, and no nested references; minor gaps are the inlined install instructions and the long auxiliary-commands block that could live separately.

4 / 5

Total

16

/

20

Passed

Description

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

The description is clear and narrowly scoped to PR creation via GitHub CLI, but it lacks an explicit "Use when..." trigger clause and omits common synonyms like "PR". Adding a when-to-use phrase and a couple more concrete actions would lift it from adequate to strong.

Suggestions

Append a "Use when..." clause naming concrete triggers, e.g. "Use when the user asks to create, open, or submit a pull request / PR."

Add the natural synonym "PR" (and "PRs") so the description matches how users actually phrase the request.

List one or two more concrete actions (e.g. set reviewers, mark draft/ready) to broaden coverage beyond just create + template + formatting.

DimensionReasoningScore

Specificity

The description names the domain and a couple of concrete actions ("Create pull requests", "proper templates", "formatting") but the action set is minimal and not comprehensive, matching the 1-2 concrete actions anchor rather than the 4-anchor's broader coverage.

3 / 5

Completeness

It gives a clear "what" (create PRs with templates/formatting) but contains no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant natural terms ("pull requests", "GitHub CLI", "templates") but misses common variations/synonyms a user might say such as "PR", "PRs", or "open a PR", fitting the some-relevant-keywords-but-missing-variations anchor.

3 / 5

Distinctiveness Conflict Risk

"Create pull requests using GitHub CLI" carves a clear niche with minimal conflict risk against unrelated skills, though it is not so distinctive as to fully eliminate overlap with adjacent git/commit skills, placing it just below the 5 anchor.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 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

relative_links

Relative link issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

NeoLabHQ/context-engineering-kit

Path

plugins/git/skills/create-pr/SKILL.md

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.