CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-draft-summary

Create the required PR-ready summary block, branch suggestion, title, and draft description for ioredis. Must be used before the final response whenever the actual task diff includes runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size. Skip only when no eligible files changed, every change is repo-meta or docs-only without behavior impact, the task is conversation-only, or the user explicitly opts out.

69

Quality

83%

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

75%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 well-structured, actionable skill body that leads with concrete git commands and a clear workflow. It is efficient but mildly redundant on skip conditions and would benefit from a worked output example and optional extraction of the command catalog.

Suggestions

Consolidate the skip conditions into one authoritative list; the description, Close-out Gate #4, and Output Format intro currently restate the same eligibility criteria three times.

Add one fully worked PR Draft block example (with a concrete title, branch, and description) so the template's expected output is unambiguous.

Consider moving the long git command catalog under 'Inputs to Collect' into a references file, leaving SKILL.md as a lean overview — this would tighten conciseness and improve progressive disclosure.

DimensionReasoningScore

Conciseness

Dense and free of concept over-explanation, with concrete git commands listed directly, but the skip conditions are restated three times (description, Close-out Gate #4, and Output Format) and the Inputs/Workflow sections overlap on 'run the commands above'.

4 / 5

Actionability

Provides copy-paste-ready git commands and concrete branch-naming rules (feat/<slug>, fix/<slug>, docs/<slug>), but the title and description are given only as template placeholders with no worked example showing a finished PR block.

4 / 5

Workflow Clarity

A clearly sequenced 9-step workflow with an explicit empty-diff checkpoint in step 2; the task is non-destructive so the validation cap does not apply, though a couple of decision branches could be more explicit.

4 / 5

Progressive Disclosure

Well-organized into Purpose, Close-out Gate, Inputs, Workflow, and Output Format sections with no external references needed, though the body runs slightly over 50 lines with all content inlined where a reference file could carry the command catalog.

4 / 5

Total

16

/

20

Passed

Description

92%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, specific description that clearly answers what the skill produces and exactly when to invoke it, including skip conditions. Trigger phrasing is slightly technical but overall highly actionable and distinct.

DimensionReasoningScore

Specificity

Lists multiple concrete deliverables — 'PR-ready summary block, branch suggestion, title, and draft description' — giving comprehensive coverage of the skill's outputs.

5 / 5

Completeness

Explicitly states the 'what' (create the summary block, branch, title, draft description for ioredis) and a very explicit 'when' covering both inclusion triggers and skip conditions, with concrete trigger phrases.

5 / 5

Trigger Term Quality

Captures natural terms like 'PR-ready summary', 'branch suggestion', 'title', and 'draft description', but the triggers lean technical ('runtime code', 'build/test configuration') and miss a few common user phrasings like 'draft a PR' or 'summarize my changes'.

4 / 5

Distinctiveness Conflict Risk

Scoped to ioredis and a specific PR-draft output with narrowly defined diff triggers, giving it a clear niche and minimal overlap with other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
redis/ioredis
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.