auto-run

Automate NexusOS batch task dispatch and reconciliation using DISPATCH.md and PROGRESS.md.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/cryptopafi/nexusos-skills --skill auto-run-cryptopafi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-run
Source: https://github.com/cryptopafi/nexusos-skills/tree/main/auto-run
Command: npx skills add https://github.com/cryptopafi/nexusos-skills --skill auto-run-cryptopafi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NexusOS workflows with many batch tasks require reliable dispatch, progress reconciliation, and recovery from context or session limits; manual orchestration is slow, error-prone, and hard to resume. This Skill centralizes scanning DISPATCH.md files, dispatching agents, tracking PROGRESS.md, and preserving checkpoint state so batches can be resumed or paused safely.

Core Features & Use Cases

  • Checkpointed Dispatch Loop: Initializes and updates a JSON checkpoint to survive context exhaustion and allow --resume behavior across restarts.
  • Targeted and Bulk Processing: Accepts --task-id for single-task handling or --all-active to process all tasks in the active workspace, with configurable batching and concurrency limits.
  • Automated Reconciliation and Safety: Periodically reads PROGRESS.md to move tasks between in_progress, completed, and failed, applies a circuit-breaker for repeated failures, and gracefully pauses when limits are reached or context degrades.

Quick Start

Run the auto-run skill with --all-active to dispatch and reconcile all DISPATCH.md tasks in the active workspace.

Frequently Asked Questions about auto-run

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

FAQPage Schema
How do I automate batch task dispatching and recovery in NexusOS?

Automate batch task dispatching in NexusOS by reading DISPATCH.md files and dispatching agents while maintaining checkpoint state in auto-run-checkpoint.json for safe resumption. It periodically reconciles PROGRESS.md to move tasks between in_progress, completed, and failed.

What is the best way to resume batch tasks after reaching context limits?

Resume batch tasks after context limits by relying on checkpointed state stored in auto-run-checkpoint.json. The Skill saves execution state during dispatch loops, allowing you to safely pause and restart batches without losing progress.

Can I process all active tasks at once or do I need to specify a task ID?

Process all active tasks at once using the --all-active flag for bulk dispatching, or use the --task-id flag to target a single task. Both options support configurable batching and concurrency limits.

How does task orchestration handle repeated failures during batch processing?

Task orchestration handles repeated failures by applying a circuit-breaker mechanism that pauses processing. It automatically tracks failures in checkpoint state and gracefully halts operations when limits are reached or context degrades.

Do I need specific files in my workspace to use automated task orchestration?

You need DISPATCH.md files in your active workspace directory for the orchestrator to scan and dispatch. The tool also reads and updates PROGRESS.md files to track task status and maintain accurate checkpoint state.

Why does my NexusOS task runner pause during bulk processing?

Your task runner pauses during bulk processing when context degrades or concurrency limits are reached. This graceful pause is a safety mechanism that preserves checkpoint state, allowing you to resume operations later.