Skip to content
Agentmart
Submit a tool

background-transfer-monitor

Use when running long background uploads: track progress.

Skill by iberi22

IndexedMIT
Write a review

Chalk Labs

Need help deploying background-transfer-monitor?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/iberi22-background-transfer-monitor

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use when running long background uploads: track progress.

Use cases: devops

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/background-transfer-monitor

What's inside

Skill name
background-transfer-monitor
Description
Use when running long background uploads: track progress.
License
MIT
Instructions
51 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • files: referenced but missing: references/rclone-drive.md

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Background Transfer Monitor

Run long transfers so they stay observable, report progress as % + ETA, and
verify completion independently. Applies to any transfer with countable units
(files, repos, chunks).

## 1. Launch (observable)

1. Redirect to a log file, never pipe through `tail`/`head`:
   `cmd > ~/.cache/<job>.log 2>&1`. Pipes buffer and blind process polling.
2. Launch in background with completion notification.
3. Verify alive IMMEDIATELY after launch: list/poll the job AND `pgrep` for
   the real child process. A launch that reports "started" but shows no
   process died silently — relaunch, never assume it is running.
4. Record total units up front (file count, repo count) so % is computable
   on every later ping without new discovery.

## 2. Progress checks

- Progress = completed units / total units, measured INDEPENDENTLY of the
  job (destination listing vs local source) — never from the job's own
  claims alone.
- For rclone-to-Drive specifics see `references/rclone-drive.md`.
- Before reporting "stuck" on a slow unit, drill one level deeper (files
  inside the current repo/dir) and report the inner %.

## 3. Status reports

- Terse, in Spanish: phase %, total %, what is running now, what remains,
  ETA. One or two lines, no narration.
- An unchanged % between pings is a valid report — name the current unit
  and confirm it is still transferring.

## 4. Completion

- Done = exit code 0 AND independent verification (destination counts match
  source, spot-check key artifacts). A worker's self-report alone is not
  evidence.
- Final report: what landed where + counts. If the session changed a
  standing condition (e.g. network constraint lifted), update memory.

## Pitfalls

- Never pipe a background job through `tail` for its final output — the
  monitor then only sees buffered previews until the pipe closes.
- A missing remote directory is not proof of failure — confirm the source
  unit is non-empty first (some backends have no empty-dir concept).
- Verify new rclone filters from the SAME root the transfer runs from —
  `**/` patterns match relative to root, so a check from elsewhere misleads.

From iberi22/skills, MIT.

Signals

Stars
0
Forks
0
Open issues
3
Last commit (this folder)
Oct 8, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get background-transfer-monitor running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying background-transfer-monitor?

CallGet help
Cite this page

background-transfer-monitor skill. Agent Mart. https://agentmart.dev/skills/iberi22-background-transfer-monitor (last updated 2026-10-24)