background-agent-pings
This pattern manages background agents by utilizing system progress notifications to avoid manual polling and resource waste.
Install
mkdir -p .claude/skills/background-agent-pings && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2356" && unzip -o skill.zip -d .claude/skills/background-agent-pings && rm skill.zipInstalls to .claude/skills/background-agent-pings
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Background Agent PingsKey capabilities
- →Execute background tasks without manual polling
- →Receive automated system notifications for agent progress
- →Identify agent completion via system reminders
- →Read output files only after agent signals completion
How it works
The agent executes tasks in the background while the user continues other work. The system pushes progress updates and completion signals via reminders instead of requiring manual status checks.
Inputs & outputs
When to use background-agent-pings
- →Executing background AI tasks
- →Monitoring agent progress
- →Managing agent output files
About this skill
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
TaskOutputfloods 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
When not to use it
- →When immediate task output is required for the current context
- →When manual polling is necessary to verify agent status
Limitations
- →Requires specifying an output file path in the task prompt
- →Main context is not updated with full agent transcripts
How it compares
This approach uses push-based system notifications to track agent status rather than manual polling which consumes tokens and time.
Compared to similar skills
background-agent-pings side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| background-agent-pings (this skill) | 2 | 7mo | Review | Beginner |
| opencode-cli | 14 | 7mo | Review | Advanced |
| claude-automation-recommender | 47 | 2mo | Review | Beginner |
| mcp-integration | 21 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by parcadei
View all by parcadei →You might also like
opencode-cli
SpillwaveSolutions
This skill should be used when configuring or using the OpenCode CLI for headless LLM automation. Use when the user asks to "configure opencode", "use opencode cli", "set up opencode", "opencode run command", "opencode model selection", "opencode providers", "opencode vertex ai", "opencode mcp servers", "opencode ollama", "opencode local models", "opencode deepseek", "opencode kimi", "opencode mistral", "fallback cli tool", or "headless llm cli". Covers command syntax, provider configuration, Vertex AI setup, MCP servers, local models, cloud providers, and subprocess integration patterns.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
hook-development
anthropics
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
swarm-advanced
ruvnet
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows