CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

app-store-changelog

Generate user-facing App Store release notes from git history since the last tag.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/app-store-changelog/SKILL.md

The canonical home for this skill is app-store-changelog in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

The body is a well-structured, executable workflow: concrete commands, an excellent commit-to-bullet translation table, an explicit validation step, and clean one-level-deep offloading of detail into a real script and reference file. Its only weaknesses are slight redundancy (Overview/Resources restating known information) and no explicit error-recovery feedback loop in the workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of git or App Store basics, and the workflow steps are one-line directives. Minor redundancy keeps it below anchor 5: the Overview restates the frontmatter description almost verbatim, and the Resources section re-describes what the workflow already says about the script.

4 / 5

Actionability

Guidance is fully executable: the exact command with arguments ('scripts/collect_release_changes.sh v1.2.3 HEAD') is copy-paste ready and the referenced script exists, while the commit-to-bullet example table and the example output block concretely cover the common cases. It does not drop to 4 because no key execution detail is missing.

5 / 5

Workflow Clarity

A clear four-step sequence (collect, triage, draft, validate) with an explicit validation step ('Ensure every bullet maps back to a real change', 'Check for duplicates') and an ask-for-clarification checkpoint, plus the referenced QA checklist. It is not 5 because there is no explicit error-recovery feedback loop (e.g., what to do when the script fails or the range is wrong) beyond the noted no-tags fallback.

4 / 5

Progressive Disclosure

The body is a concise overview with well-signaled, one-level-deep references — 'scripts/collect_release_changes.sh' and 'references/release-notes-guidelines.md' both exist, are listed in a Resources section, and carry the detailed language/filtering/QA rules while the body keeps only the workflow. Content is appropriately split and easy to navigate.

5 / 5

Total

18

/

20

Passed

Description

61%Weight 40%Scale 1-5

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 states a concrete, specific capability in third person with strong domain keywords, but it omits any explicit 'when to use' trigger clause, which both caps completeness and leaves common synonyms ('What's New', 'changelog') unused. It is clearly distinct and avoids vagueness or over-claiming.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for App Store "What's New" text, release notes, or a changelog from git history.'

Include common synonyms users actually say — 'What's New', 'changelog', 'version notes' — to broaden trigger coverage from anchor-4 to anchor-5.

Optionally name a second concrete action (e.g., 'group commits by theme and drop internal-only work') to raise specificity from one action to several.

DimensionReasoningScore

Specificity

The description names the domain ('App Store release notes', 'git history since the last tag') and one concrete action ('Generate'), matching anchor 3 ('Names domain and 1-2 concrete actions, but not comprehensive'). It does not list several specific actions like the anchor-4 example ('Extracts text, fills forms, converts pages'), so it falls below that level.

3 / 5

Completeness

The 'what' is clear ('Generate user-facing App Store release notes from git history since the last tag'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

'App Store', 'release notes', 'git history', and 'tag' are natural phrases a user would say when needing this skill, giving good keyword coverage. Common synonyms like 'What's New' and 'changelog' are missing, which keeps it below the comprehensive anchor-5 coverage.

4 / 5

Distinctiveness Conflict Risk

The niche ('App Store release notes' specifically) is distinct with minimal conflict against unrelated skills. It is not a 5 because a closely related generic 'generate changelog / commit messages from git history' skill could plausibly overlap, and no explicit 'when' triggers sharpen the boundary.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/app-store-changelog/SKILL.md

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.