Legacy batch file transfer
Skill jukrap/ai-agent-playbook/skills/legacy/legacy-batch-file-transfer
Use when maintaining scheduled batches, cron jobs, Windows Task Scheduler, CSV/Excel import-export, SFTP/file drops, EDI-like transfers, or nightly integrations.From its SKILL.md
npx -y skills add jukrap/ai-agent-playbook --skill legacy-batch-file-transferAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 194 tokens by cl100k_base, as published. Nobody here has run it
Legacy Batch File Transfer
Protect idempotency, file contracts, and operational recovery.
Workflow
- Identify scheduler, trigger time, input/output folders, filename patterns, encoding, delimiter, and retention rules.
- Trace parsing, validation, deduplication, retries, partial failure, and archive/error handling.
- Check timezone, holidays, business-day rules, file locks, concurrent runs, and large-file behavior.
- Preserve file format contracts unless every producer/consumer is updated.
- Verify with good file, malformed file, duplicate file, empty file, and rerun scenarios where feasible.
Guardrails
- Do not make batch jobs non-idempotent.
- Do not delete or overwrite files without an archive/recovery story.
- Do not hide partial failures behind success logs.
Reference
Read references/file-transfer-boundary.md for batch contracts, file lifecycle, retry behavior, reconciliation, and operational recovery checks.
What ships with it: 2 files
1.8 KB alongside SKILL.md
agents/
- openai.yaml278 B