CtrlK
BlogDocsLog inGet started
Tessl Logo

ubuntu-review-ffe

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

58

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

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 skill body is well-structured, concise, and actionable with explicit per-step validation criteria and a concrete report template. Its main weakness is progressive disclosure: the referenced checks.md file is missing, leaving the core check content inaccessible.

Suggestions

Ship the referenced checks.md (containing the common and Feature Freeze checks) alongside SKILL.md so the deferred core content actually exists.

Consider moving the long report template into a reference file (e.g. references/report-template.md) and keeping only the field summary inline, to tighten the overview further.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explanations of what an FFe or Launchpad is); the report template is long but is the actual output spec, with only minor spots that could be trimmed.

4 / 5

Actionability

Concrete executable commands (pull-lp-source, dget, seeded-in-ubuntu, rmadison) and an explicit PASS/FAIL/N/A report template give mostly copy-paste-ready guidance, with minor gaps deferred to checks.md.

4 / 5

Workflow Clarity

A clear 5-step sequence where each step ends with an explicit *Criterion:* validation checkpoint plus a report checklist; no retry/feedback loop, but none is required for a non-destructive review task.

4 / 5

Progressive Disclosure

The body is well sectioned and clearly signals checks.md one level deep, but checks.md is absent from the bundle (no references/scripts/assets and no checks.md at root), so navigation to the core check content is broken.

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 specific to a clear niche and uses strong domain trigger terms, but it omits any explicit "when to use this" guidance, which caps completeness. Adding a trigger clause would lift the completeness and overall score.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing an Ubuntu Feature Freeze exception (FFe) request filed as a Launchpad bug, or when the user mentions an FFe / freeze exception."

Expand the action list slightly (e.g. "verify seed impact, apply the freeze-exception checks, sanitize PII") to push specificity toward 4-5.

DimensionReasoningScore

Specificity

Names the Ubuntu FFe domain plus two concrete actions ("Review... for compliance with the Release Team process" and "produce a report with a recommendation"), matching the 1-2-actions anchor; it does not list a broader set of specific actions needed for a 4.

3 / 5

Completeness

It clearly states what the skill does but has no "Use when..." clause or equivalent trigger guidance; per the judging guidelines, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Strong niche keyword coverage ("Ubuntu Feature Freeze exception (FFe)", "Launchpad bug", "Release Team process") including the natural abbreviation a user would say, with only minor natural variations missing.

4 / 5

Distinctiveness Conflict Risk

Targets a highly specific niche (Ubuntu Feature Freeze exception review) with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

15

/

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.