app-store-changelog
Generate user-facing App Store release notes from git history since the last tag.
66
80%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/app-store-changelog/SKILL.mdQuality
Discovery
82%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 its purpose and uses natural trigger terms. Its main weakness is the absence 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 for release notes, App Store changelog, or wants to summarize changes since the last release tag.'
| Dimension | Reasoning | Score |
|---|---|---|
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 about what it does and how it does it. | 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 the rubric, a missing 'Use when' clause caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Contains strong natural trigger terms: 'App Store', 'release notes', 'git history', 'tag'. These are terms a user would naturally use when requesting this kind of task. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'App Store release notes' and 'git history since the last tag' creates a very specific niche that is unlikely to conflict with other skills like general git tools or generic documentation generators. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%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 are particularly effective, providing concrete translation patterns. Minor weaknesses include some boilerplate content (Limitations section, When to Use) and the absence of referenced bundle files that would strengthen progressive disclosure.
Suggestions
Remove or significantly trim the generic 'Limitations' section — it adds no skill-specific safety constraints 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.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary padding. The 'Limitations' section is boilerplate that doesn't add skill-specific value, and phrases like 'comprehensive, user-facing changelog' in the overview are slightly verbose. The commit-to-bullet examples and workflow are well-justified, but the 'When to Use' section restates what's obvious from the title. | 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 without ambiguity. | 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 constitutes a proper feedback loop for a non-destructive text 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, so we can't verify they exist. The skill keeps content inline at a reasonable length (~60 lines of meaningful content), but the guidelines reference could contain important filtering rules that would benefit from being available. | 2 / 3 |
Total | 10 / 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
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
4cc48db
- 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.