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.
82
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./execution-skills/skills/release-notes-generator/SKILL.mdQuality
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 a specific multi-step workflow, names concrete tools and integrations, and provides explicit timing guidance for when to use it. It covers the full pipeline from source (issue trackers) to destination (Google Drive) with specific intermediate steps, making it both highly informative and easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read completed tickets, filter to user-visible changes, group by product area, write polished release notes, and save as .docx to Google Drive. | 3 / 3 |
Completeness | Clearly answers both 'what' (read tickets, filter, group, write release notes, save to Drive) and 'when' ('Use before each release or on a weekly cadence'), providing explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'release notes', 'Linear', 'Jira', 'GitHub Issues', 'Google Drive', '.docx', 'weekly cadence', and 'release'. These cover the major project management tools and the core task terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: generating user-facing release notes from issue trackers and saving to Google Drive. The combination of specific tools (Linear, Jira, GitHub Issues), output format (.docx), destination (Google Drive), and purpose (release notes) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%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 a clear prompt template and good formatting guidance (title examples, framing rules). Its main weaknesses are the lack of concrete tool invocations (no specific MCP calls for Linear/Jira/GitHub or Google Drive), missing validation checkpoints in the workflow, and some unnecessary motivational framing at the top.
Suggestions
Add concrete MCP tool call examples (e.g., specific Linear/Jira query syntax or Google Drive file creation calls) to make the skill truly executable rather than a prompt template.
Add a validation step between Step 3 and Step 4, such as confirming the number of tickets found, listing skipped items, or presenting a draft summary before generating the .docx.
Remove the opening motivational paragraph ('Writing release notes from raw tickets is tedious...') — Claude doesn't need to be convinced of the skill's value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph ('Writing release notes from raw tickets is tedious...') explains motivation Claude doesn't need. The tips section adds useful but somewhat tangential advice. The core prompt template and setup table are reasonably lean, but the framing could be tightened. | 2 / 3 |
Actionability | The prompt template provides clear filtering criteria, grouping logic, and formatting rules with good/bad examples for titles. However, there's no executable code or concrete MCP tool invocations — it's a natural language prompt template with placeholders rather than specific API calls or commands. The .docx creation step is hand-waved ('Save as .docx'). | 2 / 3 |
Workflow Clarity | The four steps are clearly sequenced and logically ordered. However, there are no validation checkpoints — no step to verify ticket counts, confirm grouping accuracy, or review output before saving. The 'do not publish — save for review only' is a safety note but not a validation loop. For a batch operation producing a deliverable document, a review/confirmation step is missing. | 2 / 3 |
Progressive Disclosure | For a skill with no bundle files, the content is well-organized into distinct sections (prompt template, setup table, placeholders, tips) with clear headers. The structure is flat and easy to navigate. The skill is under 50 lines of substantive content and doesn't need external references. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- amplitude/builder-skills
- Commit
221ffaa
- 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.