CtrlK
BlogDocsLog inGet started
Tessl Logo

draft-release-notes

Takes a structured list of changes from changelog-scan and produces a clean, categorized, user-facing release notes draft. Follows project voice and conventions. Never publishes — only proposes a draft file or section.

66

Quality

80%

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 ./starters/changelog-drafter/.grok/skills/draft-release-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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 lean, actionable, and well-organized with a concrete copy-paste template and clear escalation checkpoints; the only minor gap is that explicit validate-then-proceed feedback loops are implied rather than spelled out.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — 'Be concise and scannable. One line per item when possible' and the copy-paste markdown template earn their place with no concept explanations or padding, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Concrete executable guidance is provided throughout: an exact output path 'RELEASE_NOTES_DRAFT.md', a copy-paste markdown template with named sections, and specific rules ('One line per item ... with link to PR', 'Always call out breaking changes ... at the top'), fitting the fully-executable 5-anchor for an instruction-only skill.

5 / 5

Workflow Clarity

A clear sequence (inputs → write draft → escalate → update state) is present with checkpoint-like escalation triggers ('More than ~40 items', 'Any breaking or security item', 'human review needed first'), but explicit validate-then-proceed feedback loops are only implied, matching the 4-anchor's 'most checkpoints present; minor validation gaps' rather than the explicit-loop 5-anchor.

4 / 5

Progressive Disclosure

This is a self-contained simple skill (~55 lines) with clear section headers (Inputs, Output, Rules, When to Escalate) and no need for external references; per the simple-skill note well-organized sections warrant a 5, and no bundle files exist to verify against.

5 / 5

Total

19

/

20

Passed

Description

66%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 specific and third-person with a clear niche and good trigger terms, but it omits an explicit 'Use when...' trigger clause, which caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when drafting release notes from a scanned changelog or when preparing user-facing changelog entries.'

Broaden trigger terms with synonyms users naturally say, such as 'changelog entry', 'version notes', or 'what's new', beyond the tool-specific 'changelog-scan'.

Consider splitting the single long action into a short comma-separated action list (take changes, categorize, draft, propose) to lift specificity toward the 5-anchor.

DimensionReasoningScore

Specificity

Quotes 'produces a clean, categorized, user-facing release notes draft' and 'only proposes a draft file or section' name the domain plus several concrete actions (categorize, draft, propose), with only minor coverage gaps, fitting the 'several specific actions' anchor above the 3-anchor's 1-2 actions.

4 / 5

Completeness

The 'what' is clear (produce a categorized release-notes draft) but there is no explicit 'Use when...' trigger clause; per guidelines a missing trigger clause caps completeness at 3, and the 4-anchor requires both an explicit 'what' and 'when'.

3 / 5

Trigger Term Quality

Natural terms 'release notes', 'changelog', and 'draft' appear, but 'changelog-scan' is tool-specific jargon and common synonyms like 'changelog entry' are missing, matching 'good keyword coverage; a few natural terms missing' rather than the comprehensive 5-anchor.

4 / 5

Distinctiveness Conflict Risk

The 'draft-release-notes' niche with a named upstream consumer (changelog-scan) is mostly distinct with only minor overlap risk against general writing/changelog skills, fitting the 4-anchor better than the fully-distinct 5-anchor.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
cobusgreyling/loop-engineering
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.