CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-add-component

[Skill] Add a new component to Azure Linux. Use when importing packages from Fedora, creating comp.toml files, choosing inline vs dedicated definitions, or setting up a new component with overlays. Triggers: add component, new package, import from fedora, create comp.toml.

79

Quality

100%

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

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.

The skill body is concise, highly actionable, and presents a well-sequenced workflow with explicit validation checkpoints and guards for risky operations. Progressive disclosure is handled through clearly signaled one-level-deep links to external materials.

DimensionReasoningScore

Conciseness

The body is lean and executable with no padding about concepts Claude already knows (e.g., no 'what is an RPM' filler); every section delivers domain-specific azldev guidance or concrete commands. A few explanatory sentences (e.g. the overlays-vs-fork rationale) earn their place as non-obvious project knowledge.

3 / 3

Actionability

Provides copy-paste-ready executable commands throughout — 'azldev comp prep-sources -p <name> --skip-overlays --force -o ...', 'azldev comp render -p <name>', 'diff -r ...', 'azldev comp build -p <name>' — plus complete TOML examples, matching the score-3 anchor.

3 / 3

Workflow Clarity

Clear end-to-end sequence (inspect spec → decide inline/dedicated → add overlays → render/validate → diff-debug → build → smoke-test) with an explicit 'Validate' checkpoint and feedback loop ('render the spec to verify'), plus a destructive-operation guard requiring explicit user sign-off before forking a spec.

3 / 3

Progressive Disclosure

Content is well-organized into clearly labeled sections (Before You Start, Decision, Spec Sources & Overlays, Validate) with one-level-deep, clearly signaled references to an external instructions file and two sibling skills, rather than a monolithic wall of text.

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.

The description is third-person, concise, and clearly communicates both the capability and its trigger conditions with natural user-facing terms. It is among the strongest patterns in the rubric's good examples.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Add a new component', 'importing packages from Fedora', 'creating comp.toml files', 'choosing inline vs dedicated definitions', and 'setting up a new component with overlays' — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers 'what' ('Add a new component to Azure Linux') and 'when' ('Use when importing packages from Fedora, creating comp.toml files...'), satisfying the score-3 anchor requiring both.

3 / 3

Trigger Term Quality

Provides strong natural-term coverage via both a 'Use when...' clause and an explicit 'Triggers: add component, new package, import from fedora, create comp.toml' list — terms a user would plausibly say.

3 / 3

Distinctiveness Conflict Risk

The Azure Linux / comp.toml / Fedora-import niche is specific and unlikely to fire for unrelated skills; triggers are clearly scoped to component addition.

3 / 3

Total

12

/

12

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: 4 suspicious

Warning

Total

15

/

16

Passed

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.