data-throughput-accelerator
Skill1 starsChanged 4 months agoMITView on GitHub
Use when large data ingestion, backfill, export, ETL, warehouse loading, manifest catch-up, or table synchronization needs to become much faster while preserving data correctness.
4 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- AndresArreguy/ecc-pi-portedited, first seen Nov 16, 2026
- renepf/claude-skillsedited, first seen Oct 25, 2026
- davidanthonyn/claude-skillsword for word, first seen Oct 20, 2026
- gongyijie85/dsh-eccedited, first seen Oct 13, 2026
Other versions4 projects use a version of this.
Word for word · 1
- davidanthonyn/claude-skills★ 0100% same
Edited · 3
- gongyijie85/dsh-ecc★ 898% same
- AndresArreguy/ecc-pi-port★ 186% same
- renepf/claude-skills★ 099% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository280 other files it gives its agents.
- agent-architecture-auditSkill
- agent-evalSkill
- agent-harness-constructionSkill
- agentic-engineeringSkill
- agentic-osSkill
- agent-introspection-debuggingSkill
- agent-payment-x402Skill
- agent-sortSkill
- ai-first-engineeringSkill
- ai-regression-testingSkill
- autonomous-agent-harnessSkill
- autonomous-loopsSkill
- braindump-autoSkill
- braindumpSkill
- continuous-agent-loopSkill
- continuous-learning-v2Skill
- data-scraper-agentSkill
- enterprise-agent-opsSkill
- eval-harnessSkill
- foundation-models-on-deviceSkill
- ito-data-atlas-agentSkill
- llm-trading-agent-securitySkill
- mcp-server-patternsSkill
- mle-workflowSkill
- recsys-pipeline-architectSkill
- regex-vs-llm-structured-textSkill
- scholar-evaluationSkill
- superbraindumpSkill
- team-agent-orchestrationSkill
- carrier-relationship-managementSkill
- customer-billing-opsSkill
- energy-procurementSkill
- finance-billing-opsSkill
- inventory-demand-planningSkill
- logistics-exception-managementSkill
- prediction-market-oracle-researchSkill
- prediction-market-risk-reviewSkill
- production-schedulingSkill
- quality-nonconformanceSkill
- returns-reverse-logisticsSkill
- architecture-decision-recordsSkill
- codebase-onboardingSkill
- codehealth-mcpSkill
- code-tourSkill
- hexagonal-architectureSkill
- repo-scanSkill
- article-writingSkill
- brand-voiceSkill
- content-engineSkill
- crosspostSkill
- investor-materialsSkill
- investor-outreachSkill
- lead-intelligenceSkill
- marketing-campaignSkill
- market-researchSkill
- seoSkill
- social-publisherSkill
- x-apiSkill
- bun-runtimeSkill
- cisco-ios-patternsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. 12 are common, 0 are distinctive, and 0 are very specific to this project.
12
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 10
Use this skill when the bottleneck is moving, transforming, or saving lots of data.
- Common: line 31
Prefer warehouse-native scans, joins, and appends for large landed files.
- Common: line 32
Use manifests or checkpoints so completed files/partitions are skipped.
- Common: line 33
Use partitioning and clustering that match the read and append pattern.
- Common: line 36
Keep raw, derived, and serving tables separately accountable.
- Common: line 40
Read the current source, target, and manifest contracts.
- Common: line 43
Run a safe catch-up or sample benchmark.
- Common: line 52
Use a hard accounting block:
- Common: line 67
Do not delete raw data to make a metric look better.
- Common: line 68
Do not skip failed files silently.
- Common: line 69
Do not mix historical backfill status with live-tail freshness.
- Common: line 70
Do not call a pipeline complete until the target tables and manifest agree.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Read the current source, target, and manifest contracts.
- Measure backlog: external files, manifest rows, raw rows, derived rows, min/max timestamps, and unprocessed counts.
- Run a safe catch-up or sample benchmark.
- Compare variants: batch size, worker count, warehouse SQL, file grouping, staging shape, and manifest update method.
- 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.
Accounting Output
Use a hard accounting block:
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 matchGuardrails
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

