ssh_mv

Move files across remote hosts atomically via SSH and SFTP.

6|Updated Apr 17, 2026

Search Tags:#filesystem #file move #remote operation #remote hosting #SFTP

Ready to run

npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-mv

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ssh_mv
Source: https://github.com/Nightreaver/python-ssh-mcp/tree/main/skills/ssh-mv
Command: npx skills add https://github.com/Nightreaver/python-ssh-mcp --skill ssh-mv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The need for a robust and secure method to move files across remote hosts, ensuring that operations are atomic and secure.

Core Features & Use Cases

Atomic File Moving: Ensures file moves are completed without failure, preserving data integrity.
Cross-filesystem and POSIX Compatibility: Supports moving files across filesystems and works on POSIX systems.
Windows Compatibility: Allows file moves on Windows hosts with SFTP posix_rename support.
Use Case: Automate the deployment of an application by moving a compiled artifact from a staging directory to a production directory on a remote server.

Quick Start

Move the file 'application.tar.gz' from the staging directory to the production directory on the server 'web01'.

Frequently Asked Questions about ssh_mv

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

FAQPage Schema

How do I move files across different filesystems on a remote host?▼

To move files across different filesystems on a remote host, you can use atomic operations that ensure data integrity. This Skill supports cross-filesystem moves on POSIX systems, completing the transfer without partial failures.

Does SFTP support moving files on Windows hosts?▼

SFTP supports moving files on Windows hosts by utilizing the posix_rename feature. This provides compatibility for remote file operations on Windows systems while maintaining secure authentication.

What is the best way to automate moving a deployment artifact to a production directory?▼

The best way to automate moving a deployment artifact is by executing atomic file moves from a staging directory to a production directory. This ensures the remote operation completes fully without corrupting the compiled artifact.

Why do remote file moves fail and how can I ensure they are atomic?▼

Remote file moves can fail due to interruptions or cross-filesystem incompatibilities. You can ensure they are atomic by using operations that preserve data integrity and guarantee the move completes successfully before finalizing.

Can I execute remote file operations without direct shell access?▼

You can execute remote file operations without direct shell access by using SFTP with posix_rename support. This requires proper authentication and access to the remote host's filesystem to securely move files.

Do I need POSIX compliance to move files on remote servers?▼

You do not strictly need POSIX compliance to move files on remote servers, as Windows compatibility is provided through SFTP. However, POSIX systems are fully supported for native cross-filesystem atomic moves.