CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-mock

[Skill] Test and inspect packages in Azure Linux mock chroots. Use when testing built RPMs, inspecting dependencies, debugging runtime issues, or verifying package contents. Triggers: test package, mock shell, inspect rpm, smoke test, chroot, verify build output.

75

Quality

92%

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

85%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 body is highly actionable with executable commands and a well-sequenced interactive workflow, organized into clear sections. The main weakness is redundant repetition of the -p/--add-package semantics across multiple sections.

Suggestions

Consolidate the -p/--add-package explanation into a single location; the Key Flags table, the warning callout, and the Gotchas entry all restate the same semantics.

Add a one-line validation/exit-code check example to the non-interactive heredoc workflow so failed commands surface automatically.

Consider a brief 'Prerequisites' line noting that mock/azldev must be installed, since the commands assume an existing Azure Linux dev environment.

DimensionReasoningScore

Conciseness

The body is mostly lean and command-driven, but the -p/--add-package flag semantics are explained three times (Key Flags table, the warning callout, and Gotchas), which could be tightened. It earns its tokens but includes redundancy rather than being perfectly efficient.

2 / 3

Actionability

Fully executable commands throughout (mock --scrub, heredoc azldev adv mock shell, rpm -qip/-qlp/-qRp, mock --copyin) with specific flags and copy-paste-ready blocks.

3 / 3

Workflow Clarity

The Agent workflow is a clear 6-step sequence with an explicit checkpoint ('Wait for the user to confirm they are in the mock shell') and terminal-selection feedback, distinguishing interactive vs non-interactive approaches with a stated preference.

3 / 3

Progressive Disclosure

No bundle files exist, but the single SKILL.md is well-organized into clearly labeled sections (Resetting, Non-Interactive, Inspect, Interactive, Key Flags, Gotchas) with no nested references, which satisfies the simple-skill allowance.

3 / 3

Total

11

/

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 specific, trigger-rich, and complete, clearly stating both capability and invocation conditions for a distinct niche. The '[Skill]' prefix is minor noise but does not undermine specificity or voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('testing built RPMs, inspecting dependencies, debugging runtime issues, or verifying package contents') in a specific domain, matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what ('Test and inspect packages in Azure Linux mock chroots') and when via an explicit 'Use when...' clause plus a dedicated trigger list, satisfying the top anchor.

3 / 3

Trigger Term Quality

Explicit 'Triggers:' list ('test package, mock shell, inspect rpm, smoke test, chroot, verify build output') provides natural terms a user would actually say, with broad coverage.

3 / 3

Distinctiveness Conflict Risk

The Azure Linux mock chroot niche is specific and tool-bound ('azldev'/'mock'), with distinct triggers unlikely to fire for 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.