CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr-create

Create or update a GitHub pull request for the current branch. Use when the user invokes `$pr-create`, asks to create/open a PR, or wants the current branch pushed and described as a draft PR.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 workflow is lean, fully executable, and well-checkpointed, with explicit stop conditions and label/template validation. The only gaps are the absence of error-recovery guidance for failed commands and the inlining of fairly detailed template-selection policy that could be split into a reference file.

DimensionReasoningScore

Conciseness

The body is dense operational instruction — bash snippets, ordered selection rules, and explicit stop conditions — with no padding or explanation of concepts Claude already knows. Every step earns its tokens, matching the lean anchor 5 rather than the minor-trim anchor 4.

5 / 5

Actionability

Fully executable commands throughout: `gh pr list --head "${branch}"…`, `git push -u "${remote}" "${branch}:${branch}"`, `gh label list`, and the complete `gh pr create --draft --assignee @me …` invocation. Placeholders appear only where content is inherently dynamic (title, generated body), matching the copy-paste-ready anchor 5.

5 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced with explicit validation checkpoints (default-branch stop, existing-PR check, label validation, unfilled-template blocker). It falls short of anchor 5 only because there are no error-recovery loops for command failures (e.g., push or `gh pr create` failing), landing at anchor 4's "minor validation gaps".

4 / 5

Progressive Disclosure

No bundle files exist, and the body is self-contained with clear section headers and hierarchical sub-steps (4a, 6a, 6b) for easy navigation. At ~135 lines, the detailed template detection/selection policy could arguably live in a reference file, so it matches anchor 4 (good structure, minor organization gaps) rather than the well-split anchor 5.

4 / 5

Total

18

/

20

Passed

Description

83%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 description: concrete actions, explicit when-to-use triggers with natural synonyms, and a clearly bounded niche. The only refinements would be enumerating a fuller action list and trimming the "update" overlap with the dedicated pr-update-desc skill.

DimensionReasoningScore

Specificity

"Create or update a GitHub pull request for the current branch" and "pushed and described as a draft PR" name the domain plus several concrete actions with only minor gaps (e.g., labeling and template handling are not mentioned). It does not reach anchor 5, which expects a comprehensive multi-action enumeration.

4 / 5

Completeness

It clearly states what the skill does ("Create or update a GitHub pull request for the current branch") and gives an explicit "Use when…" clause with concrete trigger phrases, exactly matching the anchor-5 example pattern rather than the weaker anchor 4.

5 / 5

Trigger Term Quality

Triggers include "invokes `$pr-create`", "asks to create/open a PR", and "described as a draft PR", giving good natural coverage with synonyms (create/open, PR/pull request). A few common phrasings like "submit a PR" or "ready for review" are missing, keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

The GitHub PR-creation niche with distinct triggers ($pr-create, create/open a PR, draft PR) is mostly distinct, but "or update" creates minor overlap with a dedicated PR-update skill (which the body delegates to $pr-update-desc). This matches anchor 4 (minor overlap risk with closely related skills), not the minimal-conflict anchor 5.

4 / 5

Total

17

/

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

phatblat/dotfiles

Path

.agents/skills/pr-create/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.