CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr

Creates a draft GitHub pull request with a plain-text conventional-commit title and a succinct description of the branch. Use when the user asks to open, raise, or create a pull request or PR.

Quality

94%

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

93%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 an exemplar of lean, actionable skill writing — every token is a constraint, command, or example rather than explanation. The single weakness is a workflow step ('uncommitted changes') whose failure path is never specified, leaving a small ambiguity in an otherwise well-validated sequence.

DimensionReasoningScore

Conciseness

The body is lean and directive-only: it explains no concepts Claude already knows (no PR or conventional-commit primers), and every section — Title Rules, Body Rules, Error Handling — carries constraints Claude would not infer on its own. The one-line intro duplicates the frontmatter description only slightly and serves as a legitimate summary.

5 / 5

Actionability

Fully executable guidance throughout: the exact create command ('gh pr create --draft --title "<type>(<scope>): <subject>" --body-file <file> --base main'), three example titles, a default body template, a complete worked example body, and copy-paste common actions.

5 / 5

Workflow Clarity

A clear 4-step sequence opens with validation ('gh auth status, current branch, uncommitted changes') and an Error Handling section provides recovery paths, but the uncommitted-changes check names no action (commit? abort?) and there is no post-create confirmation step — minor validation gaps that fit the anchor 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist, and none are needed: the ~93-line body is well-sectioned (Workflow, Title Rules, Body Rules, Common Actions, Error Handling), cohesive, and contains nothing that belongs in a separate reference file, so navigation within SKILL.md is easy with no deep-reference risk.

5 / 5

Total

19

/

20

Passed

Description

95%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, third-person, and lean, with explicit what/when structure and natural trigger phrasing. Its only shortcoming is modest coverage — auxiliary actions present in the body (mark ready, add reviewers) are not surfaced in the description.

DimensionReasoningScore

Specificity

The description lists several concrete deliverables — 'Creates a draft GitHub pull request', 'plain-text conventional-commit title', 'succinct description of the branch' — rather than vague language, but omits auxiliary capabilities covered in the body (marking ready, adding reviewers), keeping it short of comprehensive coverage.

4 / 5

Completeness

It explicitly answers 'what' (creates a draft GitHub PR with a conventional-commit title and succinct description) and 'when' ('Use when the user asks to open, raise, or create a pull request or PR') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'open, raise, or create a pull request or PR' covers the natural verbs users say plus both noun forms ('pull request' and 'PR'), matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — GitHub pull request creation via gh with specific formatting rules — and its PR-specific triggers minimally overlap with related skills like commit-message generation.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

rikdc/ai-skills

Path

plugins/git-workflow/skills/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.