agentsclimarketplace

Background agent pings

Skill vibeeval/vibecosystem/skills/background-agent-pings

AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution.

Install
npx -y skills add vibeeval/vibecosystem --skill background-agent-pings

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Background Agent Pings

SKILL.md

1.3 KB, 288 tokens by cl100k_base, as published. Nobody here has run it

Background Agent Pings

Trust system reminders as agent progress notifications. Don't poll.

Pattern

When you launch a background agent, continue working on other tasks. The system will notify you via reminders when:

  • Agent makes progress: Agent <id> progress: X new tools used, Y new tokens
  • Agent writes output file (check the path you specified)

DO

1. Task(run_in_background=true, prompt="... Output to: .claude/cache/agents/<type>/output.md")
2. Continue with next task immediately
3. When system reminder shows agent activity, check if output file exists
4. Read output file only when agent signals completion

DON'T

# BAD: Polling wastes tokens and time
Task(run_in_background=true)
Bash("sleep 5 && ls ...")  # polling
Bash("tail /tmp/claude/.../tasks/<id>.output")  # polling
TaskOutput(task_id="...")  # floods context

Why This Matters

  • Polling burns tokens on repeated checks
  • TaskOutput floods main context with full agent transcript
  • System reminders are free - they're pushed to you automatically
  • Continue productive work while waiting

Source

  • This session: Realized polling for agent output wasted time when system reminders already provide progress updates

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.