agentleFS
geekxxgeekxx/ai-assistant-starter-kit/.claude/skills/safe-mv/SKILL.md

safe-mv

Skill1 starsChanged 4 months agoMITView on GitHub

Use whenever moving or relocating files on cloud-synced paths (OneDrive, Google Drive, or any CloudStorage path). Enforces the safe-mv.sh wrapper — never use raw mv or cp on cloud paths.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not use raw mv or cp on cloud paths.

    line 14
  2. Very specific:

    Run --dry-run first to preview the move without touching anything.

    line 19
  3. Very specific:

    If the output looks correct, run without --dry-run to execute.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Safe Move

Enforces the safe-mv.sh wrapper for all file moves on cloud-synced paths. The wrapper refuses to move zero-byte offline stubs (files that appear present but have not been downloaded from the cloud), preventing silent data loss.

When to run this

Any move or relocation of files where the source or destination is under OneDrive, Google Drive, or any CloudStorage path. For local-only paths this wrapper is optional but harmless.

Do not use raw mv or cp on cloud paths. This skill exists to make that deterministic.

Steps

  1. Confirm source(s) and destination before executing.
  2. Run --dry-run first to preview the move without touching anything.
  3. If the output looks correct, run without --dry-run to execute.

Tools

  • $CLAUDE_PROJECT_DIR/.claude/scripts/safe-mv.sh — safe-move wrapper.

Usage:

safe-mv.sh [OPTIONS] SOURCE [SOURCE...] DEST

Flags:

  • --dry-run / -n — show what would move, no filesystem changes
  • --force / -f — skip the stub check (confirmation prompt still fires if stubs are detected)
  • --help / -h — show usage

Rules:

  • Single source: DEST can be a file path or a directory.
  • Multiple sources: DEST must be a directory.
  • Zero-byte file on a cloud path → rejected unless --force is passed.
  • --force with stubs detected → prompts for explicit confirmation before proceeding.
  • Paths with spaces are handled correctly (all variables quoted internally).

Output

For each source: prints Moving: <src> / To: <dest> / Done. on success. Exits non-zero on any failure with a plain-English error message.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.