parcadei/Continuous-Claude-v3 / .claude/skills/no-polling-agents
no-polling-agents
VerifiedNo Polling for Background Agents
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.2 KB |
SKILL.md
View on GitHub---
name: no-polling-agents
description: No Polling for Background Agents
user-invocable: false
---
# 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
1. User explicitly asks "are they done?"
2. You need agent output to proceed with next task
3. Significant time has passed and user is waiting
## Example
```typescript
// 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"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |