CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-description-skill

Use this skill to write the PR description (PR body) for any pull request opened against microsoft/apm. Produces one self-sufficient GitHub-Flavored Markdown artifact: TL;DR, Problem (WHY), Approach (WHAT), Implementation (HOW), 1-3 validated mermaid diagrams, explicit trade-offs, validation evidence, and a How-to-test section -- with every WHY-claim backed by a verbatim quote from PROSE or Agent Skills. Activate when the user asks to "write a PR description", "draft a PR body", "open a PR", "fill in the PR template", or any equivalent.

77

Quality

96%

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

92%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 a well-structured, actionable skill with an explicit sequenced workflow, validation feedback loops, and clean one-level progressive disclosure to real asset files. Its only weakness is mild repetition of a few rules across sections that could be tightened.

Suggestions

Deduplicate the '<details> for long evidence' guidance, which appears both in the Concision targets section and the GFM features section.

Consolidate the charset rule so it is stated once and merely cross-referenced from the Anti-patterns section instead of re-explained.

State the cite-or-omit rule once in Core principles and reference it from the execution checklist and output contract rather than restating it.

DimensionReasoningScore

Conciseness

The body is dense and mostly assumes Claude's competence (no explaining of what mermaid/GFM is), but a few points are repeated across sections (the <details> guidance appears twice; cite-or-omit and the charset rule are restated in anti-patterns), which keeps it just below fully lean.

4 / 5

Actionability

Provides copy-paste-ready executable guidance: a complete mmdc validation bash block, concrete git commands in the activation contract table, and an explicit ordered execution checklist covering the common PR-body cases.

5 / 5

Workflow Clarity

The execution checklist is a clearly sequenced multi-step process with explicit validation checkpoints (lint gate, mandatory mermaid validation, self-check pass, line-count check) and feedback loops (fix and re-run on mmdc failure).

5 / 5

Progressive Disclosure

SKILL.md acts as an overview with one-level-deep, clearly signaled references to real bundle files (assets/section-rubric.md, assets/mermaid-conventions.md, assets/pr-body-template.md, assets/scenario-evidence-rubric.md), each loaded only at the point it is needed.

5 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: it names the artifact, enumerates its concrete sections, scopes it to a single repo, and lists natural trigger phrases users would actually say. Both the what and the when are answered explicitly and concretely.

DimensionReasoningScore

Specificity

Lists multiple concrete output components ("TL;DR, Problem (WHY), Approach (WHAT), Implementation (HOW), 1-3 validated mermaid diagrams, explicit trade-offs, validation evidence, and a How-to-test section") with comprehensive coverage of what the artifact contains.

5 / 5

Completeness

Explicitly answers both what ("Produces one self-sufficient GitHub-Flavored Markdown artifact") and when ("Activate when the user asks to...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say ("write a PR description", "draft a PR body", "open a PR", "fill in the PR template") plus the "or any equivalent" catch-all, giving comprehensive synonym coverage.

5 / 5

Distinctiveness Conflict Risk

Scoped to a clear niche (PR descriptions for microsoft/apm) with distinct triggers, so it is unlikely to fire for an unrelated skill.

5 / 5

Total

20

/

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
microsoft/apm
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.