model-sync
/model-sync
Synchronizes ML model files across servers. Supports rsync-based transfer with bandwidth control and checksum verification. Use for "모델 동기화", "모델 배포", "rsync 모델", "서버로 전송" requests.
- Author
- jiunbae ↗
- Repository
- agent-skills ↗
- Licence
- MIT
- Last repository change
- 01.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 2
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 2 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/model-sync.sh, tests/test_model_sync.py
What it does and when to use it
Synchronizes ML model files across servers. Supports rsync-based transfer with bandwidth control and checksum verification. Use for "모델 동기화", "모델 배포", "rsync 모델", "서버로 전송" requests.
Triggers from the description
Original author description
Synchronizes ML model files across servers. Supports rsync-based transfer with bandwidth control and checksum verification. Use for "모델 동기화", "모델 배포", "rsync 모델", "서버로 전송" requests.
How it works
- Configuration
- Safe Workflow
- Quick Reference
- Common Patterns
- Multi-Server Sync
- Verification
- Best Practices
SKILL.md preview
---
name: model-sync
description: Synchronizes ML model files across servers. Supports rsync-based transfer with bandwidth control and checksum verification. Use for "모델 동기화", "모델 배포", "rsync 모델", "서버로 전송" requests.
---
# Model Sync
Sync ML model files between configured servers with the bundled helper. Preview
the exact transfer first, then request post-transfer SHA-256 verification.
## Configuration
Create `~/.model-sync.yaml` with simple scalar values:
```yaml
servers:
gpu1:
host: gpu1.internal
user: deploy
model_base: /srv/models
```
Server names, hosts, users, and remote paths are intentionally restricted to
shell-safe forms. Remote paths must be absolute, cannot be `/`, and cannot
contain whitespace or `.`/`..` segments. Transfers stay within the configured
`model_base`; `server:relative/path` is resolved beneath that base.
## Safe Workflow
```bash
# Preview first.
./scripts/model-sync.sh push ./models/llama-7b gpu1 --dry-run
# Transfer, then compare canonical relative-path + SHA-256 manifests.
./scripts/model-sync.sh push ./models/llama-7b gpu1 --verify
# Pull and apply the same verification contract.
./scripts/model-sync.sh pull gpu1:llama-7b ./models/llama-7b --verify
```
The helper exits nonzero when transfer or verification fails and reports
`Verified | yes` only after the manifests match. It accepts regular files and
directories with safe relative paths; symlinks and special files are rejected.
Local rsync operands are normalized to absolute paths. Pull destinations reject
every existing symlink component, are contained beneath their nearest trusted
existing physical ancestor, and are checked again immediately before transfer.
Push destinations receive a fixed remote structural preflight that rejects
symlink components and checks containment beneath the configured `model_base`.
These checks do not provide a caller-configured local destination policy root.
They also cannot eliminate a check/use race if local or remote directories are
mutated concurrently; stronger guarantees require descriptor-relative or
transactional transfer support.
`--delete` is disabled because the helper does not implement an approval-bound
deletion preview. Arbitrary remote `exec` is also disabled.
## Quick Reference
### Basic Sync
```bash
rsync -avz --progress \
./models/ user@server:/models/
```
### With Bandwidth Limit
```bash
rsync -avz --bwlimit=10000 \
./models/ user@server:/models/
```
### Checksum Verification
```bash
# -c enables rsync's checksum comparison.
rsync -avzc \
./models/ user@server:/models/
```
## Common Patterns
### Sync Specific Model
```bash
rsync -avz ./models/llama-7b/ server:/models/llama-7b/
```
### Exclude Checkpoints
```bash
rsync -avz --exclude='*.ckpt' --exclude='*.tmp' \
./models/ server:/models/
```
### Dry Run (Preview)
```bash
rsync -avzn ./models/ server:/models/
```
## Multi-Server Sync
```bash
# Sync to multiple servers
for server in gpu1 gpu2 gpu3; do
rsync -avz ./models/ "${server}:/models/" &
done
wait
```
## Verification
```bash
# Generate checksum
sha256sum models/model.bin > model.sha256
# Verify on remote
ssh server "cd /models && sha256sum -c model.sha256"
```
## Best Practices
- Use `--checksum` for critical models
- Limit bandwidth on production networks
- Always verify after sync
- Do not add `--delete` without a bounded deletion manifest and fresh approval
Files in this package (3)
- SKILL.md 3 KB
- scripts/model-sync.sh 32 KB
- tests/test_model_sync.py 18 KB
Versions
The database has no other skills named model-sync.
Database snapshot: 13.11.2026 · package version 390d59387860 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100rsync
rsync copies and synchronizes files locally or over SSH, sending only the parts that changed. Use when someone asks to "copy files to a server", "sync two directories", "mirror a folder", "make incremental backups with hard links", "deploy a build to a remote host", "resume a… - 90ostiary
Run commands and transfer files on remote servers through ostiary. Use whenever a task needs a shell on a server, logs from a host, a service restart, or a file copied to/from a host. Never use ssh/scp/rsync directly. - 100linux-rsync-sync
Use when designing, previewing, running, or verifying rsync copies, mirrors, offsite transfers, or hard-linked backups on Debian/Ubuntu or RHEL-family hosts. Covers SSH, filters, deletion, checksums, and resume; use linux-archive-integrity for tar archives. - 100sc-sync
rsync gitignored files between a VPS and a local machine over Tailscale, for a repo checked out (mirrored path) on both. Two directions: vps-local and local-vps, selected by SYNC_ROLE crossed with the requested direction (never by sniffing hostname). Always dry-run first,… - 100ssh
SSH remote access - connections, tunnels, keys, file transfers. Use when connecting to servers, managing SSH keys, setting up port forwarding, or transferring files with scp/rsync. - 100bdb-deploy
Use when the user wants to build and deploy a project to a real server via rsync over SSH — "deploy this", "push the build live", "sync to production". Not for git push/PR workflows, and not a replacement for a real CI pipeline; this is the direct-deploy path.