CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

patch-notes

Player-facing patch notes from git history and changelogs. Translates developer language into player communication.

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/patch-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, highly actionable workflow: every phase has concrete commands, paths, verbatim failure messages, and complete output templates, with genuine validation gates and hard stops. The only weaknesses are mild — two rationale paragraphs that could be trimmed and inline templates that could be externalized at this length.

DimensionReasoningScore

Conciseness

The body is dominated by lean directives, exact paths, and placeholder templates, with only minor over-explanation — the 'Why this is a hard stop, not a warning' and 'Filter per commit' rationale paragraphs could be trimmed without losing the instruction. Not 5 because that padding is real; not 3 because most content earns its place.

4 / 5

Actionability

Fully executable guidance throughout: exact commands ('git log --oneline -20'), exact file paths (docs/CHANGELOG.md, production/sprints/, design/balance/), verbatim blockquote messages for both failure branches, and three complete output templates plus concrete translation examples ('Refactored damage calculation pipeline' → 'Improved hit detection accuracy').

5 / 5

Workflow Clarity

A clearly sequenced multi-phase workflow (Provenance check → Phases 1–7) with explicit validation checkpoints: the provenance hard stop with a verbatim failure message, the no-changelog-data stop with its message, a Phase 5 review checklist, and a permission gate before any file write. Error paths instruct stop-and-report rather than silent continuation.

5 / 5

Progressive Disclosure

A single well-sectioned file with no bundle files; the core style templates are appropriately inline since they are used on nearly every invocation. Minor gap: at ~240 lines, the three full style templates (~70 lines) could be split into a references file to keep SKILL.md a leaner overview.

4 / 5

Total

18

/

20

Passed

Description

61%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 communicates a clear, distinct capability with concrete actions and natural trigger terms, but it never tells Claude when to use it. Adding an explicit 'Use when...' clause with the 'release notes' synonym would lift both completeness and trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for patch notes, release notes, or a player-facing announcement for a game version.'

Include the synonym 'release notes' (and possibly 'update announcement') among the trigger terms to broaden natural keyword coverage.

Mention one or two additional concrete capabilities — e.g. output styles (brief/detailed/full) or writing notes to docs/patch-notes/ — to round out specificity.

DimensionReasoningScore

Specificity

Names the domain ('Player-facing patch notes from git history and changelogs') and two concrete actions — generating notes from git/changelog sources and 'Translates developer language into player communication' — but omits styling, categorization, and output destinations, so coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear (generate player-facing patch notes from git history and changelogs), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is only weakly implied, which caps this dimension at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'patch notes', 'git history', 'changelogs', 'player' are terms users would actually say, though the common synonym 'release notes' is missing. Not 5 because synonym-level coverage is absent.

4 / 5

Distinctiveness Conflict Risk

'Player-facing patch notes' carves a clear niche distinct from internal changelog tooling, with minor overlap risk against a closely related changelog-writing skill. Not 5 because the missing 'when' clause leaves triggering keyword-only and the sibling /write-changelog skill occupies adjacent territory.

4 / 5

Total

14

/

20

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/patch-notes/SKILL.md

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.