CtrlK
BlogDocsLog inGet started
Tessl Logo

terminal

Use Desktop Commander for terminal and command-line work, especially anything that needs a shell whose state persists across turns: Python/Node REPLs, database shells, dev servers and other long-running processes, SSH into remote machines, and Windows PowerShell. Also handles everyday terminal tasks — navigating folders, choosing the right command for the user's shell (PowerShell, cmd, bash, zsh), running Docker/curl/cloud-CLI commands, inspecting processes and ports, and saving recurring workflows as scripts — even when the user doesn't say "Desktop Commander" or "terminal." Reach for it on pasted errors like "command not found", "permission denied", "EADDRINUSE", "address already in use", "npm ERR!", "ModuleNotFoundError", or "ENOENT", and on intents like "what's using port 3000", "kill that process", "ssh into my server", or "why won't my dev server start". Works on Windows, macOS, and Linux. Never run destructive commands without explicit confirmation.

75

Quality

94%

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

88%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.

A well-structured, actionable terminal assistant body with concrete commands, an executable REPL pattern, and strong safety validation around destructive operations. It is concise and clearly navigable, with only minor trim opportunities.

DimensionReasoningScore

Conciseness

Dense and mostly actionable — tables of shell equivalents, code blocks, and bullets — with little explanation of concepts Claude already knows; only minor flavor prose ('Be a calm, safe, cross-platform terminal copilot') and a few guidance sentences could be trimmed.

4 / 5

Actionability

Fully executable guidance: copy-paste REPL pattern, concrete per-CLI commands, shell-equivalent tables, and specific port/process inspection commands covering the common cases.

5 / 5

Workflow Clarity

Multi-step processes (env detection first, §6 numbered error diagnosis, §7 destructive-command confirmation) are clearly sequenced with explicit validation checkpoints — show-before-kill, dry-run-first, wait for a clear 'yes' — so the destructive-cap is avoided.

5 / 5

Progressive Disclosure

Well-organized into eight numbered sections plus operating etiquette with clear headers and easy navigation; no bundle files exist so everything is inline, which is appropriate for a cohesive operational guide though slightly long for a single file.

4 / 5

Total

18

/

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.

A strong, third-person description that pairs concrete capabilities with explicit, natural-language triggers covering both pasted errors and user intents. It is comprehensive, distinct, and free of vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — REPLs, database shells, dev servers, SSH, Docker/curl/cloud-CLI, process/port inspection, saving scripts — giving comprehensive coverage rather than vague abstractions.

5 / 5

Completeness

Explicitly answers both 'what' (Desktop Commander for persistent-shell terminal work and everyday terminal tasks) and 'when' via concrete 'Reach for it on...' trigger clauses covering pasted errors and intents.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including verbatim error strings users paste ('command not found', 'EADDRINUSE', 'npm ERR!', 'ModuleNotFoundError', 'ENOENT') and natural intents ('what's using port 3000', 'kill that process', 'why won't my dev server start').

5 / 5

Distinctiveness Conflict Risk

Clear niche around Desktop Commander / persistent-shell terminal work with distinctive error-string and intent triggers, making overlap with unrelated skills minimal.

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.