mcpbeat

No Polling Agents

vibeeval/no-polling-agents

No Polling for Background Agents

314 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
521
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/vibeeval/vibecosystem --skill no-polling-agents

The instruction itself

7 sections, as written by the author

No Polling for Background Agents

When launching parallel background agents, do NOT poll with sleep loops.

Pattern

Background agents write to status files when complete. Wait for them naturally.

DO

  • Launch agents with run_in_background: true
  • Continue with other work while agents run
  • Check status file only when user asks or when you need results to proceed
  • Trust the agent completion system

DON'T

  • Run sleep 10 && cat status.txt in loops
  • Continuously poll for completion
  • Waste tokens checking status repeatedly
  • Block on agents unless absolutely necessary

When to Check Status

  • User explicitly asks "are they done?"
  • You need agent output to proceed with next task
  • Significant time has passed and user is waiting

Example

// Launch agents
Task({ ..., run_in_background: true })
Task({ ..., run_in_background: true })

// Continue with other work or conversation
// Agents will write to status file when done

// Only check when needed
cat .claude/cache/status.txt

Source

User feedback: "You can just wait until everyone pings you"

How to use it

Copy the folder

Take vibeeval/no-polling-agents from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.