automated-orchestration

Orchestrates multi-stage analysis pipelines with checkpoint resume and adaptive depth.

13|2|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/aaddrick/written-voice-replication --skill automated-orchestration-aaddrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: automated-orchestration
Source: https://github.com/aaddrick/written-voice-replication/tree/main/.claude/skills/automated-orchestration
Command: npx skills add https://github.com/aaddrick/written-voice-replication --skill automated-orchestration-aaddrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long-running data pipelines that fail mid-execution lose hours of progress, forcing full restarts. This Skill provides a checkpoint/resume architecture so every stage is resumable, idempotent, and adapts its analysis depth to the actual data volume. ## Core Features & Use Cases - Checkpoint/Resume Pipeline Stages: Each stage writes atomic JSON checkpoints, skips completed work on re-run, and resumes from partial progress after interruption or failure. - Activity-Based Depth Adjustment: Automatically selects shallow, standard, deep, or archival analysis tiers based on item count instead of hardcoding depth. - Rate-Limit-Aware Fetching: Exponential backoff with jitter for external API calls, plus partial-failure tolerance that logs errors without aborting the pipeline. - Use Case: Processing a large Reddit data export through fetch, parse, enrich, and report stages — if the enrich stage fails after 3 hours, re-running resumes from that stage's checkpoint instead of starting over. ## Quick Start Use the automated-orchestration skill to build a checkpointed pipeline that processes my data archive in resumable stages and writes a status report.

Frequently Asked Questions about automated-orchestration

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

FAQPage Schema
How do I add checkpoint and resume to a Python data pipeline?

Wrap each stage in a class that saves a JSON checkpoint after every N items and on completion, using atomic write-then-rename. On restart, load the checkpoint, skip already-processed item keys, and continue from where the stage stopped.

How to make pipeline stages idempotent so re-runs are safe?

Give each item a unique key (such as an MD5 hash of its content) and record processed keys in the checkpoint. Re-running a completed stage becomes a no-op, and partial re-runs skip items already in the processed set.

How do I handle API rate limits in a long-running fetch job?

Use exponential backoff with jitter: on a rate-limit error, wait base_delay times 2 to the power of the attempt number plus a random fraction, then retry up to a maximum. After max retries, mark the stage degraded and continue with partial data.

What happens if a checkpoint file gets corrupted?

Delete the corrupted checkpoint and re-run that stage from scratch, logging the corruption event. Because stages are idempotent and keyed by item, re-running does not duplicate downstream results.

When should I not use a checkpointed pipeline pattern?

Skip it for single-shot scripts under five minutes with no intermediate state, pipelines where full re-execution is cheap, and real-time streaming workloads, which need event-driven patterns instead of batch checkpoints.