dask

combined

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars. Scales pandas, NumPy, and custom Python research workflows beyond memory or across clusters with Dask. Covers DataFrames, Arrays, Bags, Futures, chunking, schedulers, and distributed diagnostics. Use for partitioned file processing, scientific array computation, or parallel tasks whose memory and dependency structure require Dask.

When to use

Process datasets that exceed available RAM
Scale pandas or NumPy operations to larger datasets
Parallelize computations for performance improvements
Process multiple files efficiently (CSVs, Parquet, JSON, text logs)
Build custom parallel workflows with task dependencies
Distribute workloads across multiple cores or machines

When not to use

out-of-core analytics on single machine
in-memory speed

Skill page

Conflict

The three copies share the same core Dask structure (DataFrames, Arrays, Bags, Futures) and the same high-level guidance, but they disagree on concrete parameters and add different constraints. K-Dense-AI/scientific-agent-skills pins dask 2026.8.0, requires Python 3.10+, pandas 2+, PyArrow 16+, and states that since 2025.1.0 the expression-based DataFrame API is the only implementation (do not install dask-expr or disable query planning). It also uses a small, memory-safe array example and a more specific DataFrame groupby example. The other two copies use a much larger array example (100000x100000) and a simpler groupby example, and they include a laptop-to-cluster capacity line that the K-Dense copy omits. FreedomIntelligence/OpenClaw-Medical-Skills adds a tool-selection note (use vaex for out-of-core single-machine analytics, polars for in-memory speed) that the others lack. Because each copy has material steps or constraints the others lack, and they disagree on version pinning and example sizing, crowning one would hide real alternatives.