CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pr

Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.

69

Quality

84%

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

86%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 a tight, well-sequenced six-step workflow that assumes Claude's competence and avoids bloat. It loses only slightly on actionability and workflow clarity where a couple of steps leave specifics implicit rather than fully explicit.

DimensionReasoningScore

Conciseness

The body is a lean six-step list with no padding or explanation of concepts Claude already knows; every token earns its place, matching the anchor for lean and efficient content.

5 / 5

Actionability

Steps give concrete, executable guidance (GitHub MCP server not gh CLI, `/commit` skill, `show_ui=false`, area-prefix examples) but step 1's "compile and hygiene tasks" and step 3 leave a few specifics implicit, fitting the mostly-executable-with-minor-gaps anchor.

4 / 5

Workflow Clarity

A clear six-step sequence with an implicit fix loop in step 1; validation is implicit rather than an explicit checkpoint, matching the clear-sequence-with-minor-validation-gaps anchor.

4 / 5

Progressive Disclosure

A simple, single-purpose skill under 50 lines with no bundle files and a well-organized numbered list, satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

82%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 clearly answers both what the skill does and when to use it, with natural trigger terms and low conflict risk. It is only slightly limited on specificity, naming a single action rather than enumerating the full scope of PR creation.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("Create a pull request for the current session") but does not enumerate multiple specific actions, matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Explicitly states both what it does ("Create a pull request for the current session") and when to use it ("Use when the user wants to open a PR with the session's changes"), matching the anchor that requires both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users say ("pull request", "open a PR", "session's changes") but misses common variations like review, merge, or diff, fitting the good-coverage-with-few-missing-terms anchor.

4 / 5

Distinctiveness Conflict Risk

"Create a pull request" / "open a PR" is a clear, narrow niche with distinct triggers and minimal conflict risk against other skills.

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
posit-dev/positron
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.