common-store-changelog
Generate user-facing release notes for the Apple App Store and Google Play Store by collecting git history, triaging user-impacting changes, and drafting store-compliant changelogs. Enforces character limits (App Store ≤4000, Google Play ≤500), tone, and bullet format. Use when generating release notes, app store changelog, play store release, what's new, or version release notes for any mobile app.
76
96%
Does it follow best practices?
Impact
—
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 an excellent skill description that clearly articulates specific capabilities (git history collection, change triage, store-compliant drafting with exact character limits), uses natural trigger terms users would actually say, and includes an explicit 'Use when...' clause with comprehensive trigger phrases. The description is concise yet thorough, and its focus on App Store/Play Store release notes makes it highly distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: collecting git history, triaging user-impacting changes, drafting store-compliant changelogs, enforcing character limits with exact numbers, tone, and bullet format. | 3 / 3 |
Completeness | Clearly answers both what (generate release notes by collecting git history, triaging changes, drafting changelogs with specific constraints) and when (explicit 'Use when...' clause with multiple trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'release notes', 'app store changelog', 'play store release', 'what's new', 'version release notes', 'mobile app', plus platform-specific terms like 'Apple App Store' and 'Google Play Store'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining mobile app stores, release notes, specific character limits, and store compliance. Unlikely to conflict with generic changelog or git history skills due to the app store specificity. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted skill that provides clear, actionable guidance for generating store-compliant release notes. The workflow is well-sequenced with validation steps, the output templates are concrete and ready to use, and the anti-patterns section effectively prevents common mistakes. The only weakness is the reference to a bundle file (references/commit_examples.md) that doesn't exist, which slightly undermines progressive disclosure.
Suggestions
Create the referenced `references/commit_examples.md` file with concrete commit-to-bullet mapping examples, or remove the reference if the bundle won't include it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what git is, what app stores are, or how changelogs work. Rules are stated as direct imperatives with concrete examples ('Faster checkout' not 'refactored cart service'). | 3 / 3 |
Actionability | Provides specific git commands, concrete output templates with exact formatting, explicit character limits, clear categorization labels (New/Improved/Fixed), and anti-pattern examples showing what to drop and why. The output format sections are copy-paste ready. | 3 / 3 |
Workflow Clarity | Five clearly sequenced steps (Collect → Triage → Draft App Store → Draft Play Store → Validate) with an explicit validation checkpoint at step 5 that includes character counting and commit traceability. The anti-patterns section adds a feedback loop for character overrun ('truncate + rewrite if needed'). | 3 / 3 |
Progressive Disclosure | References a supporting file (references/commit_examples.md) which is well-signaled and one level deep, but the bundle confirms no such file exists. The skill is otherwise well-structured with clear sections, but the broken reference reduces the score. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
3df717f
- 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.