CtrlK
BlogDocsLog inGet started
Tessl Logo

changeset

Command: changeset

52

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/changeset/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a strong, actionable reference: concrete templates, wrong/correct examples, and explicit verification gates for a release-sensitive workflow. The only minor weakness is light repetition of the 'relative to main' rule and registry delegation.

DimensionReasoningScore

Conciseness

The body is largely lean with imperative bullets and copy-paste examples and assumes Claude's competence, though the 'relative to main' rule and registry-changelog delegation are each restated, adding minor trimmable repetition.

4 / 5

Actionability

It provides concrete wrong/correct YAML frontmatter, real file paths, exact CLI commands for the registry generator, and copy-paste templates for simple, API, and breaking changes covering the common cases.

5 / 5

Workflow Clarity

The release-sensitive operation is gated by explicit validation: the 'Before shipping' Red Flags checklist, the 'what will a user upgrading from main observe?' verification question, the 'check the API exists on main' gate, and the generator `--check` command form a clear validation/feedback loop.

5 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear section headers and no bundle files; registry detail is appropriately delegated to the sibling registry-changelog skill rather than duplicated, fitting the simple-skill exception.

5 / 5

Total

19

/

20

Passed

Description

28%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 essentially a bare label ('Command: changeset') with no stated actions, triggers, or use-conditions, making it weak across specificity, trigger quality, and completeness. Its only real strength is that the term 'changeset' is a distinct niche artifact name.

Suggestions

Add concrete actions, e.g. 'Write and format .changeset/*.md files documenting package feat, fix, and breaking changes for release.'

Add an explicit trigger clause: 'Use when creating changesets, documenting package changes for release, or updating the Plate UI registry changelog.'

Drop the 'Command:' prefix and lead with a third-person capability verb so the description reads as a capability statement.

DimensionReasoningScore

Specificity

The description 'Command: changeset' names the concrete domain artifact but provides no action verbs describing capabilities, matching the 'names the domain but actions are minimal' anchor rather than the pure-abstraction score 1.

2 / 5

Completeness

It offers a vague 'what' (just the noun 'changeset') and no 'when' / 'Use when...' clause, matching the 'vague what and no when' anchor; the missing trigger guidance also caps this dimension.

2 / 5

Trigger Term Quality

Only the technical term 'changeset' appears; natural user phrases like 'write a changeset', 'document changes', or 'release notes' are absent, fitting the 'one or two generic/technical keywords' anchor.

2 / 5

Distinctiveness Conflict Risk

'changeset' is a fairly niche term with low overlap risk, but the description supplies no trigger context to disambiguate, leaving it at 'somewhat specific but could still overlap'.

3 / 5

Total

9

/

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

description_field

'description' is very short (18 chars), consider making it more detailed

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

13

/

16

Passed

Repository
udecode/plate
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.