delete_file

Delete specified filesystem paths while enforcing safety boundary validations.

8|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/OpenAuthority/clawthority --skill delete-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delete_file
Source: https://github.com/OpenAuthority/clawthority/tree/main/examples/skills/delete_file
Command: npx skills add https://github.com/OpenAuthority/clawthority --skill delete-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool prevents accidental deletions by validating paths, enforcing safety checks on protected system areas, and ensuring only targeted deletions occur.

Core Features & Use Cases

  • Deletes the file or empty directory at the specified path.
  • Enforces safety rules to block deletions of critical system paths and non-existent targets.
  • Provides clear error codes when a path cannot be deleted or is not empty.

Quick Start

Provide a path to delete and execute the tool to remove the file or empty directory safely.

Frequently Asked Questions about delete_file

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

FAQPage Schema
How do I safely delete a file from the filesystem without risking critical system paths?

To safely delete a file, you provide a path parameter to the tool, which validates the input and blocks access to critical system paths before performing the deletion. This ensures only targeted files are removed with explicit error signaling.

Why does my directory delete operation fail with an error?

Your directory delete operation fails because the tool rejects non-empty directories as a safety precaution. It enforces safety rules that block deletions of non-empty directories and non-existent targets, providing clear error codes when a path cannot be deleted.

Can I delete a directory that still contains files?

No, you cannot delete a directory that still contains files because the tool explicitly rejects non-empty directories. It operates within a defined safety boundary by ensuring only empty directories or targeted files are removed from the filesystem.

What is the best way to prevent accidental deletions during filesystem cleanup?

The best way to prevent accidental deletions during filesystem cleanup is to use a tool that validates paths and enforces safety checks on protected system areas. This approach ensures only specific files or empty directories are deleted, blocking access to critical paths.

Does the delete operation work on protected system paths?

No, the delete operation does not work on protected system paths. The tool enforces strict safety rules to block deletions of critical system areas, preventing accidental damage by validating inputs and rejecting access to these protected locations.

How do I get started with removing an empty directory safely?

To get started removing an empty directory safely, simply provide a valid path to the target directory and execute the tool. The tool will validate the input, confirm the directory is empty, and perform the deletion with explicit error signaling if issues arise.