data-throughput-accelerator

Accelerate large data ingestion and warehouse loading pipelines with checkpointing and manifests.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/sakamoto-family-smile/agent_monorepo --skill data-throughput-accelerator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: data-throughput-accelerator
Source: https://github.com/sakamoto-family-smile/agent_monorepo/tree/main/.claude/skills/ecc/data-throughput-accelerator
Command: npx skills add https://github.com/sakamoto-family-smile/agent_monorepo --skill data-throughput-accelerator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when the bottleneck is moving, transforming, or saving lots of data. The goal is not just speed; the goal is faster, correct data landing in the right place with verifiable proof.

Core Features & Use Cases

  • Fast path heuristics: Move compute to where the data already is; prefer warehouse-native scans, joins, and appends for large landed files; use manifests or checkpoints to skip completed files/partitions; apply partitioning and clustering that match reads and writes; batch small files and requests; ensure writes are idempotent through unique keys, manifests, or replaceable staging.
  • Workflow transparency: Measure backlog, run safe catch-up benchmarks, compare variants, and promote the fastest path while maintaining manifest counts and max timestamps.
  • Guardrails & accounting: Preserve raw data, avoid silent failures, and keep explicit accounting blocks to prove correctness.

Quick Start

Run the throughput accelerator on a backlog to measure backlog and initiate a safe catch-up workflow.

Frequently Asked Questions about data-throughput-accelerator

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

FAQPage Schema
How do I speed up large data ingestion and warehouse loading pipelines without sacrificing data correctness?

Large data ingestion pipelines can be accelerated using fast path heuristics like manifest-based processing, checkpointing, and idempotent writes to ensure verifiable data landing. This approach moves compute to the data and batches small files for speed.

What is the best way to run a manifest-based backfill on a data lake safely?

A manifest-based backfill skips completed files or partitions to safely catch up on data lake workloads. It relies on deterministic execution and explicit accounting blocks to avoid silent failures and preserve raw data during the catch-up process.

How do I ensure idempotent writes during ETL table synchronization?

Idempotent writes during ETL table synchronization are ensured by using unique keys, processing manifests, or replaceable staging tables. This prevents duplicate records and maintains strong data correctness when re-running failed pipeline tasks.

How does checkpointing work for skipping completed files in ETL workloads?

Checkpointing in ETL workloads tracks completed files and partitions via manifests or max timestamps, allowing the pipeline to skip them on reruns. This reduces redundant processing and accelerates backlog measurement during catch-up.

What are the limitations of using fast path heuristics for data throughput acceleration?

Fast path heuristics for data throughput require matching partitioning and clustering to read and write patterns to be effective. Without explicit accounting blocks and raw data preservation, rapid warehouse loading might mask silent failures or data correctness issues.