CtrlK
BlogDocsLog inGet started
Tessl Logo

update-pr-description

Evaluate a PR's title and description against its actual implementation, then iteratively suggest and apply updates. Use when the user asks to check, fix, or update a PR title or description.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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.

A tight, well-structured instruction-only skill: every step is tied to a concrete gh command, the workflow includes an early-exit checkpoint and an iterative user-confirmation loop before the destructive edit, and the Notes section captures non-obvious repository conventions. Nothing wasted, nothing missing.

DimensionReasoningScore

Conciseness

Every line is actionable or carries non-obvious judgment guidance ("Only flag *meaningful* divergence... Ignore trivial wording", "Do not remove the canary release section"). No concept re-explanation or padding exists, matching the lean anchor-5 example.

5 / 5

Actionability

Each step includes an exact, executable command — "gh pr view", "gh pr view <pr> --json title,body", "gh pr diff <pr>", "gh pr edit <pr> --title ... --body ..." — plus concrete criteria for what counts as divergence. Per the rubric's instruction-only guidance note, this actionable specificity merits the top anchor.

5 / 5

Workflow Clarity

Six numbered steps in a clear sequence with explicit checkpoints: step 4's early exit ("If not, stop here"), step 5's one-change-at-a-time user confirmation loop, and step 6 gated on agreement before the mutating edit. Not 4 because no validation checkpoint is missing for the write operation.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and content is organized into well-signaled sections (Workflow, Notes). The rubric's simple-skill guideline awards 5 in exactly this case.

5 / 5

Total

20

/

20

Passed

Description

87%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: concise, third person, with a concrete what and an explicit when clause carrying natural trigger terms. It mirrors the rubric's good-example structure with only minor gaps in synonym coverage.

DimensionReasoningScore

Specificity

"Evaluate a PR's title and description against its actual implementation, then iteratively suggest and apply updates" names the domain plus three concrete actions (evaluate, suggest, apply). Not 3 because more than 1-2 actions are listed; not 5 because coverage has minor gaps (e.g., how the update workflow interacts with PR templates or bodies is unenumerated).

4 / 5

Completeness

Both questions answered explicitly: what ("Evaluate a PR's title and description against its actual implementation, then iteratively suggest and apply updates") and when ("Use when the user asks to check, fix, or update a PR title or description") with concrete trigger phrases. Matches the anchor-5 good example structure exactly.

5 / 5

Trigger Term Quality

"Use when the user asks to check, fix, or update a PR title or description" gives good natural-keyword coverage (check, fix, update, PR title, PR description). Not 5 because common synonyms like "edit", "rewrite", or "PR body/summary" are missing; clearly above 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (PR title/description maintenance) with triggers that explicitly name PR title and description, minimizing conflict with general PR-review or commit-message skills. At most trivial overlap with generic "check a PR" phrasing, which anchor 5 permits.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
storybookjs/storybook
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.