app-store-changelog
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 strong skill description that clearly defines what the skill does (generates App Store release notes from git history), when to use it (with explicit trigger scenarios), and uses natural language terms users would actually say. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'collecting and summarizing all user-impacting changes', 'since the last git tag (or a specified ref)', and specifies the output format as 'App Store release notes'. These are concrete, well-defined actions. | 3 / 3 |
Completeness | Clearly answers both 'what' (create App Store release notes by collecting and summarizing user-impacting changes since last git tag) and 'when' (explicit 'Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'release notes', 'App Store', 'What's New', 'changelog', 'git history', 'git tag'. These cover multiple natural phrasings a user might employ. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: App Store release notes from git history/tags. The combination of App Store context, git tags, and user-facing changelog makes it unlikely to conflict with generic git or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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-crafted skill that is concise, actionable, and clearly structured. The commit-to-bullet examples table is particularly effective at teaching the translation pattern without over-explaining. The workflow is logically sequenced with appropriate validation, and external resources are cleanly referenced.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place. No unnecessary explanations of what git tags are, what App Store notes are, or how changelogs work. The examples serve a clear purpose (showing the commit-to-bullet translation) and aren't padded. | 3 / 3 |
Actionability | Provides concrete commands (`scripts/collect_release_changes.sh v1.2.3 HEAD`), specific examples of commit-to-bullet translations in a table, a complete example output, and clear filtering criteria (what to drop vs. keep). Claude can execute this workflow directly. | 3 / 3 |
Workflow Clarity | Four clearly sequenced steps with an explicit validation step (Step 4) that includes checking for duplicates, verifying bullets map to real changes, and asking for clarification on ambiguous items. This is a non-destructive workflow, so the validation is appropriately scoped. | 3 / 3 |
Progressive Disclosure | The skill is well-structured with a concise overview, clear workflow steps, examples inline where needed, and one-level-deep references to external resources (`scripts/collect_release_changes.sh` and `references/release-notes-guidelines.md`). Content is appropriately split. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dimillian/Skills
- Commit
05ba982
- 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.