CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openmeld-changelog

Use when deciding whether an OpenMeld change needs a Changelog entry, writing or publishing an entry, preparing release notes, validating Changelog projections, or historically backfilling missing changes.

Quality

83%

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

75%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 deliberately minimal thin-adapter stub that is maximally token-efficient and clearly signals its single one-level-deep delegation. Its weakness is that all substantive guidance lives in an external file that is not part of this bundle and could not be verified, leaving no fallback and making the skill a pure pointer rather than a self-contained guide.

Suggestions

Add a brief fallback line (e.g., where to find the canonical file relative to the repository root, or what to do if it is absent) so the skill does not dead-end when the referenced path cannot be resolved.

Include a one- or two-line summary of the canonical workflow's core rules (entry format, when an entry is required, how to publish) so the skill degrades gracefully and remains minimally actionable without the external file.

State the path-resolution convention explicitly (that `.agents/skills/openmeld-changelog/SKILL.md` is relative to the repository root, not the skill directory) to remove ambiguity for agents reading this adapter.

DimensionReasoningScore

Conciseness

The body is three lean sentences — "Read and follow `.agents/skills/openmeld-changelog/SKILL.md`. It is the cross-agent source of truth for this workflow. Do not copy or reinterpret its rules here." — with zero padding and no explanation of concepts Claude already knows; even the guardrail sentence earns its place by preventing rule-drift. This matches the anchor 'Lean and efficient; assumes Claude's competence; every token earns its place', and there is nothing to trim that would justify a 4.

5 / 5

Actionability

The single instruction is concrete (an exact file path, better than the high-level hints of a 2), but the file contains none of the actual domain guidance — writing, publishing, validating, and backfilling entries are entirely delegated to a file that is not part of this bundle and whose existence could not be verified. This fits 'Some concrete guidance but incomplete... missing key details'; the gap is the whole substance of the workflow, not the 'minor gaps' required for a 4.

3 / 5

Workflow Clarity

As a single-purpose skill the one action ("Read and follow `.agents/skills/openmeld-changelog/SKILL.md`") is unambiguous, which per the simple-skill note supports a high score; however there is no fallback or checkpoint if the canonical file is absent, and the path does not resolve within the bundle. This lands at 'Clear sequence with most checkpoints present; minor validation gaps' rather than 5, since the workflow's success hinges entirely on an unverifiable external dependency with no failure handling.

4 / 5

Progressive Disclosure

Scored against the actual bundle structure: no references/, scripts/, or assets/ exist, and the sole referenced path (`.agents/skills/openmeld-changelog/SKILL.md`) was not found on disk. The reference is clearly signaled ("cross-agent source of truth") and exactly one level deep with nothing inlined, matching 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'. It falls short of 5 because navigation cannot be assured — the pointer target is outside the bundle and unverifiable — but not to 3, since nothing is inlined and the reference is prominently, not bury, signaled.

4 / 5

Total

16

/

20

Passed

Description

83%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: explicit 'Use when' trigger guidance, five concrete lifecycle actions, and tight OpenMeld/Changelog scoping that minimizes conflict risk. Its only weaknesses are a 'what' that is conveyed solely through the when-clause rather than stated declaratively, and a few missing natural synonyms like 'version history' or 'CHANGELOG.md'.

DimensionReasoningScore

Specificity

The description lists five distinct concrete actions — "deciding whether an OpenMeld change needs a Changelog entry", "writing or publishing an entry", "preparing release notes", "validating Changelog projections", "historically backfilling missing changes" — covering the full changelog lifecycle. This matches 'Lists multiple specific concrete actions; comprehensive coverage'; a 4 would require minor coverage gaps, and none are evident for this domain.

5 / 5

Completeness

The 'when' is explicitly and richly answered via "Use when deciding whether... writing or publishing... preparing release notes... validating... or historically backfilling", and the gerund actions convey the 'what'. However, no independent statement of what the skill does exists — the capability must be inferred from the trigger list, so it does not meet the 5 anchor's requirement that both be 'clearly and explicitly' answered, while the 'what' is far more than weakly implied (the 3 anchor).

4 / 5

Trigger Term Quality

Natural user phrases like "Changelog entry", "release notes", and "backfilling" are present, giving good keyword coverage. It falls short of the 5 anchor because common synonyms and variations (e.g., "CHANGELOG.md", "version history", "what's new") are absent and "Changelog projections" leans toward internal jargon; it is clearly above a 3, whose bar is only 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Triggers are scoped to "an OpenMeld change", "Changelog entry", and "Changelog projections", giving a clear niche with minimal conflict risk — tighter than the 4 anchor's example of overlapping file-type skills. The only overlap surface is the unqualified "preparing release notes", which could also match a generic release-notes skill, but this is negligible against the project-specific qualifiers.

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

amplifthq/opentag

Path

.claude/skills/openmeld-changelog/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.