clanker-ops-background-dispatch

Manages background dispatch of Clanker Ops tasks via subprocess spawning and audit logging.

Updated May 15, 2026
One-click install
npx skills add https://github.com/ruskibeats/t1d --skill clanker-ops-background-dispatch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clanker-ops-background-dispatch
Source: https://github.com/ruskibeats/t1d/tree/main/.pi/skills-archive/clanker-ops-background-dispatch
Command: npx skills add https://github.com/ruskibeats/t1d --skill clanker-ops-background-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) components.

What problem does it solve?

Manages the background dispatch of Clanker Ops tasks to pi-subagents, ensuring tasks run asynchronously while maintaining responsiveness and providing persistent audit logs.

Core Features & Use Cases

  • Background Dispatch: Executes Clanker Ops tasks in the background using detached subprocesses.
  • Path Resolution and Config Building: Resolves paths for jiti and runner scripts, and constructs pi-subagents RunnerConfig.
  • Process Spawn and Fallback Commands: Spawns background processes and provides manual fallback commands for execution issues.
  • Audit Logging: Maintains a persistent audit trail for task dispatches.

Quick Start

Dispatch a Clanker Ops task to a pi-subagent with the command: /clanker dispatch #N to @agent.

Frequently Asked Questions about clanker-ops-background-dispatch

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

FAQPage Schema
How do I dispatch background tasks with subprocess spawning in Node.js?

Background task dispatch with subprocess spawning executes processes asynchronously using detached subprocesses. This approach maintains system responsiveness while running tasks in the background and generating persistent audit logs for each dispatched process.

What is audit logging for background process dispatch and why do I need it?

Audit logging for background process dispatch creates a persistent record of all spawned tasks and their execution details. You need it to maintain accountability and track asynchronous task history when subprocesses run detached from the main process.

Do I need Node.js to run subprocess spawning for background task dispatch?

Yes, Node.js is required to run subprocess spawning for background task dispatch. The process spawning and path resolution logic depends on Node.js to execute detached subprocesses and manage the runner configuration.

How do I configure path resolution and runner config for background task dispatch?

Configuring path resolution and runner config for background task dispatch involves resolving paths for runner scripts and constructing the runner configuration on disk. The system then spawns the background process using this configuration with fallback commands available.

What happens if subprocess spawning fails during background task dispatch?

When subprocess spawning fails during background task dispatch, the system provides manual fallback commands for execution. This allows you to manually trigger the task and verify the path resolution or runner configuration if the detached process encounters issues.