CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

generate-release-notes

Generate categorized release notes from any source (GitHub, Linear, Jira, or manual input) with optional publishing

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/generate-release-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 concise delegation stub that points to an authoritative external playbook and a rules file with a clear worker-substitution rule. It is token-efficient and concrete as a redirect, but contains none of the skill's substantive guidance, validation steps, or bundled reference material, capping actionability, workflow clarity, and progressive disclosure.

Suggestions

Inline a minimal quick-start for release-note generation (e.g. one example command or categorized output template) so the skill is useful even if the referenced playbook is unavailable.

Add a validation step before the optional publishing action, since publishing is outward-facing and hard to reverse.

Bundle or summarize the referenced `.agents/rules/cog.md` rules inline so the skill does not depend entirely on an external file that is not part of the bundle.

DimensionReasoningScore

Conciseness

The body is lean with no padding — each line points to a specific file or rule — but it earns its brevity by deferring all substance to an external file rather than teaching, keeping it just below the score-5 anchor.

4 / 5

Actionability

It gives concrete, executable pointers (specific file paths and the `invoke_subagent` mechanism) but delegates the entire actual workflow to an unbundled playbook, leaving key details of how to generate release notes unstated.

3 / 5

Workflow Clarity

A rough sequence is present (read and execute the playbook, then follow cog.md, with a worker-substitution rule), but there are no validation checkpoints and the real steps live in the referenced file, so checkpoints are missing or implicit.

3 / 5

Progressive Disclosure

References to `.claude/skills/generate-release-notes/SKILL.md`, `.agents/rules/cog.md`, and `.agents/agents/<name>.md` are explicitly signaled, but none of these files are bundled and the skill is essentially a one-line redirect to an external authoritative file, so structure is present yet shallow.

3 / 5

Total

13

/

20

Passed

Description

62%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 conveys a clear, distinctive capability with concrete source coverage, but lacks an explicit "Use when..." trigger clause and broader synonym coverage. It is strong on distinctiveness and specificity but capped on completeness by the missing trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for release notes, a changelog, or ship notes."

Include natural synonyms such as "changelog" and "ship notes" alongside "release notes" to improve trigger-term coverage.

Optionally name the publish targets (e.g. GitHub release, Slack) to make the "optional publishing" capability more concrete.

DimensionReasoningScore

Specificity

"Generate categorized release notes from any source (GitHub, Linear, Jira, or manual input) with optional publishing" names the domain plus several concrete capabilities (categorization, multiple named sources, optional publishing), with only minor coverage gaps relative to the score-5 anchor.

4 / 5

Completeness

It clearly states what the skill does (generate categorized release notes from named sources with optional publishing) but provides no "Use when..." or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"release notes" is a natural term users would say and the named sources (GitHub, Linear, Jira) add relevance, but common synonyms like "changelog" or "ship notes" are missing, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

"Generate categorized release notes" is a clear, narrow niche with a distinct trigger phrase and minimal overlap risk with other skills, matching the score-5 anchor for a clear niche.

5 / 5

Total

15

/

20

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

Validation for skill structure

No warnings or errors.

Repository

huytieu/COG-second-brain

Path

.agents/skills/generate-release-notes/SKILL.md

Revision

144c7a3

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill