ubuntu-review-sru

Review an Ubuntu Stable Release Update (SRU) and produce a report with a recommendation.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./groups/ubuntu-engineering/skills/ubuntu-review-sru/SKILL.md

Quality

Content

71%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 content is a well-sequenced, mostly executable workflow with per-step validation criteria and a concrete report template. Its main weaknesses are the missing checks.md bundle file (which breaks progressive disclosure and leaves the actual SRU checks undefined) and the absence of explicit error-recovery feedback loops.

Suggestions

Provide the referenced checks.md file (or inline the SRU check definitions) so the skill can actually perform its core checking function rather than deferring to a missing file.

Add explicit feedback loops for failure cases, e.g. what to do when a referenced Launchpad bug is not public or when a check fails mid-review.

Tighten minor filler such as "Be meticulous." to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with brief persona, prerequisites, and a sequenced workflow; only minor trimmable filler like "Be meticulous" exists, and the 21-row report template is justified as the required output format rather than padding.	4 / 5
Actionability	Provides concrete executable commands (git ubuntu clone, git ubuntu queue sync), specific URL/format guidance, and a copy-paste report template, with the main gap being that step 3 defers all check detail to a checks.md file that is not present in the bundle.	4 / 5
Workflow Clarity	A clear 5-step sequence with explicit per-step success criteria as checkpoints and a 21-item checklist in the report, but it lacks explicit error-recovery feedback loops (e.g. what to do when a referenced bug is not public) which keeps it below 5.	4 / 5
Progressive Disclosure	The body has reasonable section structure and a clearly-signaled one-level reference to checks.md, but that referenced file does not exist in the bundle, so the core detailed check content is neither inlined nor reachable, leaving the disclosure incomplete.	3 / 5
	Total	15 / 20 Passed

Description

65%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 is distinctive and names a concrete domain and actions, but it lacks any explicit "Use when..." trigger guidance, which caps completeness. Trigger term quality is good but could add common synonyms.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill, e.g. 'Use when reviewing an Ubuntu Stable Release Update (SRU) upload or when the user asks to review a stable update for an Ubuntu package.'

Broaden trigger terms with synonyms users might say such as 'stable update', 'regression update', or 'sru upload' to improve trigger recall.

Dimension	Reasoning	Score
Specificity	Names the domain ("Ubuntu Stable Release Update (SRU)") and two concrete actions ("Review" and "produce a report with a recommendation"), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The "what" is clear but there is no "Use when..." clause or equivalent trigger guidance; per the judging guidelines a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural domain terms a user would say ("Ubuntu", "SRU", "Stable Release Update", "review", "report") with good coverage, though a few common variations like "stable update" or "regression update" are missing.	4 / 5
Distinctiveness Conflict Risk	"Ubuntu Stable Release Update (SRU)" is a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	15 / 20 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: canonical/copilot-collections
Path: groups/ubuntu-engineering/skills/ubuntu-review-sru/SKILL.md
Commit: e75d6ec

Reviewed: 1 day 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.