release-notes-generator

Read completed tickets from Linear, Jira, or GitHub Issues, filter to user-visible changes, group by product area, and write polished user-facing release notes saved as a .docx to Google Drive. Use before each release or on a weekly cadence.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

The body is actionable, clearly sequenced, and well-organized with concrete examples and edge-case handling. Its lone weakness is a small amount of promotional intro text that redundantly restates the description.

Suggestions

Trim or remove the opening tagline and 'This skill does all of it' paragraph so the body leads directly with the prompt template.

Consider an explicit 'verify the .docx opened and entries are grouped correctly' note in Step 4 to add a lightweight output checkpoint.

Dimension	Reasoning	Score
Conciseness	The prompt template, setup table, placeholders, and tips are lean, but the opening tagline and 'Writing release notes from raw tickets is tedious… This skill does all of it' restate the value prop already covered by the description and could be tightened.	2 / 3
Actionability	Provides a concrete four-step prompt template, explicit title rules with good/bad examples ('Faster search results' vs never 'added/fixed/shipped'), and defined placeholders, giving copy-ready guidance.	3 / 3
Workflow Clarity	A clear Step 1–4 sequence with an explicit edge-case checkpoint ('If no tickets found, say which sources you checked'); the task is non-destructive so the missing-output-validation cap does not apply.	3 / 3
Progressive Disclosure	Self-contained skill with well-organized sections (Prompt Template, Setup, Placeholders, Tips) and no external references needed; no bundle files exist to verify.	3 / 3
	Total	11 / 12 Passed

Description

85%

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 distinctive, clearly stating both capability and when to use it. Its only weakness is trigger-term breadth within the description field itself, since richer natural phrasings are relegated to suggest_when.

Suggestions

Fold one or two natural trigger variations (e.g. 'changelog', 'what shipped this sprint') into the description itself rather than relying solely on suggest_when.

Keep the explicit 'Use before each release or on a weekly cadence' clause — it is what lifts completeness above 2.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — read tickets from Linear/Jira/GitHub Issues, filter to user-visible changes, group by product area, write release notes, and save a .docx to Google Drive — matching the comprehensive-actions anchor.	3 / 3
Completeness	Clearly answers what (read→filter→group→write→save) and when ('Use before each release or on a weekly cadence'), satisfying both halves with explicit trigger guidance.	3 / 3
Trigger Term Quality	'release notes', 'tickets', and 'release' are natural terms, but common variations like 'changelog' or 'what shipped' are absent from the description (they live in the separate suggest_when field the rubric does not evaluate), so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The ticket-to-release-notes-to-.docx-to-Drive niche is specific with distinct triggers, making overlap with other skills unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: amplitude/builder-skills
Commit: 22b0634

Reviewed: 3 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.