CtrlK
BlogDocsLog inGet started
Tessl Logo

app-store-changelog

Generate user-facing App Store release notes from git history since the last tag.

63

Quality

75%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/app-store-changelog/SKILL.md

The canonical home for this skill is app-store-changelog in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, actionable overview with an executable script command, concrete translation examples, a sequenced workflow ending in validation, and well-signaled one-level-deep references that all resolve to real files. The only minor weaknesses are slight section redundancy and a soft rather than hard validation retry loop.

Suggestions

Collapse the small overlap between 'Overview' and 'When to Use' into a single trigger-oriented section to tighten conciseness.

Make the Validate step an explicit feedback loop (e.g. 'if a bullet cannot be mapped to a real change, drop it and re-check for duplicates') to push workflow clarity to 5.

Consider merging the commit-to-bullet examples and the Example Output so each example appears once, reducing redundancy.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence (no explaining git or the App Store), and every section earns its place, though the Overview/When-to-Use and Examples/Example Output pairs have minor redundancy.

4 / 5

Actionability

Provides a copy-paste-ready executable command ('scripts/collect_release_changes.sh v1.2.3 HEAD') plus a concrete commit-to-bullet translation table and a full example output covering common cases.

5 / 5

Workflow Clarity

A clear four-step sequence (Collect, Triage, Draft, Validate) with an explicit validation step that checks mappings, duplicates, and asks for clarification; minor gap is the lack of a hard error-recovery retry loop, but the task is non-destructive so no cap applies.

4 / 5

Progressive Disclosure

The body is a well-organized overview that points via a Resources section to one-level-deep, verified bundle files (scripts/collect_release_changes.sh and references/release-notes-guidelines.md), with content appropriately split between the script, the reference, and the overview.

5 / 5

Total

18

/

20

Passed

Description

65%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 concise and distinct with a clear statement of what the skill does, but it lacks an explicit 'when to use' trigger clause and only names a single concrete action. Adding a 'Use when...' clause and one more specific action would raise completeness and specificity.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks for App Store "What's New" text, release notes, or a changelog from git history.'

Name one or two more concrete actions (e.g. 'triage commits for user impact' or 'deduplicate and format bullets') to lift specificity above a single action.

Include natural synonyms like 'What's New' and 'changelog' alongside 'release notes' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('App Store release notes', 'git history since the last tag') and one concrete action ('Generate ... release notes from git history'), but lists only a single action rather than comprehensive coverage.

3 / 5

Completeness

Provides a clear 'what' (generate release notes from git history) but no explicit 'Use when...' trigger clause, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural phrases users would say ('App Store release notes', 'git history') but omits common synonyms like 'What's New' or 'changelog', so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

The 'App Store release notes from git history since the last tag' framing carves out a clear, narrow niche with distinct triggers and minimal overlap risk with other skills.

5 / 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.