agentleFS
LouLouLibsLouLouLibs/claude-skills/skills/esync-setup/SKILL.md

esync-setup

Skill1 starsChanged 59 days agoMITView on GitHub

Use when setting up file synchronization for a project, when user wants to sync local files to a remote server or backup location, or when configuring esync for a new or existing project directory

  • Reads credentials
  • Installs packages

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When setting up esync, add project-appropriate ignores:

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

esync Setup

Set up esync — a lightweight file sync tool that watches for changes and automatically rsyncs them to a local or remote destination.

Quick Reference

CommandPurpose
esync init -r user@host:/pathGenerate config from current directory
esync checkValidate config + preview included/excluded files
esync editOpen config in $EDITOR, validate on save
esync syncStart watching + syncing (TUI)
esync sync --daemonRun in background (no TUI)
esync statusCheck if daemon is running

Setup Workflow

  1. Install: go install github.com/louloulibs/esync@latest (or download binary from releases)
  2. Init: cd into the project, run esync init -r <destination>
    • Auto-imports .gitignore patterns
    • Detects common dirs (.venv, build, __pycache__, dist, .tox, .mypy_cache)
  3. Customize: Edit esync.toml — adjust ignore patterns, SSH, rsync flags
  4. Verify: esync check to see what files will be included/excluded
  5. Sync: esync sync (interactive TUI) or esync sync --daemon (background)

Config Structure

[sync]
local  = "."
remote = "user@host:/path/to/dest"

[sync.ssh]                          # Optional: explicit SSH control
host             = "myserver.com"
user             = "deploy"
port             = 22
identity_file    = "~/.ssh/id_ed25519"
interactive_auth = false            # true for 2FA servers

[settings]
watcher_debounce = 500              # ms between batched syncs
initial_sync     = false            # full sync on startup
ignore = [".git", "node_modules", ".DS_Store"]

[settings.rsync]
archive    = true
compress   = true
extra_args = ["--delete"]           # pass-through rsync flags
ignore     = ["*.log", "*.tmp"]     # rsync-only excludes

[settings.log]
file   = "/var/log/esync.log"       # optional log file (daemon mode)
format = "text"                     # "text" or "json"

Language-Specific Ignore Patterns

When setting up esync, add project-appropriate ignores:

Python: [".venv", "__pycache__", "*.pyc", ".tox", ".mypy_cache", "*.egg-info", ".pytest_cache"]

Node.js: ["node_modules", "dist", ".next", ".nuxt", "coverage", ".turbo"]

Go: ["vendor"] (most Go artifacts are in separate GOPATH)

Rust: ["target"]

R/Data Science: [".Rhistory", ".RData", "renv/library", "*.rds"]

General: [".git", ".DS_Store", "*.swp", "*.swo", ".env", "*.log"]

SSH Setup

Simple (when ~/.ssh/config is already set up):

[sync]
remote = "myserver:/opt/app"    # uses SSH config alias

Explicit (full control, enables ControlMaster keepalive):

[sync.ssh]
host          = "192.168.1.50"
user          = "deploy"
port          = 2222
identity_file = "~/.ssh/deploy_key"

2FA servers: Set interactive_auth = true in [sync.ssh].

Common Customizations

Delete extraneous remote files: extra_args = ["--delete"]

Bandwidth limit: extra_args = ["--bwlimit=5000"]

Set remote permissions: extra_args = ["--chmod=Du=rwx,Dgo=rx,Fu=rw,Fgo=r"]

Dry run first: esync sync --dry-run

Force initial full sync: esync sync --initial-sync

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.