safe-file-deletion

Require explicit user consent before deleting files or directories.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/CxxxxDxxxF/project-blackout --skill safe-file-deletion-cxxxxdxxxf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: safe-file-deletion
Source: https://github.com/CxxxxDxxxF/project-blackout/tree/main/packages/agent-core/mcp-tools/safe-file-deletion
Command: npx skills add https://github.com/CxxxxDxxxF/project-blackout --skill safe-file-deletion-cxxxxdxxxf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents accidental or unauthorized deletion of files by enforcing explicit user permission before any file removal operation.

Core Features & Use Cases

  • Mandatory Permission: Requires user approval before executing any file deletion command.
  • Batch Deletion Support: Allows requesting permission for multiple files in a single operation.
  • Use Case: When an agent needs to clean up old log files, it will first ask for your explicit permission for each file or batch of files before proceeding, ensuring no critical data is lost.

Quick Start

Use the safe-file-deletion skill to request permission to delete the file '/home/user/old_data.txt'.

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 automated scripts?

To prevent accidental file deletion, you can enforce explicit user consent before executing any file removal operations. This requires a mandatory permission request step for single files, multiple files, or directory removal to ensure no critical data is lost.

Can I request permission to delete multiple files in a single batch operation?

Yes, you can request permission to delete multiple files in a single batch operation. This functionality allows scripts to ask for user approval for a batch of files, such as cleaning up old log files, before proceeding with the removal.

How does a user consent mechanism work for directory removal?

A user consent mechanism for directory removal works by intercepting any command that removes data from disk and requiring explicit user authorization. It enforces a confirmation step that prevents the deletion from executing until permission is granted.

What is the best way to secure data safety during automated disk cleanup?

The best way to secure data safety during automated disk cleanup is to enforce mandatory permission checks before executing file deletion commands. This ensures user authorization is obtained for each file or batch, preventing unauthorized data loss.

Does this file deletion permission check apply to all script functions that remove data?

Yes, the file deletion permission check applies to any command or script function that removes data from disk. It enforces explicit user authorization across all file removal operations to guarantee data safety.

When should I not use an automated file removal process without user consent?

You should not use an automated file removal process without user consent when handling critical data. Bypassing explicit permission requests risks accidental data loss during tasks like batch directory removal or log cleanup.