What this error means

Error: Permission denied: Write to /home/node/mulmoclaude/.claude/skills/... Error: Permission denied: Edit /home/node/mulmoclaude/.claude/skills/... is a Claude Code failure pattern reported for developers trying to fix claude code refusing to write or edit files in .claude/skills/ directory without showing permission prompt. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Issue (2026-05-13) reports Claude Code ~2.1.79+ silently denies Write/Edit to .claude/skills/** files without permission dialog. Bash tool workaround (Python heredoc) still works. SkipAutoPermissionPrompt toggle doesn't help.

Common causes

  • Claude Code is a paid AI coding tool. After v2.1.79, Write/Edit operations on .claude/skills/** files are silently denied without permission dialog, breaking skill management workflows. Developers need to understand why and how to fix it.
  • Issue (2026-05-13) reports Claude Code ~2.1.79+ silently denies Write/Edit to .claude/skills/** files without permission dialog. Bash tool workaround (Python heredoc) still works. SkipAutoPermissionPrompt toggle doesn't help.

Quick fixes

  1. Confirm the exact error signature matches Error: Permission denied: Write to /home/node/mulmoclaude/.claude/skills/... Error: Permission denied: Edit /home/node/mulmoclaude/.claude/skills/....
  2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
  3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.