CtrlK
BlogDocsLog inGet started
Tessl Logo

prepare-pr

Prepare GitHub pull request title and body files from the current branch diff, especially for non-interactive CI/autofix flows that must follow the repository PR template without pushing or creating the PR.

70

Quality

86%

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.

A tight, highly actionable instruction skill with concrete commands and clear anti-pattern guidance. The only gap is the absence of an explicit validation checkpoint in the workflow, though the task is non-destructive file writing.

Suggestions

Add a brief verification step to the workflow (e.g., confirm both pr-title.txt and pr-body.md exist and that all template headings are preserved before finishing).

DimensionReasoningScore

Conciseness

The body is lean throughout — "Create PR metadata files only. Do not push, comment, or run `gh pr create`" — with no padding and no explanation of concepts Claude already knows; every line earns its place.

5 / 5

Actionability

Guidance is concrete and executable: exact git commands ("git diff origin/main...HEAD", "git log -1 --pretty=%B"), specific output paths, and a Common Mistakes list of concrete anti-patterns cover the common cases.

5 / 5

Workflow Clarity

A clear numbered 5-step sequence is present, but there is no explicit validation/checkpoint step after writing the files; the skill is non-destructive so no validation cap applies.

4 / 5

Progressive Disclosure

The body is under 50 lines with no need for external references, and is organized into clearly labeled sections (Inputs, Required Outputs, Workflow, PR Body Rules, Common Mistakes) making it easy to navigate.

5 / 5

Total

19

/

20

Passed

Description

78%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 specific, well-triggered description that clearly conveys both what the skill does and the CI/autofix context it targets. It is held back only by a moderately explicit (rather than crisp "Use when...") trigger clause and a few missing action specifics.

Suggestions

Add an explicit "Use when..." trigger clause naming the situations that should activate this skill.

Mention the Conventional Commit title format and in-place template filling in the description to round out the action list.

DimensionReasoningScore

Specificity

"Prepare GitHub pull request title and body files from the current branch diff" lists several concrete actions (title, body files, from branch diff) but omits specifics like Conventional Commit format and template filling that appear only in the body.

4 / 5

Completeness

It answers both "what" (prepare PR title/body files from the branch diff) and "when" ("especially for non-interactive CI/autofix flows that must follow the repository PR template"), with the "when" moderately explicit rather than a clean "Use when..." trigger.

4 / 5

Trigger Term Quality

Natural terms users would say are present ("GitHub pull request", "PR title", "PR body", "branch diff", "CI/autofix", "PR template") with good coverage, though a few common synonyms like "PR description" are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — generating PR metadata files for CI/autofix flows "without pushing or creating the PR" — giving it distinct triggers and minimal conflict risk with general PR-creation skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
QwenLM/qwen-code
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.