desktop-commander-deploy

Document Desktop Commander workflows for safe file operations in the PANaCEa repo.

Updated Nov 16, 2025
One-click install
npx skills add https://github.com/aaronjullger-lgtm/PANaCEa --skill desktop-commander-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop-commander-deploy
Source: https://github.com/aaronjullger-lgtm/PANaCEa/tree/main/.claude/skills/desktop-commander-deploy
Command: npx skills add https://github.com/aaronjullger-lgtm/PANaCEa --skill desktop-commander-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill documents and codifies best practices and workarounds for using Desktop Commander MCP to write, read, edit code, and run commands in the PANaCEa repository, helping prevent silent failures and wasted time.

Core Features & Use Cases

  • Centralized guidance on common issues like empty read_file responses, git index locks, write_file timeouts, and tsc OOM crashes.
  • Step-by-step workarounds and best practices for reliable code deployment and local development workflows.
  • Use cases include writing or inspecting repository files, editing code safely, and executing Desktop Commander tasks with guardrails.

Quick Start

Follow the documented workarounds and run the recommended procedures to ensure reliable file operations in the PANaCEa repo.

Frequently Asked Questions about desktop-commander-deploy

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

FAQPage Schema
Why does read_file return empty responses when using Desktop Commander?

Empty read_file responses are a common Desktop Commander anomaly. This skill provides documented workarounds and guardrails to handle these silent failures and ensure reliable file inspection in the PANaCEa repo.

What causes tsc out of memory crashes and how can I avoid them?

tsc OOM crashes occur when TypeScript compilation exhausts memory. This skill codifies concrete requirements and procedures to avoid tsc OOM crashes and prevent silent failures during deployment.

How do I safely write and edit code with Desktop Commander without silent failures?

To safely edit code, follow the documented safe file operation scopes, read/write patterns, and guardrails. This skill defines robust workflows to prevent write_file timeouts and other common pitfalls.

Does this skill provide guidance for both local development and deployment workflows?

Yes, this skill defines guardrails for both local development and deployment workflows. It centralizes best practices for executing Desktop Commander tasks reliably across the PANaCEa repository.