npx skills add smithery/scooter-lacroix --skill no-polling-agents
parcadei/continuous-claude-v3
no-polling-agents
No Polling for Background Agents
Installation
npx skills add parcadei/continuous-claude-v3 --skill no-polling-agents
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…
3.3M installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsPrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…
568.3K installsAlso in this package
Other skills from parcadei/continuous-claude-v3 · top by installs.
npx skills add parcadei/continuous-claude-v3
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,206 B -
docs
SUMMARY.md54 B
History
- First seen on skills.sh
- First recorded snapshot · 474 installs
SKILL.md
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
runinbackground: 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.txtin 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"