Results for “background-tasks”
10 skillsbackground-agents
This skill should be used when the user asks about "parallel agents", "background tasks", "run_in_background", "non-blocking agents", "check agent progress", "TaskOutput", "retrieve agent results", or discusses running multiple agents concurrently. Covers patterns for launching agents in background, monitoring progress, and retrieving results.
2
delegation
Offload sub-tasks to other agents, specialist models, or background jobs, with guidance on choosing the right method and verifying results.
2
More results
remove-bg-automation
Automates background removal tasks by discovering and executing Remove Bg tools through the Rube MCP interface.
66.9k
claude-handoff
Hands the current conversation to a fresh background agent that picks up the work immediately. Use when the user wants the work continued by a background agent.
580 · bundle
coding-agent
Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup.
0
dex
Task tracking for async/multi-step work. Use dex to create, track, and complete tasks that span multiple sessions or require coordination (e.g., coding agent dispatches, PR reviews, background jobs). Tasks stored as JSON files in .dex/tasks/.
12
async-job-design
`task-agent`/`review-agent`: use when jobs, workers, queues, schedules, retries, cancellation, or status visibility need design; skip when no async-job decision is required.
4 · bundle
trigger-dev
Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.
505 · bundle
boost-prompt
Refines task prompts through iterative questioning about scope, deliverables, and constraints, then copies the final markdown to the clipboard.
36.2k
coding-agent
Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.
9