CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-fix-overlay

[Skill] Diagnose and fix overlay issues in Azure Linux components. Use when overlays fail to apply, produce unexpected results, or need debugging. Triggers: overlay error, fix overlay, overlay not applying, spec-search-replace failed, overlay debug.

76

Quality

95%

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 skill body: executable commands, a clear diagnosis sequence with validation checkpoints, and per-failure remediation guidance. It respects Claude's competence and uses one-level-deep references appropriately.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: concrete commands and per-failure fixes with no preamble explaining what overlays or specs are, so every token earns its place.

3 / 3

Actionability

It gives fully executable commands (`azldev comp render -p <name>`, `prep-sources`, `diff -r`) and copy-paste-ready fixes per failure type (use `spec-set-tag`, TOML literal strings, multiple single-line replacements).

3 / 3

Workflow Clarity

The diagnosis workflow is a clear numbered sequence (render/inspect -> diff pre/post -> inspect upstream) with render as the validation checkpoint, plus feedback loops in the Tips ('Test incrementally', 'verify with prep-sources', 'smoke-test after fixing').

3 / 3

Progressive Disclosure

Content is organized into clearly separated Diagnosis Workflow, Common Failures, and Tips sections, with one-level-deep, clearly signaled references to related skills and external schema docs rather than nesting detail inline.

3 / 3

Total

12

/

12

Passed

Description

90%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-structured description with explicit use-when guidance and natural trigger terms. Its only weakness is that the capability statement is generic ('diagnose and fix') rather than enumerating concrete overlay-fixing actions.

Suggestions

Replace the generic 'Diagnose and fix overlay issues' with specific concrete actions, e.g. 'Render overlays, diff pre/post sources, and resolve spec-add-tag, spec-search-replace, and file-* failures in Azure Linux components.'

DimensionReasoningScore

Specificity

It names the domain ('overlay issues in Azure Linux components') and two actions ('Diagnose and fix'), but stops at two generic verbs rather than listing multiple specific concrete actions like the 3-anchor example.

2 / 3

Completeness

It states what it does ('Diagnose and fix overlay issues') and gives an explicit 'Use when...' clause plus a Triggers list, clearly answering both what and when.

3 / 3

Trigger Term Quality

The explicit 'Triggers: overlay error, fix overlay, overlay not applying, spec-search-replace failed, overlay debug' gives good coverage of natural phrases a user would actually say, including a concrete failure string.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow (overlay issues in Azure Linux components) with specific triggers like 'spec-search-replace failed', making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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: 5 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.