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.

68

Quality

81%

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

72%

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

A compact, well-structured checklist that respects the token budget and is easy to navigate. It loses points on actionability and workflow clarity: several steps are abstract and there are no explicit validation checkpoints before the PR is created.

Suggestions

Name the specific GitHub MCP tool(s) to call (e.g. create_pull_request) or include a minimal example invocation so step 6 is copy-paste ready.

Add an explicit validation checkpoint before creating the PR, such as 'confirm compile and hygiene tasks pass' or 'verify tests are green'.

Tighten vague steps like 'Run the compile and hygiene tasks' and 'Review all changes' with the concrete commands or review criteria to perform.

DimensionReasoningScore

Conciseness

The body is lean — a one-line framing rule plus a six-item checklist with no padding and no explanation of concepts Claude already knows — so every token earns its place, matching the 'lean and efficient' anchor at 3.

3 / 3

Actionability

Some guidance is concrete ("do NOT use the `gh` CLI", area-prefix examples like "sessions: …"), but steps such as "Run the compile and hygiene tasks" and "Review all changes" are vague direction with no MCP tool names or example invocation, matching the 'some concrete guidance but incomplete' anchor at 2 rather than the copy-paste-ready anchor at 3.

2 / 3

Workflow Clarity

The six steps are clearly sequenced and step 1 mentions fixing errors, but there are no explicit validation/verification checkpoints (e.g., confirm tests pass before creating the PR, verify the PR URL), so it sits at the 'steps listed but checkpoints missing or implicit' anchor at 2 rather than the explicit-checkpoint anchor at 3.

2 / 3

Progressive Disclosure

This is a short single-purpose skill (well under 50 lines) with no bundle files and no need for external references, organized into a heading, framing line, and numbered list — matching the rubric note that such skills score 3 with well-organized sections.

3 / 3

Total

10

/

12

Passed

Description

90%

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 concise, well-formed description that clearly states the capability and an explicit trigger, using natural user phrasing. Its only weakness is specificity: it names a single action rather than a fuller set of concrete capabilities.

DimensionReasoningScore

Specificity

It names one concrete action ("Create a pull request") and the domain, but is not comprehensive — there are no sub-actions listed, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multiple-actions anchor at 3 or the vague anchor at 1.

2 / 3

Completeness

It states both what ("Create a pull request for the current session") and an explicit when ("Use when the user wants to open a PR with the session's changes"), satisfying the explicit-trigger anchor at 3 and avoiding the 'when only implied' cap at 2.

3 / 3

Trigger Term Quality

"pull request" and "open a PR" are exactly the natural phrases a user would say when they need this skill, giving good coverage of the relevant terms; it is above the 2 anchor which expects missing common variations.

3 / 3

Distinctiveness Conflict Risk

The scope is narrowly scoped to opening a PR for the current session's changes, a clear niche unlikely to fire for unrelated skills, matching the distinct-triggers anchor at 3 rather than the overlap-prone 2 anchor.

3 / 3

Total

11

/

12

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.