create-pr

Create a pull request with a clear, concise description that follows the repository's current PR template. Use when asked to open a PR or prepare its title and description.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%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 content is lean, actionable, and well-sequenced with explicit validation checkpoints for the publishing step, and is appropriately organized for a simple single-purpose skill. No bundle files are present or needed, and no weakness meriting suggestions was found.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive ("Write for busy developers", "Find and read the repository's applicable PR template every time") with no padding or explanation of concepts Claude already knows, matching the score-5 anchor.	5 / 5
Actionability	Despite being an instruction-only skill, it gives concrete executable guidance such as checking "the repository root, `.github/`, and `docs/`" and "use `--body-file` to preserve newlines and literal code", matching the score-5 anchor.	5 / 5
Workflow Clarity	Sections are clearly sequenced (Read template → Write description → Link related work → Create PR) with explicit validation checkpoints before publishing and duplicate-PR checks, matching the score-5 anchor including required feedback loops for a publish operation.	5 / 5
Progressive Disclosure	At ~40 lines with no external references needed, the four well-organized sections satisfy the simple-skill exception allowing a score-5 for progressive disclosure without bundle files.	5 / 5
	Total	20 / 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 clear, complete, and distinct, with explicit what-and-when guidance and natural trigger phrasing. Its only weakness is moderate specificity — it states one primary action rather than enumerating several concrete capabilities.

Suggestions

Broaden the capability list slightly to raise specificity, e.g. "Create a pull request with a clear, concise description, draft the title and body, and fill the repository's PR template."

Add a couple of natural synonyms to widen trigger coverage, such as "submit a PR" or "draft a pull request" alongside "open a PR".

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ("Create a pull request with a clear, concise description that follows the repository's current PR template") but does not enumerate several specific actions, matching the score-3 anchor rather than the multi-action score-4.	3 / 5
Completeness	Explicitly answers both what (create a PR with a template-following description) and when ("Use when asked to open a PR or prepare its title and description") with concrete trigger phrases, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Includes natural user phrases ("asked to open a PR", "prepare its title and description") with good coverage; falls short of 5 only because synonym/extension variety (e.g. "submit", "draft") is absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear PR-creation niche with distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: ueberdosis/tiptap
Path: skills/create-pr/SKILL.md
Commit: aef3880

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.