CtrlK
BlogDocsLog inGet started
Tessl Logo

computer-health-check

Run a comprehensive, read-only health check on the user's computer and return a scored chat summary with prioritized, plain-English recommendations and safe cleanup suggestions. Use this whenever the user wants to check their computer's health, speed it up, free up / reclaim disk space, find what's eating CPU / memory / storage, check battery health and wear, audit login & startup items, see pending updates, or asks for a "tune-up", "checkup", "system report", "health check", or "is my Mac/PC/laptop healthy". Trigger even on casual phrasing like "my laptop feels slow", "why is my fan so loud", "my computer is laggy", "running out of space", or "clean up my machine". Works on macOS, Windows, and Linux. This is a Desktop Commander skill: it relies on a real local shell (start_process / interact_with_process) and is strictly read-only by default — it never needs sudo and only performs cleanups the user explicitly approves.

89

1.19x
Quality

96%

Does it follow best practices?

Impact

61%

1.19x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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-structured, actionable playbook: a tight multi-step workflow with validation checkpoints, a concrete scoring rubric and report template, and clean one-level-deep progressive disclosure to per-OS reference files. Only minor motivational framing keeps conciseness from a perfect score.

Suggestions

Trim the flavor text in 'What this skill does' and the safety-contract intro (e.g. 'the way a good technician would...', 'This is the part that makes users trust the skill') to tighten conciseness without losing substance.

Consider making the post-cleanup re-check a mandated validation step rather than 'a nice confirmation' to strengthen the feedback loop for batch/destructive operations.

Add a one-line note clarifying how to handle a platform the OS-detection step cannot identify (neither macOS, Windows, nor Linux) to close a small gap in workflow coverage.

DimensionReasoningScore

Conciseness

Largely efficient and substantive — scoring rubric, report template, and recommendation rules all earn their tokens — with only minor color that could be trimmed such as 'the way a good technician would: look first, explain plainly, fix only with permission' and 'This is the part that makes users trust the skill, so honor it strictly'.

4 / 5

Actionability

Provides copy-paste-ready guidance: an exact chat report template, a concrete scoring table with numeric thresholds, OS-detection commands, and specific recommendation mappings, with executable collection and cleanup scripts delegated to the platform reference files.

5 / 5

Workflow Clarity

Five clearly sequenced steps (detect OS → collect → score → report → suggest cleanups) with explicit validation checkpoints: the read-only safety contract, per-command error tolerance ('If a single command errors, continue'), and an approval gate before any cleanup with a suggested post-cleanup re-check.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that splits platform-specific commands into three one-level-deep reference files (references/macos.md, windows.md, linux.md), each real and explicitly signaled with 'Read only the one that matches', giving easy navigation with no nested-reference chaining.

5 / 5

Total

19

/

20

Passed

Description

100%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 a strong, complete trigger spec: it states concrete capabilities, gives exhaustive natural-language triggers including casual phrasing and platform synonyms, and bounds the skill's scope clearly. It uses third-person/imperative voice throughout with no vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and coverage areas — 'run a comprehensive, read-only health check', 'return a scored chat summary', 'prioritized, plain-English recommendations and safe cleanup suggestions', plus battery, startup, updates, and disk space — giving comprehensive coverage rather than a single vague action.

5 / 5

Completeness

Explicitly answers both 'what' (read-only health check returning a scored summary with recommendations) and 'when' ('Use this whenever the user wants to...' followed by concrete trigger phrases and casual phrasing examples).

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms and casual phrasing — 'health check', 'tune-up', 'checkup', 'system report', 'speed it up', 'free up / reclaim disk space', 'my laptop feels slow', 'why is my fan so loud', 'running out of space', and platform variants 'Mac/PC/laptop'.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (local computer health diagnostics) with distinctive triggers and an explicit scope boundary ('Desktop Commander skill: it relies on a real local shell... strictly read-only by default'), minimizing overlap with other skills.

5 / 5

Total

20

/

20

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
wonderwhy-er/DesktopCommanderMCP
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.