CtrlK
BlogDocsLog inGet started
Tessl Logo

contributor-pr-description

Guidelines and format for writing pull request descriptions in this repository. Use this skill whenever the user asks you to draft a pull request description, submit a PR, or update a PR description.

68

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, highly actionable, and appropriately scoped for a simple instruction skill, with only minor conciseness loss from explanatory padding Claude does not need.

Suggestions

Trim the opening rationale paragraph and the 'Tone and Style' list, which restate knowledge Claude already has.

Consider folding the identity-verification precondition into a short checklist so the precondition-to-action ordering is explicit.

DimensionReasoningScore

Conciseness

The body is mostly efficient and template-driven, but the opening rationale ('A good PR description speeds up the review process and serves as documentation...') and the 'Tone and Style' section ('Be clear and concise', 'Focus on the Why', 'Be professional') restate guidance Claude already knows and could be tightened.

2 / 3

Actionability

It provides a copy-paste-ready PR description template with concrete section structure, specific commands (`dart test`, `gh auth status`, `git commit --author="..."`), and concrete bad-vs-good summary examples — fully actionable for an instruction-only skill.

3 / 3

Workflow Clarity

This is a single-purpose, under-50-line skill whose single action (fill in the template) is unambiguous, with a clear precondition (identity verification before pushing/PR); per the simple-skills note, that warrants a 3 even without a multi-step validation loop.

3 / 3

Progressive Disclosure

No bundle files are needed or referenced, and the content is organized into well-labeled sections (Identity Verification, PR Description Template, Tone and Style, Bad vs Good Examples), satisfying the under-50-line/no-external-references case for a 3.

3 / 3

Total

11

/

12

Passed

Description

82%

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 solid description with an explicit 'what' and 'when' and natural trigger terms, weakened by an abstract opening framing, second-person voice, and a somewhat broad 'submit a PR' trigger that risks overlap with other git/PR skills.

Suggestions

Rewrite the opening in third person with concrete capabilities, e.g. 'Drafts, updates, and reviews pull request descriptions using this repository's template.'

Narrow the 'submit a PR' trigger to focus on the description (e.g. 'when the user asks you to draft or update the description for a pull request') to reduce overlap with general PR-creation skills.

Avoid second-person phrasing ('the user asks you to'); keep the trigger clause in third person to maximize specificity.

DimensionReasoningScore

Specificity

The description names the domain ('writing pull request descriptions in this repository') and concrete actions ('draft a pull request description, submit a PR, or update a PR description'), but the framing ('Guidelines and format for writing') is abstract and the actions are variations of one task rather than distinct capabilities; the second-person phrasing ('the user asks you to draft') triggers a 1-point reduction per the rubric guidelines.

2 / 3

Completeness

It explicitly states what the skill does ('Guidelines and format for writing pull request descriptions') and when to use it ('Use this skill whenever the user asks you to draft...'), with an explicit 'Use this skill whenever...' trigger clause.

3 / 3

Trigger Term Quality

It covers natural terms a user would say — 'pull request description', 'PR', 'draft', 'submit', and 'update' — giving good coverage of common phrasings rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The 'pull request description' niche is fairly distinct, but the 'submit a PR' trigger is broad enough to overlap with general PR-creation or git workflow skills, so it is not cleanly conflict-free.

2 / 3

Total

10

/

12

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.

Validation14 / 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
flutter/agent-plugins
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.