What problem does it solve? Running the KX NYSE TAQ benchmark suite involves a strict four-step pipeline (selecting a data size, downloading PSV files, generating kdb+/Parquet databases, and executing benchmark scripts) where skipping or misordering steps causes confusing failures. This Skill guides the workflow end-to-end, including reusing already-generated data to avoid repeating slow downloads. ## Core Features & Use Cases - Guided four-step workflow: Walks through SIZE selection, PSV download via getPSVs.sh, kdb+/Parquet database generation via generateDB.sh, and benchmark execution via queryEngines.sh or kdbAttributes.sh. - Engine and format mapping: Matches engine subsets (kdb, kdbxsql, pykx, duckdb, chdb, polars, pandas) to the required database format so only the necessary binaries are generated. - Data reuse detection: Checks ${NYSEBENCHMARKDIR}/${SIZE} for existing kdb and Parquet directories so users can re-run queries with different thread counts or query filters without regenerating data. - Results interpretation: Explains the results.psv columns (run times, memory, status, threadcount) and troubleshooting for common failures like missing submodules or OOM on Community Edition. - Use Case: A performance engineer wants to compare DuckDB and KDB-X query latency on TAQ data at medium size with 4 and 16 threads; the Skill verifies prerequisites, generates both database formats, runs the benchmark, and explains the warm-run timing columns. ## Quick Start Ask the assistant to run the NYSE TAQ benchmark at small size comparing KDB-X and DuckDB with 4 and 16 threads, reusing any data already on disk.