CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-notes

Use this skill when the user asks about release dates, release owners, rollout status, or launch checklist details.

Quality

76%

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 ./examples/skilltoolactivation/skills/release-notes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary lean, well-organized lookup skill: a concrete tool call, a single clear workflow, and an explicit fallback for missing information, with no wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean — one intro line plus three numbered steps with no padding and no explanation of concepts Claude already knows — so every token earns its place, matching the score-5 anchor.

5 / 5

Actionability

It names a concrete tool (`release_docs_read_file`) and a concrete file (`release_notes.md`) with an explicit not-found fallback, but it stops short of showing the exact call syntax, fitting the score-4 anchor of mostly executable guidance with minor gaps.

4 / 5

Workflow Clarity

The three-step sequence is clear and unambiguous with an explicit error-recovery path (step 3); the simple-skill exception applies since this is a read-only lookup with no destructive or batch operation to cap the score.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (release_notes.md is data read by the tool, not a bundle file), and is well-organized with a heading and numbered steps, so the simple-skill exception yields a score of 5.

5 / 5

Total

19

/

20

Passed

Description

47%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 has strong, natural trigger phrases and a distinct niche, but it omits any statement of what the skill actually does and describes no concrete actions, leaving both the 'what' and capability specifics underspecified.

Suggestions

Add a 'what' clause stating the skill's action, e.g. 'Looks up and answers questions from the release notes' before the 'Use when...' trigger clause, to satisfy both halves of completeness.

Include the term 'release notes' itself (and a synonym like 'changelog' or 'deployment notes') among the trigger phrases so the skill's own name and common variations are covered.

Lead with a concrete action verb (e.g. 'Looks up', 'Retrieves') rather than only describing when the user asks, to raise specificity from naming the domain to naming the action.

DimensionReasoningScore

Specificity

Names the domain with four concrete topics (release dates, release owners, rollout status, launch checklist details) but describes no actions at all — 'asks about' is the user's action, not the skill's, matching the score-2 anchor of naming a domain with minimal/generic actions.

2 / 5

Completeness

It provides a strong explicit 'when' (four concrete triggers) but no 'what' — it never states what the skill does, which matches the score-2 anchor 'only when is present without what' rather than the score-3 anchor (clear what, weak when).

2 / 5

Trigger Term Quality

Phrases like 'release dates', 'release owners', 'rollout status', and 'launch checklist details' are natural user language with good coverage, but it omits the term 'release notes' (the skill's own name) and synonyms like 'changelog' or 'deployment', so it falls short of the comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The release/launch niche with its specific triggers is mostly distinct with minimal conflict risk, though the missing 'release notes' term leaves minor overlap risk with a generic deployment or project-status skill, fitting the score-4 anchor.

4 / 5

Total

12

/

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

trpc-group/trpc-agent-go

Path

examples/skilltoolactivation/skills/release-notes/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.