CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-remove-component

[Skill] Remove components from Azure Linux. Use when deleting packages, cleaning up unused dependencies, or pruning the distro. Triggers: remove component, delete package, drop component, prune dependency.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable runbook for removing Azure Linux components: real commands, exact paths, a numbered workflow, and an explicit verification section with expected outputs. It assumes Claude's competence and avoids concept explanations while flagging the real gotchas (reverse deps, manual-release bumps, component- vs binary-scoped publishing).

DimensionReasoningScore

Conciseness

Lean runbook with no padding about concepts Claude already knows; every command, path, and note earns its place (e.g., 'There is no azldev command for this — manual deletion is the only way').

3 / 3

Actionability

Fully executable commands with exact paths throughout (azldev comp list, grep 'srpm: <name>', rm locks/<name>.lock, azldev comp render -a --clean-stale), copy-paste ready with only a clearly-marked <name> parameter.

3 / 3

Workflow Clarity

Clear sequenced process (Before You Start -> Steps 1-5 -> Verify) with explicit validation checkpoints and expected outputs ('should fail with component not found', 'should return nothing'), plus a reverse-dependency pre-check for this destructive batch operation.

3 / 3

Progressive Disclosure

A single-task, self-contained runbook with no external references and no nested lookups; well-organized into clearly headed sections, which the rubric's simple-skill carve-out allows to score 3.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A focused, well-constructed description that clearly states the capability, gives explicit 'Use when' trigger guidance with natural verb variants, and is scoped tightly enough to avoid conflicts. The leading '[Skill]' tag is a minor cosmetic artifact but does not weaken the substance.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — removing components, deleting packages, cleaning unused dependencies, and pruning the distro — rather than vague language.

3 / 3

Completeness

Explicitly answers what ('Remove components from Azure Linux') and when (an explicit 'Use when...' clause plus a Triggers list), satisfying both halves.

3 / 3

Trigger Term Quality

Provides natural verb variations a user would actually say ('remove component', 'delete package', 'drop component', 'prune dependency') in both the 'Use when' clause and an explicit Triggers list.

3 / 3

Distinctiveness Conflict Risk

Scoped to Azure Linux with distinct component-removal triggers, giving it a clear niche unlikely to collide with unrelated skills.

3 / 3

Total

12

/

12

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
microsoft/azurelinux
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.