background-tasks

Run and monitor background tasks with filtered incremental logs.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/caocuong2404/amp-bg-tasks --skill background-tasks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: background-tasks
Source: https://github.com/caocuong2404/amp-bg-tasks/tree/main/skill
Command: npx skills add https://github.com/caocuong2404/amp-bg-tasks --skill background-tasks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the execution and monitoring of background tasks to prevent context pollution from long-running processes during debugging, tests, builds, and dev servers.

Core Features & Use Cases

  • bg_run to start a command in the background and obtain a task ID
  • bg_status to list all tasks or check a specific task's status
  • bg_output for smart, context-safe log reading with filters, excludes, and incremental reads
  • bg_stop to kill a running task or clean up finished task records
  • Guidance on using log hygiene rules (filters, since, tail, max_lines) for clean context
  • Monorepo workflows: coordinate backend and frontend tasks and read targeted logs

Quick Start

Start a background task with bg_run and then monitor its output with bg_output using appropriate filters.

Frequently Asked Questions about background-tasks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run background tasks without polluting context with long build logs?

You can run background tasks without log pollution by executing commands in the background and applying incremental log reads with filters. This isolates long-running builds or dev servers, returning only targeted output lines to maintain a clean debugging context.

What is the best way to monitor multiple dev servers in a monorepo?

The best way to monitor dev servers in a monorepo is using deterministic task lifecycle commands to start, track status, and read filtered logs per process. This coordinate backend and frontend tasks simultaneously while keeping their outputs isolated.

How do I read incremental output from a background process safely?

Incremental output from a background process is read safely using log hygiene rules like tail, since, max_lines, and excludes. These filters limit the retrieved log lines, preventing context overflow while tracking live process updates.

Can I stop a long-running background task and clean up its records?

Yes, you can stop a long-running background task and clean up its records using a dedicated kill command. This terminates the active process immediately and removes the associated finished task ID from the tracking list.

Does background task execution work for monorepo test and build workflows?

Background task execution works effectively for monorepo test and build workflows by applying deterministic task lifecycle commands. It manages concurrent processes across packages and applies log filters to isolate relevant test output.

Why do my background process logs overflow the context window during debugging?

Background process logs overflow the context window because raw output streams accumulate endlessly without filters. Applying incremental reads with excludes and max_lines limits prevents this pollution during active debugging sessions.