CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.qwen/skills/prepare-pr/SKILL.md
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.

The body is an efficient, well-structured instruction set for a simple single-purpose skill: exact commands, exact output paths, and precise body rules with an anti-mistakes section. The only notable gap is the absence of a worked example (a sample Conventional Commit title or a partially filled template) and any explicit output verification step.

DimensionReasoningScore

Conciseness

The body is lean and imperative throughout — sections like "Write: <output-dir>/pr-title.txt" and the PR Body Rules state operational constraints with no concept explanation or padding. Every token earns its place, matching the anchor for assuming Claude's competence.

5 / 5

Actionability

Concrete executable commands ("git diff origin/main...HEAD", "git log -1 --pretty=%B") and exact output paths make the workflow mostly executable, matching anchor 4. It falls short of anchor 5 because no example Conventional Commit title or filled-template snippet is provided for the key generation steps.

4 / 5

Workflow Clarity

A clear, ordered 5-step sequence with a conditional checkpoint ("Read <output-dir>/e2e-report.md if it exists") and a Common Mistakes section covering error avoidance. It stays at 4 rather than 5 because there is no explicit post-write verification (e.g., confirming template headings were preserved), though the non-destructive operation avoids the destructive-cap rule.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references (none of references/, scripts/, or assets/ exist); the well-organized sections (Inputs, Required Outputs, Workflow, PR Body Rules, Common Mistakes) satisfy the rubric guideline for scoring 5 in this case.

5 / 5

Total

18

/

20

Passed

Description

61%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 concrete and identifies a clear, distinctive niche, with good natural trigger terms around pull requests, diffs, and CI/autofix flows. Its main weakness is the absence of an explicit 'Use when...' trigger clause — the CI/autofix context is stated as scope rather than usage guidance — and its action coverage is limited to the two output artifacts.

Suggestions

Add an explicit trigger clause, e.g. "Use when asked to prepare or draft a PR title/body from a branch diff, especially in non-interactive CI/autofix flows, without pushing or creating the PR."

Broaden action coverage slightly by naming the concrete sub-actions (analyze the diff and commit history, fill the repository PR template, write title/body files) to move specificity from 1-2 actions toward several.

Include a few more natural trigger synonyms such as "PR description", "draft PR", or "pull request template" so users' varied phrasings match.

DimensionReasoningScore

Specificity

"Prepare GitHub pull request title and body files from the current branch diff" names the domain and two concrete actions (title file, body file), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several distinct actions, so score 4 does not fit.

3 / 5

Completeness

The 'what' is clear (prepare PR title and body files from the branch diff), but there is no 'Use when...' clause or equivalent explicit trigger guidance — "especially for non-interactive CI/autofix flows" reads as scoping context rather than an explicit when-to-use trigger, capping completeness at 3 per the judging guideline.

3 / 5

Trigger Term Quality

Natural terms users would say are present — "GitHub pull request", "PR template", "branch diff", "CI/autofix" — giving good keyword coverage. A few common phrasings (e.g., "draft PR", "PR description") are missing, so it falls short of the comprehensive synonym-level coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (preparing PR metadata files without pushing or creating the PR, in CI/autofix flows) is mostly distinct with clear boundary markers. Minor overlap risk remains with closely related skills such as PR-creation or commit-message skills, keeping it below anchor 5.

4 / 5

Total

14

/

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.

Validation — 15 / 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

Path

.qwen/skills/prepare-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.