CtrlK
BlogDocsLog inGet started
Tessl Logo

ubuntu-review-final-freeze

Review an Ubuntu Final Freeze exception request filed as a Launchpad bug for compliance with the Release Team process, and produce a report with a recommendation.

56

Quality

65%

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 ./groups/ubuntu-engineering/skills/ubuntu-review-final-freeze/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-sequenced, actionable workflow with explicit per-step validation checkpoints and a concrete report template, but it delegates its central checks to a checks.md file that is absent from the bundle, undermining progressive disclosure.

Suggestions

Provide the referenced checks.md bundle file (or inline the common and Final Freeze checks) so the core content is actually reachable.

Trim the editorial framing in the Persona section ('Be objective and relentless...') to tighten conciseness toward the lean anchor.

Verify every bundled reference path resolves (checks.md is currently a dead link) and list real bundle files in references/ if used.

DimensionReasoningScore

Conciseness

The body is largely efficient with concrete tool lists and a compact report template, with only minor editorial padding such as 'Be objective and relentless: a freeze exception is an exception, not the default' that could be trimmed.

4 / 5

Actionability

It gives real executable commands (pull-lp-source, dget, seeded-in-ubuntu) and a complete PASS/FAIL/N/A report template, but the core check definitions are delegated to checks.md rather than being self-contained, a minor gap.

4 / 5

Workflow Clarity

Five numbered steps are clearly sequenced, each ending in an explicit '*Criterion:' validation checkpoint, with a PII-sanitization gate (step 4) and a NEEDS-INFO feedback path, matching the checklist-with-checkpoints anchor.

5 / 5

Progressive Disclosure

Sections are well organized, but the critical detailed content is pointed at [checks.md](checks.md), a reference file that does not exist in the bundle, so the promised one-level-deep navigation is broken.

3 / 5

Total

16

/

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 is specific to its Ubuntu release-team niche and clearly states what it does, but it omits an explicit 'Use when...' trigger clause and broader synonym coverage, leaving the trigger and completeness dimensions at the middle anchor.

Suggestions

Add an explicit 'Use when...' clause naming the natural trigger phrases (e.g. 'Use when reviewing an Ubuntu Final Freeze exception request filed as a Launchpad bug').

Include common synonyms/variations users might say, such as 'freeze exception', 'FFe review', or 'milestone freeze exception'.

Optionally surface the concrete actions the report performs (verify checks, sanitize PII, emit APPROVE/REJECT/NEEDS-INFO) to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Ubuntu Final Freeze exception request filed as a Launchpad bug', 'Release Team process') and two concrete actions ('Review ... for compliance' and 'produce a report with a recommendation'), but coverage is not comprehensive beyond those two actions.

3 / 5

Completeness

The 'what' is clear (review a freeze-exception request and produce a recommendation report), but the 'when' is only weakly implied with no explicit 'Use when...' clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

It uses relevant niche terms a release-team user would say ('Final Freeze exception', 'Launchpad bug', 'Release Team process'), but lacks common variations/synonyms and any explicit 'Use when...' trigger phrase.

3 / 5

Distinctiveness Conflict Risk

'Final Freeze exception' carves a clear niche distinct from generic review skills, with only minor overlap risk against the sibling ubuntu-review-ffe / ubuntu-review-uife skills referenced in the body.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
canonical/copilot-collections
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.