CtrlK
BlogDocsLog inGet started
Tessl Logo

app-store-changelog

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

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

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./plugins/antigravity-awesome-skills-claude/skills/app-store-changelog/SKILL.md

The canonical home for this skill is app-store-changelog in popey/claude-code-skills

SKILL.md
Quality
Evals
Security

Quality

Content

77%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill with strong actionability and workflow clarity. The commit-to-bullet examples table is particularly effective, and the four-step workflow with validation is well-designed. Minor weaknesses include some boilerplate content that doesn't add value (Limitations, When to Use) and missing bundle files for the referenced resources.

Suggestions

Remove or significantly trim the 'Limitations' section — it's generic boilerplate that doesn't add skill-specific value and wastes tokens.

Provide the referenced bundle files (scripts/collect_release_changes.sh and references/release-notes-guidelines.md) to support the progressive disclosure structure.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary sections like the boilerplate 'Limitations' block and the 'When to Use' section which restates what's obvious from the title. The commit-to-bullet examples and workflow steps earn their place, but the overall content could be tightened.

2 / 3

Actionability

Provides concrete, executable guidance: a specific script to run with arguments, clear commit-to-bullet translation examples with a table, and a complete example output. The workflow steps are specific enough to follow directly.

3 / 3

Workflow Clarity

The four-step workflow is clearly sequenced (collect → triage → draft → validate) with an explicit validation step that includes checking for duplicates, verifying bullets map to real changes, and asking for clarification on ambiguous items. This is a good feedback loop for a content-generation task.

3 / 3

Progressive Disclosure

References to `scripts/collect_release_changes.sh` and `references/release-notes-guidelines.md` are clearly signaled, but no bundle files are provided to back them up. The content is reasonably structured with sections, but the inline examples and output format could potentially be split out for a cleaner overview.

2 / 3

Total

10

/

12

Passed

Description

82%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-crafted, specific description that clearly communicates what the skill does with natural trigger terms. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding trigger guidance would elevate this from good to excellent.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to generate release notes, write App Store changelogs, or summarize changes since the last release tag.'

DimensionReasoningScore

Specificity

The description lists a concrete action ('Generate user-facing App Store release notes') and specifies the data source ('from git history since the last tag'). This is specific and actionable.

3 / 3

Completeness

The 'what' is clearly stated (generate App Store release notes from git history since last tag), but there is no explicit 'Use when...' clause or equivalent trigger guidance. Per rubric, this caps completeness at 2.

2 / 3

Trigger Term Quality

Contains strong natural trigger terms: 'App Store', 'release notes', 'git history', 'tag'. These are terms users would naturally use when requesting this functionality.

3 / 3

Distinctiveness Conflict Risk

This is a very specific niche: App Store release notes from git history. The combination of 'App Store', 'release notes', and 'git history/tag' makes it highly distinctive and unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation — 10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
popey/claude-code-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.