Skip to main content
Agent skill

Data Throughput Accelerator

Diagnose and accelerate large data movement — ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, and table synchronization — by isolating the true bottleneck, benchmarking variants, and codifying the fastest path with a hard accounting block proving rows and timestamps cohere. Use when a pipeline or backfill is too slow and must get faster without losing data correctness.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Data Throughput Accelerator when an AI agent needs a reusable SKILL.md workflow for this job: Diagnose and accelerate large data movement — ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, and table synchronization — by isolating the true bottleneck, benchmarking variants, and codifying the fastest path with a hard accounting block proving rows and timestamps cohere. Use when a pipeline or backfill is too slow and must get faster without losing data correctness.

When not to use it

Skip Data Throughput Accelerator when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/data-throughput-accelerator
# Save SKILL.md to ~/.claude/skills/data-throughput-accelerator/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/data-throughput-accelerator/SKILL.md. For a shared project, commit the folder at .claude/skills/data-throughput-accelerator/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Data Throughput Accelerator skill for this task: Read the current source, target, and manifest contracts. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
82/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Data Throughput Accelerator

Use this skill 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 proof.

## First Distinction

Separate these before optimizing:

- source extraction speed; - network transfer speed; - warehouse/load speed; - transform speed; - serving-table freshness; - live tail growth while the job runs.

A pipeline can be "fast" and still appear behind if new data arrives faster than the final catch-up window.

## 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 so completed files/partitions are skipped. - Use partitioning and clustering that match the read and append pattern. - Batch small files, requests, and writes. - Make writes idempotent through unique keys, manifests, or replaceable staging. - Keep raw, derived, and serving tables separately accountable.

## Workflow

1. Read the current source, target, and manifest contracts. 2. Measure backlog: external files, manifest rows, raw rows, derived rows, min/max timestamps, and unprocessed counts. 3. Run a safe catch-up or sample benchmark. 4. Compare variants: batch size, worker count, warehouse SQL, file grouping, staging shape, and manifest update method. 5. Promote only the fastest path that keeps counts and timestamps coherent. 6. Codify the path as a CLI, scheduled job, workflow, or runbook. 7. Rerun final accounting after the codified path executes.

## Accounting Output

Use a hard accounting block:

```text Data throughput result: - Source files discovered: 294 - Files processed this run: 294 - Raw rows added: 9,683,598 - Derived rows added: 8,917,585 - Remaining tail: 24 files at readback time - Runtime: 38.7s - Correctness gate: manifest counts and table max timestamps match ```

## Guardrails

- Do not delete raw data to make a metric look better. - Do not skip failed files silently. - Do not mix historical backfill status with live-tail freshness. - Do not call a pipeline complete until the target tables and manifest agree. - For finance, healthcare, regulated, or customer-impacting data, preserve replay evidence and approval gates.

Intended uses

  • Read the current source, target, and manifest contracts.
  • Measure backlog: external files, manifest rows, raw rows, derived rows,
  • Run a safe catch-up or sample benchmark.
  • Compare variants: batch size, worker count, warehouse SQL, file grouping,
  • Promote only the fastest path that keeps counts and timestamps coherent.
  • Codify the path as a CLI, scheduled job, workflow, or runbook.
  • Rerun final accounting after the codified path executes.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.