run-system-diagnostics

Run ACB (Anypoint Code Builder) system diagnostics to check if the machine meets minimum specifications and apply Windows optimizations if needed

1.84x

Quality

63%

Does it follow best practices?

Impact

98%

1.84x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/mule-development/run-system-diagnostics/SKILL.md

Quality

Content

67%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 body is a well-sequenced, highly actionable procedural skill with strong command coverage and appropriate validation gates. Its main gaps are the missing Linux command set, the absence of explicit retry feedback loops, and minor conciseness redundancy.

Suggestions

Add the Linux gathering commands (e.g. lscpu, free -h, lsblk, nvme / smartctl, ip link) so Step 2 matches the cross-platform intent stated in Step 1.

Introduce explicit validate→fix→retry loops for the IOPS test and Defender exclusion steps so failed runs can be recovered rather than only reported.

Trim the redundant opening sentence (it repeats the frontmatter description) and consolidate the macOS per-command explanations into terser notes.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command lists with brief, useful output-interpretation notes, but the opening line restates the frontmatter description and several asides could be trimmed. Not a 4 because the redundancy and explanatory padding are more than minor.	3 / 5
Actionability	Provides concrete, copy-paste-ready PowerShell, sysctl, and diskspd commands with a complete download block for Windows and macOS. Not a 5 because Linux is named in Step 1 but no Linux gathering commands are given, leaving a coverage gap.	4 / 5
Workflow Clarity	A clear Step 1–5 sequence includes checkpoints (immediate pass/fail table, user permission gates, admin-error handling, download-fail fallback) and validation precedes the system-modifying operations. Not a 5 because there are no explicit validate→fix→retry feedback loops for failed IOPS or exclusion steps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed steps and subsections with clearly signaled asset paths and a download fallback; no nested references. Not a 5 because all detail lives inline in a single ~160-line file with no reference files splitting the lengthy Windows-optimization material.	4 / 5
	Total	15 / 20 Passed

Description

58%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 concrete and reasonably distinctive, naming three specific actions tied to the ACB niche. Its main weakness is the absence of an explicit "Use when..." trigger clause and incomplete coverage of natural synonyms.

Suggestions

Add a "Use when..." clause with concrete triggers, e.g. "Use when setting up or troubleshooting Anypoint Code Builder, checking system requirements, or tuning Windows for ACB performance."

Include natural synonyms users might say, such as "system requirements" and "performance tuning", alongside "minimum specifications" and "optimizations".

Optionally surface the specific optimizations (IOPS benchmarking, Defender exclusions, power plan) so the action list is comprehensive rather than summarized.

Dimension	Reasoning	Score
Specificity	Names three concrete actions — "Run ACB system diagnostics", "check if the machine meets minimum specifications", and "apply Windows optimizations" — matching the several-specific-actions anchor. Not a 5 because it omits the specific optimizations (IOPS, Defender, power plan) and is not comprehensive.	4 / 5
Completeness	The description gives a clear "what" but contains no "Use when..." or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3. Not a 2 because the "what" is concrete, not vague.	3 / 5
Trigger Term Quality	Relevant keywords appear ("system diagnostics", "minimum specifications", "Windows optimizations", "ACB") but common natural synonyms such as "system requirements" or "performance tuning" are missing. Not a 4 because keyword coverage is incomplete rather than merely short a few terms.	3 / 5
Distinctiveness Conflict Risk	The ACB/Anypoint Code Builder niche makes it mostly distinct with only minor overlap risk against generic system-diagnostic skills. Not a 5 because "system diagnostics" and "Windows optimizations" could still trigger for unrelated diagnostic requests.	4 / 5
	Total	14 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: mulesoft/mulesoft-dx
Path: skills/mule-development/run-system-diagnostics/SKILL.md
Commit: af20367

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.