CtrlK
BlogDocsLog inGet started
Tessl Logo

ubuntu-create-autopkgtest

Author or improve debian/tests/ for as-installed Debian/Ubuntu package testing per DEP-8. Detects package shape (library, daemon, CLI tool, data), proposes the minimal Restrictions set, and produces a draft debian/tests/control plus test scripts for the maintainer to run. Advisory only — does not run tests.

64

Quality

75%

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

Quality

Content

75%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 well-organized, actionable, and respects Claude's intelligence without padding, with a clear gated workflow and bail-out structure. The main gap is the absence of a complete example test script that maintainer guidance could be benchmarked against.

Suggestions

Add one fully copy-paste-ready example test script (e.g. a complete `debian/tests/cli-version` bash file) so the authoring guidelines have a concrete model to follow.

Tighten the Persona & Role prose to the essential constraints to recover a few tokens.

Consider moving the autodep8 Testsuite table into a short reference file if the skill grows, keeping SKILL.md as the overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient — it avoids explaining basic Debian/packaging concepts and uses compact tables for restrictions and Testsuite values — but the persona/role prose and a few explanatory sentences could be trimmed further.

4 / 5

Actionability

Concrete guidance is present throughout — specific restriction names, Testsuite values, `set -euo pipefail`, `cd "$AUTOPKGTEST_TMP"`, `Depends: @`, `autopkgtest <pkg> -- null` — but no complete copy-paste example test script body is provided, leaving a minor gap.

4 / 5

Workflow Clarity

A clear 6-step Process is sequenced with a confirmation gate (step 3) and a structured bail-out report template; because the skill is advisory and never runs tests, run-time validation feedback loops are out of scope, leaving only minor validation gaps.

4 / 5

Progressive Disclosure

The single file is well-structured with clear section headers and tables and no nested references; at ~175 lines all content is inline, which is appropriate for this skill, though a couple of reference tables could optionally be split out.

4 / 5

Total

16

/

20

Passed

Description

75%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, concrete, and occupies a well-defined niche, but it states only what the skill does and never explicitly when a user should invoke it. Adding an explicit 'Use when...' clause with the 'autopkgtest' trigger term would lift the two weakest dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks to add or improve as-installed (DEP-8 / autopkgtest) tests for a Debian or Ubuntu package.'

Include the natural keyword 'autopkgtest' alongside 'DEP-8' since that is the tool name users most often say.

Keep the concrete action list but ensure the trigger guidance is as explicit as the capability list so 'what' and 'when' are both answered.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Author or improve debian/tests/', 'Detects package shape (library, daemon, CLI tool, data)', 'proposes the minimal Restrictions set', 'produces a draft debian/tests/control plus test scripts' — giving comprehensive coverage rather than vague abstraction.

5 / 5

Completeness

The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural-term coverage ('debian/tests', 'DEP-8', 'Debian/Ubuntu package testing', 'Restrictions', 'debian/tests/control'), but the most common tool name 'autopkgtest' is absent, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

It targets a clear, narrow niche (as-installed DEP-8 testing for Debian/Ubuntu packages) with distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.