move_file

Move files between paths with validation and atomic rename.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moving and relocating files can be error-prone and lead to data loss if not handled correctly. This skill provides a safe, reliable way to move a file from a source path to a destination path while removing the original after the move.

Core Features & Use Cases

  • Validates that the source path exists and is a regular file before moving.
  • Moves the file to the destination, overwriting if it already exists.
  • Uses an atomic rename on the same filesystem and falls back to a copy-then-delete approach with rollback on failure.

Quick Start

Move the file from a source path to a destination path.

Frequently Asked Questions about move_file

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

FAQPage Schema
How do I safely move a file to a new path without risking data loss?

To safely move a file, this skill validates the source exists and is a regular file, then uses an atomic move on the same filesystem or falls back to a copy-and-delete approach with rollback on failure to prevent data loss.

What is the best way to relocate files across local or mounted filesystems?

The best way to relocate files is using an atomic rename when possible, falling back to a copy-then-delete approach with rollback on failure when moving across local or mounted filesystems.

How does an atomic file move work and when does it fall back to copy and delete?

An atomic file move works by renaming the file on the same filesystem, ensuring the destination is written before removing the source. It falls back to copy-and-delete with rollback when moving across different filesystems.

Does moving a file overwrite the destination if it already exists?

Yes, moving a file overwrites the destination if it already exists, while the source is removed only after a successful move operation completes.

What happens if a file transfer fails midway through the operation?

If a file transfer fails midway, the skill initiates a rollback during the copy-and-delete fallback approach to ensure the original source file remains intact and no data is lost.

When should I use a dedicated file move tool instead of a basic rename command?

You should use a dedicated file move tool when you need safety checks like validating the source is a regular file, atomic relocation on the same filesystem, and automatic rollback on failure to prevent data loss.