CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-pr

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

Quality

87%

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.

A tight, well-sequenced instruction-only skill whose guidance is concrete and specific throughout, with token-efficient prose that assumes Claude's intelligence. The only improvement space is an explicit pre-PR verification checkpoint and an example `gh` fallback command.

DimensionReasoningScore

Conciseness

The 12-line body is lean and assumes Claude's competence: it names the tool choice ("Use the GitHub MCP server to create a pull request if available, otherwise use `gh` CLI") and each numbered step without any concept explanation or padding.

5 / 5

Actionability

Steps are concrete and specific (use the `/commit` skill, prefix examples like "sessions: …", pass `show_ui=false`), but no example `gh pr create` command is given, leaving a minor gap between the fallback tool choice and actual execution.

4 / 5

Workflow Clarity

Six steps are clearly sequenced with a fix-errors feedback loop in step 1 ("Run the compile and hygiene tasks (fixing any errors)"), but there is no explicit checkpoint confirming tasks pass before the PR is created. PR creation is not destructive or batch, so no cap applies.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well organized; the only reference (the `/commit` skill) is clearly signaled, satisfying the simple-skill exception.

5 / 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, lean description that clearly states a single concrete capability and an explicit, naturally phrased trigger clause. Its only weaknesses are modest keyword variation and slight overlap with adjacent commit-skill triggers.

DimensionReasoningScore

Specificity

The description names the domain and a concrete action ("Create a pull request for the current session"), which fully covers this single-purpose skill, placing it above the 1-2-actions-but-incomplete anchor but below the multiple-specific-actions anchor.

4 / 5

Completeness

It explicitly answers both what ("Create a pull request for the current session") and when ("Use when the user wants to open a PR with the session's changes") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It covers the key synonym pair "pull request" and "PR" in natural phrasing ("open a PR"), but a few natural variations like "submit a PR" or "make a PR" are missing.

4 / 5

Distinctiveness Conflict Risk

The PR-creation niche with "session's changes" triggers is mostly distinct, with only minor overlap risk against closely related commit-focused skills.

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

posit-dev/positron

Path

src/vs/sessions/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.