pr-submit

Create and submit a GitHub PR from the current branch

1.92x

Quality

—

Does it follow best practices?

Impact

96%

1.92x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

72%

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

The body is concise and well-structured with a clear sequence of mostly executable commands, but a few key steps lack exact commands and the workflow omits validation checkpoints for the destructive/outward-facing push and PR steps.

Suggestions

Provide exact commands for branch creation (e.g., `git checkout -b <branch>`) and commits, and show the full `gh pr create --title ... --body ...` invocation rather than the bare command.

Add a validation checkpoint after pushing (confirm the push succeeded) and after `gh pr create` (capture and verify the returned PR URL/number) before proceeding to the changelog and description steps.

Since pushing and opening a PR are outward-facing, include an explicit confirmation step with the user before pushing.

Dimension	Reasoning	Score
Conciseness	The ~20-line body is lean and assumes Claude's competence: every line is an actionable step with no padding or explanation of concepts Claude already knows.	3 / 3
Actionability	It gives real executable commands ("git status", "git diff", "gh pr create") but leaves key steps described rather than specified — "Create a new branch" with no exact command and "gh pr create" without --title/--body flags — so it is not copy-paste ready.	2 / 3
Workflow Clarity	The five numbered steps form a clear sequence, but there is no validation checkpoint for the outward-facing push and PR creation; per the guidelines missing verification in such operations caps workflow clarity at 2.	2 / 3
Progressive Disclosure	This is a short single-task skill under 50 lines with no need for external references, and its content is well-organized into a clear numbered Instructions section, which meets the bar for a 3.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 concise and names a concrete task, but it answers only the "what" and not the "when," and its trigger term coverage is narrow. It is adequate but leaves Claude without explicit invocation guidance.

Suggestions

Add an explicit "Use when..." trigger clause, e.g., "Use when the user asks to create, open, or submit a pull request from the current branch."

Broaden trigger terms to include "pull request" alongside "PR" so natural phrasings match.

Spell out concrete sub-actions (create branch, commit, push, open PR) to lift specificity from a single combined action to multiple specific actions.

Dimension	Reasoning	Score
Specificity	"Create and submit a GitHub PR from the current branch" names the domain (GitHub PR) and a concrete action, but it is a single combined action rather than the multiple specific concrete actions required for a 3.	2 / 3
Completeness	The description states what the skill does but provides no "Use when..." clause or equivalent trigger guidance; per the guidelines a missing trigger caps completeness at 2.	2 / 3
Trigger Term Quality	"GitHub PR" is a natural term users would say, but the description omits common variations like "pull request", so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	PR submission is a specific niche, but the description could still overlap with general git or PR-review skills and lacks distinct explicit triggers to separate it cleanly.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: pipecat-ai/pipecat
Commit: 037ee5d

Reviewed: 4 days 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.