Skip to content
FileMayorby Chevza
Download
Use through your LLM

Talk to your filesystem. Through Claude.

Install FileMayor as a skill in Claude, Cowork, or any LLM agent that supports system prompts. From then on, prompts like "organize my Downloads folder" route through FileMayor's Curative Triad — your assistant runs the right commands in the right order, with the safety rails intact.

Files never leave your machine · the LLM only orchestrates · undo always works

Install · ~30 seconds

Three commands.

Step 1

Install the CLI.

npm install -g filemayor

Requires Node 20+. Or grab the desktop app — same engine, no Node needed.

Step 2

Drop in the skill.

git clone https://github.com/Hrypopo/filemayor-landing.git /tmp/fm-skill mkdir -p ~/.claude/skills cp -r /tmp/fm-skill/skill ~/.claude/skills/filemayor rm -rf /tmp/fm-skill

Restart Claude Code. The skill auto-loads from ~/.claude/skills.

Step 3

Just ask.

  • "organize my Downloads folder"
  • "clean up disk space"
  • "find duplicate photos"
  • "what is eating my disk"

The skill triggers automatically. No prefix needed.

Cowork users: install via plugin marketplace (search FileMayor), or copy the skill folder into your local Cowork skills directory using the same pattern. Other MCP-compatible clients can paste the SKILL.md contents into a system prompt — a dedicated MCP server is in progress.

What the skill teaches your LLM

The Curative Triad. With safety rails.

The skill is one markdown file. It teaches the LLM five verbs and five prompt-level safety rails — never apply without a plan, never touch system directories, always offer undo, etc. The CLI itself adds a second, model-independent layer: the Chevza Doctrine runs inside the binary regardless of what the LLM asks. An LLM can choose not to call the tool, but it cannot disable the safety architecture.

  1. 01
    scan
    filemayor scan ~/Downloads --json

    Read-only inventory.

  2. 02
    explain
    filemayor explain ~/Downloads

    Health score + plain-English issues.

  3. 03
    cure
    filemayor cure ~/Downloads --prompt "..."

    AI proposes the plan. Nothing touched.

  4. 04
    apply
    filemayor apply

    Execute. Journaled per move.

  5. 05
    undo
    filemayor undo --all

    Reverse the session at any time.

Privacy posture

The LLM orchestrates. The CLI executes. Your files stay local.

Your assistant's role is the conductor — it picks which command to run, parses the JSON output, asks you to confirm. The actual file work happens inside the Chevza Doctrine on your machine. AI metadata-only calls only fire when you explicitly use a command that involves them (explain, cure); the rest of the verbs are fully offline.

Disable all AI with FILEMAYOR_AI=off. The skill still works — your assistant just falls back to organize and the deterministic verbs.

Sources