CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-changelog-update

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Quality

74%

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 ./.agents/skills/openclaw-changelog-update/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 an exceptionally actionable, well-sequenced release workflow with strong validation checkpoints and real executable commands. Its weaknesses are token weight and monolithic structure — verifier semantics and attribution policy are inlined rather than split into one-level-deep reference files.

DimensionReasoningScore

Conciseness

The body contains no filler explaining concepts Claude already knows — everything is project-specific contract — but at ~430 lines it includes dense multi-clause paragraphs (e.g. the 15-line npm beta-base rules) and attribution rules restated across multiple sections that could be materially tightened. This is anchor 3: mostly efficient but could be tightened.

3 / 5

Actionability

Guidance is fully executable with copy-paste ready commands (e.g. "node scripts/release-changelog.mjs write --version <version> --file <section.md>", full git log format strings, pnpm changelog:check) plus exact flags, paths, and placeholder conventions covering the common beta/stable/extended-stable cases. This matches anchor 5.

5 / 5

Workflow Clarity

A 10-step sequenced workflow includes explicit validation checkpoints (verify-release-notes failure conditions enumerated, pnpm changelog:check, pnpm release:candidate render check, git diff --check) and error-recovery guidance (e.g. what the command fails on and how to resume after quota exhaustion). This matches anchor 5: clear sequence, explicit validation, and feedback loops.

5 / 5

Progressive Disclosure

Sections are well-organized and the bundle script (scripts/verify-release-notes.mjs) is referenced by its real path, but roughly 250 lines of verifier flag semantics and attribution policy are inlined directly in SKILL.md where they clearly belong in separate reference files. This matches anchor 3: some structure, but content that should be separate is inline.

3 / 5

Total

16

/

20

Passed

Description

62%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 clear, appropriately concise, and distinct, with an explicit when-clause covering all three release types. Its main weaknesses are thin action coverage and missing common trigger synonyms such as "release notes", which limit discoverability from natural user phrasings.

Suggestions

Enumerate the key concrete actions in the description, e.g. "Regenerate release changelog sections and contribution records from git history, verify references and contributor credit, and publish docs mirrors."

Add natural trigger phrasings and synonyms such as "release notes" and "changelog rewrite", e.g. "Use when preparing release notes or rewriting the changelog for a beta, stable, or extended-stable release."

State the companion-skill boundary in the description (e.g. that this skill owns changelog content while release-openclaw-maintainer owns the release pipeline) to further reduce trigger overlap.

DimensionReasoningScore

Specificity

"Regenerate OpenClaw release changelog sections from git history" names the domain and one concrete action, but does not enumerate the broader capability set (grouped notes, attribution preservation, verification) that the skill actually performs. It fits anchor 3: 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

The what is clear ("Regenerate OpenClaw release changelog sections from git history") and the when is explicit ("before beta, stable, or extended-stable releases"). It is not a 5 because the when-clause is tied to release lifecycle timing rather than concrete user-utterance triggers, and not a 3 because the when is explicitly stated rather than merely implied.

4 / 5

Trigger Term Quality

Relevant keywords are present ("changelog", "git history", "beta", "stable", "extended-stable releases") but the very common synonym "release notes" and natural user phrasings like "update the changelog before release" are missing. This matches anchor 3: some relevant keywords, missing common variations or synonyms.

3 / 5

Distinctiveness Conflict Risk

The description is product-specific ("OpenClaw") and names a narrow niche (release changelog regeneration), so it is mostly distinct. Minor overlap risk remains with the closely related release-openclaw-maintainer skill mentioned in the body, which keeps it below a 5.

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

relative_links

Relative link issues: 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 4 missing, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

openclaw/openclaw

Path

.agents/skills/openclaw-changelog-update/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.