CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-pr

Opens pull requests with a consistent description format and assignment. Use when the user asks to open, create, file, or draft a PR or pull request, push a branch for review, or write a PR description.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An unusually disciplined workflow skill: fully executable commands, a clearly sequenced process with genuine validation and fallback steps, and no filler. It is slightly over-dense in places and keeps all policy inline rather than splitting peripheral detail into reference files.

DimensionReasoningScore

Conciseness

The body is dense, imperative policy Claude would not know ("Stage named paths, never `git add -A`") with no conceptual padding, but sections like Screenshots run long and a few justifications (e.g., the three-dots diff explanation) could be trimmed — matching "efficient; minor instances of over-explanation" rather than "every token earns its place".

4 / 5

Actionability

Guidance is copy-paste ready throughout: the batched context-gathering block, `gh pr create --base <base> --title "<title>" --body-file <path> --assignee @me`, the executable base-selection count via `git rev-list --count $(git merge-base ...)`, a real script (`"$SKILL_DIR/scripts/pr-stack.sh"`), and a concrete Too long/Right example table.

5 / 5

Workflow Clarity

A clear sequence (Gather context → Confirm before acting → Create or update → Description format → Cut) with explicit validation checkpoints and error-recovery loops: "Wait for approval", "Check `git status` after staging; if anything unexpected appears, stop and ask", "view each image before attaching; one that looks wrong is a bug to fix", "If an upload fails, the PR still opens — tell the user which are missing", and the `gh stack --help` failure fallback.

5 / 5

Progressive Disclosure

Sections are well-organized and the single bundle file (scripts/pr-stack.sh, verified to exist) is referenced one level deep and clearly signaled via `SKILL_DIR`; however, ~125 lines of policy are fully inlined where self-contained detail (the Screenshots rules, the base-selection algorithm) could live in reference files, matching "good structure; minor organization gaps" rather than the ideal split.

4 / 5

Total

18

/

20

Passed

Description

90%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 with an explicit "Use when" clause covering comprehensive natural trigger phrases and a clear, distinct PR-creation niche in third-person voice. Its only weakness is that the "what" states a single action rather than enumerating the skill's several concrete capabilities (updating existing PRs, stacking).

DimensionReasoningScore

Specificity

"Opens pull requests with a consistent description format and assignment" names the domain and one core action with qualifiers, but does not list several distinct concrete actions (e.g., updating an existing PR or stacking), matching the "names domain and 1-2 concrete actions" anchor rather than the "lists several specific actions" anchor above.

3 / 5

Completeness

It explicitly answers both: what ("Opens pull requests with a consistent description format and assignment") and when ("Use when the user asks to open, create, file, or draft a PR or pull request..."), with concrete trigger phrases matching the top anchor.

5 / 5

Trigger Term Quality

The "Use when" clause comprehensively covers natural phrasings users would say — "open, create, file, or draft a PR or pull request, push a branch for review, or write a PR description" — including synonyms (PR/pull request, four verbs for creating).

5 / 5

Distinctiveness Conflict Risk

A clear niche (PR creation/description) with distinct triggers like "push a branch for review" and "write a PR description"; minimal overlap with adjacent git/commit skills, matching the "clear niche with distinct triggers" anchor.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

RoleModel/rolemodel-skills

Path

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.