desktop-commander

Execute local shell commands and file operations with user confirmation.

20|25|Updated May 30, 2026
One-click install
npx skills add https://github.com/OpenCoven/coven-cave --skill desktop-commander
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop-commander
Source: https://github.com/OpenCoven/coven-cave/tree/main/marketplace/plugins/desktop-commander/skills/desktop-commander
Command: npx skills add https://github.com/OpenCoven/coven-cave --skill desktop-commander

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manages local shell and file operations with a focus on explicit and controlled actions, eliminating errors and unnecessary steps.

Core Features & Use Cases

  • Scoped Commands: Run local commands with precision, avoiding unintended consequences.
  • File Manipulation: Edit, move, and inspect files safely, with guardrails to prevent data loss.
  • Process Inspection: Monitor and manage running processes with clear, controlled actions.
  • Use Case: When you need to edit a file directly on your system but want to ensure you're only modifying what you intend to, Desktop Commander helps confirm actions before they are executed.

Quick Start

Run the 'ls' command to list files in the current directory, confirming the action with explicit intent.

Frequently Asked Questions about desktop-commander

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute local shell commands safely without unintended side effects?

To execute local shell commands safely, this skill uses explicit user intent confirmation and safety checks before running scoped commands, preventing unintended consequences. It requires local system access and asks you to confirm actions prior to execution.

How does file manipulation with guardrails prevent data loss when editing?

File manipulation with guardrails prevents data loss by requiring explicit user confirmation before editing, moving, or inspecting files. This controlled approach ensures you only modify what you explicitly intend to change on your local system.

What is process inspection and how does it work for managing running applications?

Process inspection is the monitoring and managing of running processes with clear, controlled actions. It works by checking system states and requiring explicit user intent before executing process control commands, ensuring safe local system operations.

Can I use this for local system operations on any operating system?

You can use this for local system operations if your environment provides local shell access for execution. The skill manages command execution, file manipulation, and process inspection with safety checks, requiring explicit access to the local system.

What is the best way to manage local file operations with explicit intent?

The best way to manage local file operations with explicit intent is using a controlled approach that adds safety guardrails to command execution. It prevents data loss by confirming actions before they are executed, ensuring you only modify intended files.

Why does command execution require confirmation before running on my local system?

Command execution requires confirmation to eliminate errors and unnecessary steps during local system operations. By focusing on explicit and controlled user intent, the skill ensures safety checks are passed before any file manipulation or process inspection occurs.