CtrlK
BlogDocsLog inGet started
Tessl Logo

changelog

How to keep each app's user-facing changelog. Use when you ship a change a user would notice (a new feature, a visible improvement, a bug fix), when wiring the in-app "What's new" surface into a template, or when releasing pending changelog entries. Apps opt in with `changelog.enabled: true` in `agent-native.config.ts`.

68

Quality

85%

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

82%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 well-organized, highly actionable body with concrete commands and copy-paste code covering add, release, and in-app wiring, plus a useful checklist. It could be slightly leaner in the Releasing prose and would benefit from an explicit verification step in the release workflow.

Suggestions

Tighten the 'Releasing' paragraph: collapse the Vite-plugin/Changesets explanation into one or two lines, moving deep mechanics to a reference if needed.

Add an explicit verify step to the release flow (e.g. run `agent-native changelog list` and confirm the new entry appears) to close the loop with a checkpoint.

The closing checklist is good; consider promoting the 'change is user-visible?' gate into the 'When to add an entry' section so the validation is encountered before action.

DimensionReasoningScore

Conciseness

Mostly efficient and well-sectioned with executable commands and code earning their place; the dense 'Releasing' paragraph about the Vite plugin and package Changesets could be trimmed. Not a 5 because several explanatory sentences go slightly beyond what Claude needs to know.

4 / 5

Actionability

Fully executable, copy-paste ready guidance throughout: concrete `agent-native changelog add "..." --type added` commands, a complete frontmatter example, and ready-to-use TSX snippets for both CommandMenu and ChangelogSettingsCard wiring.

5 / 5

Workflow Clarity

Clear add -> release -> wire sequence with a closing checklist and a note that rerunning release is safe; checkpoints are present but there is no explicit validate/fix/retry feedback loop. Not capped at 3 because the operations are non-destructive and idempotent, and not a 5 due to the absence of explicit error-recovery steps.

4 / 5

Progressive Disclosure

Single self-contained SKILL.md with clear, well-ordered sections (When to add, How to add, Writing good entries, Releasing, Wiring, Checklist) and no nested skill references; the under-50-line exception does not apply, and content is appropriately placed with only minor organization gaps.

4 / 5

Total

17

/

20

Passed

Description

87%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, third-person description that clearly states what the skill does and gives explicit, natural 'Use when...' triggers covering add/wire/release scenarios. Minor room to broaden trigger synonyms, but it is comprehensive and distinctive.

Suggestions

Add a couple of common user-side synonyms or phrasings (e.g. 'release notes', 'ship notes') to push trigger-term coverage toward comprehensive.

Tighten 'How to keep each app's user-facing changelog' into a more concrete lead verb to lift specificity.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('keep each app's user-facing changelog', 'wiring the in-app "What's new" surface into a template', 'releasing pending changelog entries'), with only minor coverage gaps. Not a 5 because 'keep' is somewhat generic and the action set, while specific, is not exhaustive.

4 / 5

Completeness

Explicitly answers both what (keep/wire/release the user-facing changelog) and when via a concrete 'Use when you ship a change a user would notice (a new feature, a visible improvement, a bug fix), when wiring... or when releasing pending changelog entries' trigger clause.

5 / 5

Trigger Term Quality

Strong natural trigger phrases ('What's new', 'changelog', 'new feature', 'visible improvement', 'bug fix', 'releasing') with good synonym coverage; falls short of 5 only because no file extensions or additional common variants are included.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (per-app user-facing changelog gated on `changelog.enabled: true`) with distinct triggers like 'What's new' surface and `agent-native.config.ts`, giving minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
BuilderIO/agent-native
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.