CtrlK
BlogDocsLog inGet started
Tessl Logo

breaking-change-doc

Generate breaking change documentation for merged dotnet/runtime PRs. USE FOR: creating breaking change docs, "document this breaking change", "write breaking change issue for PR #NNNNN", processing PRs labeled needs-breaking-change-doc-created. DO NOT USE FOR: general code review (use code-review skill), bug fixes, API proposals (use api-proposal skill).

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 content is highly actionable with a clear, well-validated multi-step workflow and concrete commands throughout. Its main weakness is conciseness, where Step 2's version-detection rationale and JSON-field enumeration are padded beyond what Claude needs.

Suggestions

Tighten Step 2: move the long prose on .NET cadence, backport semantics, and the full JSON field enumeration into a separate reference file, keeping only the command, the Error/Tentative decision rules, and the 'print full JSON' instruction inline.

Trim the redundant re-statements in Step 2 (e.g. the candidate-vs-confirmed backport guidance is restated across several bullet points) to a single concise decision table.

Consider extracting the area-* label mapping table (Step 1) into a references file so the core SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient procedural guidance, but the Step 2 version-detection explanation is quite long and re-explains .NET release cadence and backport semantics that could be trimmed; some padded explanatory prose around the JSON fields.

3 / 5

Actionability

Provides concrete, copy-pasteable commands (pwsh Get-VersionInfo.ps1, gh api calls, Build-IssueComment.ps1 with full flag list) and explicit, executable steps for each phase including exact output paths and template paths.

5 / 5

Workflow Clarity

A clearly sequenced Step 0-6 process with explicit validation checkpoints (duplicate check in Step 3, Error/Tentative handling in Step 2, confirmation gates and dry-run/draft modes in Step 6) and a troubleshooting table for error recovery.

5 / 5

Progressive Disclosure

Well-organized with a clear overview table of bundle files and one-level-deep references to helper scripts, but the inlined JSON-field reference and large Step 2 explanation could arguably live in a separate reference file; no references/ or scripts/ bundle directory is present alongside SKILL.md.

4 / 5

Total

17

/

20

Passed

Description

86%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 specific, well-scoped, and explicitly answers both what and when with concrete trigger phrases and clear anti-triggers. It is a strong, highly distinctive description with only minor room for more natural synonyms.

DimensionReasoningScore

Specificity

Names the domain (breaking change docs for dotnet/runtime PRs) and several concrete actions (creating docs, writing issues, processing labeled PRs), though the actions overlap conceptually rather than covering distinct operations.

4 / 5

Completeness

Explicitly answers 'what' (generate breaking change documentation for merged dotnet/runtime PRs) and 'when' via both a USE FOR clause with concrete trigger phrases and a DO NOT USE FOR clause that disambiguates.

5 / 5

Trigger Term Quality

Includes natural trigger phrases like 'document this breaking change', 'write breaking change issue for PR #NNNNN', and the label 'needs-breaking-change-doc-created'; missing some synonyms or alternate phrasings a user might naturally say.

4 / 5

Distinctiveness Conflict Risk

A clearly defined niche (dotnet/runtime breaking change docs filed in dotnet/docs) with explicit 'DO NOT USE FOR' boundaries against code-review and api-proposal skills, minimizing conflict risk.

5 / 5

Total

18

/

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
dotnet/runtime
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.