common-store-changelog

Generate user-facing release notes for the App Store and Google Play from git history (App Store <=4000 chars, Google Play <=500). Use when generating release notes, app store changelog, play store release, or "what's new" text for a mobile app.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%Weight 40%Scale 1-3

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

The content is highly actionable with a clear, validated workflow and well-structured progressive disclosure via a real reference file. The main weakness is conciseness: the character-limit rule is repeated four times and the anchor sections add tokens without proportional value.

Suggestions

State the App Store <=4000 / Google Play <=500 limits once in Always-Apply Rules and reference them elsewhere instead of repeating the numbers in the Workflow, Output Format, and Anti-Patterns sections.

Consider merging or removing the 'Canonical response anchors' and 'Remediation anchors' sections, which restate existing rules ('omit internal SDK changes', 'no jargon', 'three bullets') already covered in Always-Apply Rules and Anti-Patterns.

Consolidate 'Always-Apply Rules' and 'Anti-Patterns' where they overlap (e.g., no-jargon and drop-chore both appear) to reduce duplication.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes competence, but the character limits are restated across Always-Apply Rules, the Workflow, Output Format, and Anti-Patterns, and the 'Canonical response anchors'/'Remediation anchors' sections read as meta scaffolding rather than skill content.	2 / 3
Actionability	Concrete executable guidance throughout: a runnable `git log <last-tag>..HEAD --oneline` command, copy-paste output templates for both stores, and explicit drop/dedup rules — fully actionable.	3 / 3
Workflow Clarity	A clear five-step sequence (Collect → Triage → Draft App Store → Draft Google Play → Validate) includes an explicit validation checkpoint counting characters per store, with error-recovery guidance ('truncate + rewrite if needed') in Anti-Patterns.	3 / 3
Progressive Disclosure	Overview stays inline while commit-to-bullet mapping is split into a real, one-level-deep reference (references/commit_examples.md, verified to exist) that is clearly signaled and load-gated.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%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.

The description is specific, complete, and distinct: it names concrete actions for two app stores, gives explicit character limits, and provides natural 'Use when' triggers. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — generating App Store and Google Play release notes from git history with explicit character constraints (<=4000, <=500) — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly answers both 'what' (generate user-facing release notes for two stores from git history) and 'when' via an explicit 'Use when...' clause, satisfying the top anchor.	3 / 3
Trigger Term Quality	Natural trigger terms users would say are well covered: 'release notes', 'app store changelog', 'play store release', and "what's new" text, matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	A clear niche (mobile store release notes from git history) with store-specific triggers makes conflict with other skills unlikely, matching the distinct-triggers anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 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	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: .github/skills/common/common-store-changelog/SKILL.md
Commit: 9f695e8

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.