Tessl • The management layer for AI agent skills

The body is an exemplary lean instruction skill: tightly scoped, fully actionable with exact output behavior, and cleanly split from a real one-level-deep reference. Nothing is padded, implicit, or misplaced.

Dimension	Reasoning	Score
Conciseness	The body is nine lean lines with zero concept explanation or padding: 'Review only the release-note text supplied by the user. Do not fetch data, run commands, or change files.' Every sentence instructs, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	For an instruction-only skill the guidance is fully executable: exact scope constraint, the two checks ('names an owner and contains a rollback note'), evidence format ('Quote the supplied text for each finding'), and an exact fallback output ('write "Not provided"'). Per the scoring notes, absence of code is not penalized when guidance is this actionable.	5 / 5
Workflow Clarity	The single action is unambiguous — review supplied text, check two items, quote findings, use the stated fallback — and the skill is explicitly read-only, so no destructive/batch validation cap applies. The simple-skill exception for a single unambiguous action is met; it is not below 5 since nothing in the sequence is implicit.	5 / 5
Progressive Disclosure	The body is a concise overview under 50 lines, and the single reference ('Use the checklist in `references/checklist.md`') is clearly signaled, one level deep, and verified to exist with non-duplicative content ('Return findings only. Do not approve a release.'). Structure matches the well-signaled one-level-deep-references anchor.	5 / 5
	Total	20 / 20 Passed

Description

53%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 clear, concrete task but omits any 'when to use this' guidance, which caps completeness and limits trigger-term quality. It is reasonably distinctive within its niche. Adding an explicit trigger clause with natural user phrasings would raise most dimensions.

Suggestions

Add a 'Use when...' clause with concrete triggers, e.g., 'Use when the user supplies a release note and asks to verify its owner or rollback plan.'

Include natural keyword variations users would say, such as 'release notes', 'changelog entry', 'rollback plan', or 'go-live note', to improve trigger term coverage.

Optionally state the output promise (e.g., 'reports findings with quoted evidence') to sharpen the 'what' toward anchor 4-5 specificity.

Dimension	Reasoning	Score
Specificity	Names the domain ("release note") and two concrete checks ("for its owner and rollback note"), matching the '1-2 concrete actions, but not comprehensive' anchor. It does not list several distinct actions, so it falls short of anchor 4.	3 / 5
Completeness	The 'what' is clear ("Check a supplied release note for its owner and rollback note") but 'when' is entirely absent, which anchor 3 describes and which the guideline explicitly caps at 3.	3 / 5
Trigger Term Quality	"release note", "owner", and "rollback note" are relevant keywords but common variations and synonyms (e.g., "release notes", "changelog", "roll back plan") are absent, matching anchor 3. It is not anchor 4 because keyword coverage is thin and there is no natural trigger phrasing.	3 / 5
Distinctiveness Conflict Risk	The niche is narrow and specific (verifying owner and rollback note in release notes) with only minor overlap risk against broader release-management or QA skills. It is not anchor 5 because it lacks the explicit distinct trigger phrases that anchor-5 examples carry.	4 / 5
	Total	13 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ascending-llc/jarvis-registry
Path: docs/walkthroughs/examples/skills/revision-1/release-notes-check/SKILL.md
Revision: 3987903

Reviewed: 10 days ago

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.

release-notes-check

Table of Contents

Is this your skill?