create-pr

Create pull requests using GitHub CLI with proper templates and formatting

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/git/skills/create-pr/SKILL.md

Quality

Discovery

32%

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 identifies a clear domain (GitHub CLI pull requests) but is too brief and lacks explicit trigger guidance. It would benefit from listing more concrete actions and including a 'Use when...' clause with natural user trigger terms like 'PR', 'open a pull request', or 'gh pr'.

Suggestions

Add a 'Use when...' clause with trigger terms like 'PR', 'pull request', 'gh pr create', 'open a PR', 'submit code for review'.

List more specific actions such as 'set reviewers, add labels, link issues, apply PR templates, draft PRs'.

Include common abbreviations and variations users might say, such as 'PR', 'gh CLI', '.github/PULL_REQUEST_TEMPLATE'.

Dimension	Reasoning	Score
Specificity	Names the domain (pull requests, GitHub CLI) and mentions some aspects (templates, formatting), but doesn't list multiple concrete actions beyond 'create pull requests'. Could specify actions like setting reviewers, adding labels, linking issues, etc.	2 / 3
Completeness	Describes what the skill does (create pull requests with templates/formatting) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately detailed, warranting a 1.	1 / 3
Trigger Term Quality	Includes good terms like 'pull requests', 'GitHub CLI', and 'templates', but misses common variations users might say such as 'PR', 'gh pr create', 'open a PR', 'merge request', or 'code review'.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'GitHub CLI' and 'pull requests' provides some specificity, but could overlap with general GitHub skills, git workflow skills, or code review skills. The scope is somewhat narrow but not sharply delineated.	2 / 3
	Total	7 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill covers PR creation with GitHub CLI comprehensively but is too verbose, explaining things Claude already knows (CLI installation, basic git commands, what gh commands do). The core workflow is present but weakened by missing template content and lack of post-creation validation. The skill would benefit significantly from trimming known concepts and inlining the actual PR template structure.

Suggestions

Remove the Prerequisites/installation section entirely—Claude knows how to install CLI tools and can figure this out if needed.

Remove or drastically trim the 'Additional GitHub CLI PR Commands' section, as these are standard gh commands Claude already knows.

Include the actual PR template content inline or ensure the referenced @.github/pull_request_template.md is in the bundle, so Claude can actually fill it out.

Add a post-creation validation step (e.g., 'Verify with `gh pr view` that the PR was created correctly and all sections are populated').

Dimension	Reasoning	Score
Conciseness	Significant verbosity throughout. Explains how to install gh CLI (Claude knows this), includes a redundant 'Using Templates for PR Creation' section that repeats earlier content, explains what `git status` does, and the 'Common Mistakes to Avoid' section largely restates the Best Practices section. The additional CLI commands section is reference material Claude already knows.	1 / 3
Actionability	Provides concrete bash commands and examples of PR titles, which is good. However, the PR description creation is incomplete—it references a template file (@.github/pull_request_template.md) but never shows its contents, so Claude can't actually fill it out. The `--body-file` approach pointing to the raw template file wouldn't produce a filled-in PR description.	2 / 3
Workflow Clarity	There is a reasonable sequence (pre-flight checks → prepare description → create PR), but there's no validation after PR creation (e.g., verify the PR was created successfully, check the PR URL). The pre-flight check for uncommitted changes is good, but the overall workflow lacks explicit checkpoints after the destructive/irreversible action of creating the PR.	2 / 3
Progressive Disclosure	References the PR template file and external docs, which is appropriate. However, the skill itself is monolithic—the additional CLI commands, installation instructions, and template usage sections could be separated or omitted. Content that should be inline (the actual template structure) is missing, while content that could be omitted (installation, basic gh commands) is included.	2 / 3
	Total	7 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
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	9 / 11 Passed

Repository: NeoLabHQ/context-engineering-kit
Commit: dedca19

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.