safe-file-deletion

Require explicit user approval before executing file deletion commands.

10.9k|1.3k|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/accomplish-ai/accomplish --skill safe-file-deletion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safe-file-deletion
Source: https://github.com/accomplish-ai/accomplish/tree/main/packages/agent-core/mcp-tools/safe-file-deletion
Command: npx skills add https://github.com/accomplish-ai/accomplish --skill safe-file-deletion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents accidental or unauthorized file deletions by requiring explicit user permission before any delete operation is executed.

Core Features & Use Cases

  • Enforces a per-operation permission prompt before delete commands (rm, unlink, fs.rm, and rm -rf).
  • Supports batching by requesting permission for multiple files in a single prompt.
  • Applicable across scripts and tools that delete files to minimize data loss risks.

Quick Start

Use the safe-file-deletion policy before running a delete operation. For example, attempt to delete /path/to/file.txt and ensure the system asks for confirmation before proceeding.

Frequently Asked Questions about safe-file-deletion

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

FAQPage Schema
How do I prevent accidental file deletion when running rm or fs.rm commands?

Require explicit user permission before file deletion by enforcing a confirmation prompt. This applies to rm, unlink, fs.rm, and rm -rf commands, ensuring the system waits for approval before proceeding with any delete operation.

Can I batch multiple file deletions with a single permission prompt?

Yes. The permission system supports batching by requesting approval for multiple files in a single prompt rather than confirming each file individually, streamlining the deletion workflow while maintaining safety.

Does this work across scripts and tools that delete files, or only command-line operations?

File deletion permission applies across scripts and tools that delete files, not just direct command-line operations. This minimizes data loss risk by enforcing the same confirmation requirement consistently.

What's the best way to protect against unauthorized file deletions in automated workflows?

Enforce an explicit user permission policy before delete operations execute. This guards against both accidental deletions and unauthorized access by requiring confirmation before any file removal proceeds.

Why should I use permission prompts instead of relying on file permissions alone?

Permission prompts add an active confirmation step that catches mistakes before deletion occurs, whereas file permissions only control who can delete. Combined, they provide both access control and accident prevention.