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.
Install with Tessl CLI
npx tessl i github:Dimillian/Skills --skill app-store-changelog94
Does it follow best practices?
Validation for skill structure
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 well-crafted skill description that excels across all dimensions. It clearly specifies what the skill does (create App Store release notes from git history), includes natural trigger terms users would actually say, and has an explicit 'Use when' clause with multiple trigger scenarios. The App Store + git combination creates a distinctive niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Create user-facing App Store release notes', 'collecting and summarizing all user-impacting changes', 'since the last git tag (or a specified ref)'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag') AND when ('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 natural keywords users would say: 'release notes', 'App Store', 'What's New', 'changelog', 'git history', 'tags'. Good coverage of variations including the specific 'App Store' context and general 'release notes' terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche combining App Store context, release notes, and git-based change collection. The specific combination of 'App Store release notes' + 'git tags/history' creates a distinct trigger profile unlikely to conflict with general documentation or git skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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 excellent conciseness and clear workflow progression. The main weakness is the lack of concrete examples showing input commits transformed into output bullets, which would make the guidance more immediately actionable. The validation step and resource references are strong points.
Suggestions
Add 1-2 concrete examples showing sample commits transformed into App Store bullet points (e.g., 'fix: resolve crash on iOS 17 when opening settings' → 'Fixed a crash that could occur when opening Settings on iOS 17')
Include a brief example of the expected output format with actual sample bullets to make the guidance more copy-paste ready
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, with no unnecessary explanations of concepts Claude already knows. Every section serves a clear purpose without padding or verbose descriptions. | 3 / 3 |
Actionability | Provides concrete script commands and clear workflow steps, but lacks executable examples of the actual output format or sample commit-to-bullet transformations that would make the guidance copy-paste ready. | 2 / 3 |
Workflow Clarity | Clear four-step sequence with explicit validation step (Step 4) that includes checking for duplicates, verifying bullets map to real changes, and asking for clarification on ambiguous items. The workflow is well-structured with appropriate checkpoints. | 3 / 3 |
Progressive Disclosure | Clean overview structure with appropriate references to external resources (script and guidelines file) that are one level deep and clearly signaled. Content is appropriately split between the skill and referenced materials. | 3 / 3 |
Total | 11 / 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.
- 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.