create-release-note

Create a reno release note for a PR or change

Quality

55%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/create-release-note/SKILL.md

Quality

Discovery

32%

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 identifies a specific tool (reno) and a single action (create release note), giving it some distinctiveness, but it lacks explicit trigger guidance ('Use when...'), comprehensive action listing, and broader keyword coverage. It is too terse to reliably help Claude select this skill from a large pool of available skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a release note, changelog entry, or mentions reno.'

Include additional trigger terms users might naturally say, such as 'changelog', 'release notes', 'reno new', or 'version note'.

Expand the capability description with more concrete actions, e.g., 'Creates reno release notes with appropriate categories (features, bug fixes, deprecations) for a PR or code change.'

Dimension	Reasoning	Score
Specificity	Names the domain ('reno release note') and a single action ('create'), but doesn't list additional concrete actions like editing, formatting, or categorizing release notes.	2 / 3
Completeness	Describes what it does ('create a reno release note') but has no explicit 'Use when...' clause or trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also quite thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'reno', 'release note', 'PR', and 'change', but misses common variations users might say such as 'changelog', 'release notes', 'releasenote', or 'reno new'.	2 / 3
Distinctiveness Conflict Risk	'Reno' is a fairly specific tool, which helps distinctiveness, but the mention of 'PR or change' is generic enough that it could overlap with other changelog or documentation skills.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

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

This is a well-crafted skill with strong actionability and workflow clarity — it provides executable commands, concrete examples, explicit validation steps, and a clear feedback loop. Its main weaknesses are moderate verbosity from duplicated section descriptions (Step 1 vs. the guidelines table) and a monolithic structure that could benefit from splitting reference material into separate files. Overall it's a solid, production-ready skill.

Suggestions

Remove the Section Guidelines table or the section descriptions in Step 1 to eliminate duplication — one location is sufficient.

Consider extracting RST formatting rules and section guidelines into a referenced file (e.g., FORMATTING.md) to reduce the main skill's token footprint.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient and provides necessary detail for a multi-step interactive workflow, but the section guidelines table partially duplicates the section descriptions already given in Step 1. The 'When to skip' section and some explanatory text could be tightened.	2 / 3
Actionability	Provides fully executable commands (`reno new <topic> --no-edit`, `dda inv linter.releasenote`), concrete YAML file format examples, specific RST formatting rules with correct/incorrect patterns, and clear examples for each section type. Copy-paste ready.	3 / 3
Workflow Clarity	Clear 4-step sequence (gather info → create file → format content → verify) with an explicit validation step (linter) and a feedback loop (fix and re-run). The workflow covers destructive template replacement and includes verification before completion.	3 / 3
Progressive Disclosure	The content is well-structured with clear headers and a logical flow, but it's a fairly long monolithic file. The section guidelines table and the detailed RST formatting rules could be split into referenced files for better token efficiency, though no bundle files exist to support this.	2 / 3
	Total	10 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: DataDog/datadog-agent
Commit: a41685a

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.