CtrlK
BlogDocsLog inGet started
Tessl Logo

release-notes

Draft short release notes from a list of changes. Use when the user asks for changelogs, release notes, or a concise product update.

69

Quality

84%

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

86%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 concise, well-structured skill body that gives executable guidance and points to real bundle files. It could be marginally more actionable with a full invocation example and more explicit validation steps.

Suggestions

Include a complete example invocation of scripts/format-release-notes.ts (e.g., the full command plus a sample input) so guidance is copy-paste ready.

Add an explicit verification checkpoint, such as confirming bullets are user-facing before finalizing the draft.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; it explains no basic concepts and every line (process steps, script invocation, output template) earns its place.

5 / 5

Actionability

It names the concrete script, its input shape ({ "changes": [...] }), the function signature, and how it reads the style guide via ctx.files, with a copy-paste output template; the only gap is no full example invocation command.

4 / 5

Workflow Clarity

A clear 4-step process plus an explicit fallback for vague input is sequenced well, but validation checkpoints between steps are implicit rather than spelled out.

4 / 5

Progressive Disclosure

Content is organized into clear sections and references real one-level-deep bundle files (scripts/format-release-notes.ts and references/style-guide.md, both present) with clear signaling.

5 / 5

Total

18

/

20

Passed

Description

82%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 description that cleanly answers both what the skill does and when to trigger it, using natural user phrasing. The only weakness is limited specificity of capabilities, naming just a single action.

Suggestions

Add 1-2 more concrete capabilities (e.g., "summarize grouped changes", "format bullets for a specific audience") to lift specificity above a single action.

DimensionReasoningScore

Specificity

It names the domain and one concrete action ("Draft short release notes from a list of changes") but lists no further capabilities, matching the anchor that names the domain with only 1-2 concrete actions.

3 / 5

Completeness

It explicitly states what it does (draft release notes from a list of changes) and when to use it with concrete trigger phrases, satisfying the top anchor for both.

5 / 5

Trigger Term Quality

"Use when the user asks for changelogs, release notes, or a concise product update" provides good natural keyword coverage with synonyms, though a few common variations (e.g. "what's new") are missing.

4 / 5

Distinctiveness Conflict Risk

The release-notes niche has distinct, specific triggers (changelogs, release notes, product update) with minimal overlap risk against other skills.

5 / 5

Total

17

/

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
cloudflare/agents
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.