CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-submit

Create and submit a GitHub PR from the current branch

62

Quality

73%

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 ./.claude/skills/pr-submit/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is an exemplary lean workflow: concrete commands, an explicit validate-before-push checkpoint, ordering rationale, and delegation to complementary skills instead of duplicating them. The only weakness is that `gh pr create` and branch creation are named without example invocations, leaving minor actionability gaps.

Suggestions

Show a concrete `gh pr create` invocation (e.g. `gh pr create --title ... --body-file ...`) to close the actionability gap.

Give an example branch-creation command (e.g. `git checkout -b fix/description`) instead of the bare directive.

DimensionReasoningScore

Conciseness

The 37-line body is lean and assumes Claude's competence — every token either instructs or adds non-obvious rationale ('while corrections are still cheap', 'Both skills review their own prose — no separate pass is needed here', why /prose-review won't see commit messages). No padded explanation of git or PR concepts, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete, copy-paste-ready commands appear throughout (`git status`, `git diff`, `git log --oneline -10`, push with `-u`, `gh pr create`, `/changelog <pr_number>`). Falls short of the 5 anchor only in minor gaps: `gh pr create` is named without example flags (title/body), and branch creation is a directive rather than a command.

4 / 5

Workflow Clarity

A clear six-step sequence with an explicit validation checkpoint before the irreversible push ('Run `/prose-review branch` and fix anything it flags. Do this before pushing') and a second check on commit messages via `git log main..HEAD`, matching the anchor with explicit validation steps and fix loops. Not 4 — no meaningful validation gap remains.

5 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and requires no external references; per the rubric's simple-skill guidance, well-organized sections alone qualify for 5. The body is cleanly sectioned with the numbered instructions carrying the entire workflow.

5 / 5

Total

19

/

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 concise and names a clear, distinct task, but it reads as a bare capability statement: no trigger guidance, no synonyms like 'pull request' or 'open a PR', and only two concrete actions. Adding a 'Use when...' clause and a fuller action list would move it into the top anchors.

Suggestions

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

Spell out key actions and synonyms to broaden trigger coverage: 'Create and submit a GitHub pull request (PR): branch, commit, push, and open the PR with gh.'

Mention the supporting workflow (commit messages, changelog) so the 'what' is more comprehensive rather than just 'create and submit'.

DimensionReasoningScore

Specificity

Names the domain ('GitHub PR') and two concrete actions ('Create and submit') but stops there — comprehensive coverage would also mention branch creation, pushing, or changelog updates, so it matches the '1-2 concrete actions, not comprehensive' anchor rather than the 'several specific actions' anchor at 4.

3 / 5

Completeness

The 'what' is clear (create and submit a GitHub PR from the current branch), but there is no 'Use when...' clause or equivalent trigger guidance; the guidelines explicitly cap completeness at 3 in that case. Not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'GitHub PR', 'submit', and 'current branch' are relevant keywords, but natural phrases users would say — 'pull request', 'open a PR', 'submit a PR' — are missing as synonyms, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Create and submit a GitHub PR from the current branch' carves a distinct PR-creation niche with concrete triggers (GitHub, PR, current branch); only minor overlap risk with closely related skills like PR review or merge skills keeps it from a 5.

4 / 5

Total

13

/

20

Passed

Validation

100%

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