Agent skill · nvidia
cudf-query-engine-builder
Build the first native, single-GPU cuDF path in a query engine, or complete its initial adapter. Use for libcudf C++ or cuDF Java implementation, buffer ownership, worker readiness and CPU/reference comparison, including identifying missing POC inputs. Excludes standalone dataframe analysis, cuDF mainline changes, production integration and distributed or multi-GPU execution. Bundled maintainer evaluations use CPU simulations and source review; they do not run CUDA.
What it needs
About 6k tokens when loaded.
What this skill does
cuDF query-engine POC builder Outcome and scope Build the first native cuDF proof of concept in the target engine for a query-engine engineer. Produce working target-engine code, a runnable single-GPU program, and a correctness result, not only advice. The POC may cover one operator, a sequence of operators, or a query selected for the POC. Do not reduce it to one operator by default. If a smaller increment is needed for feasibility or safe implementation, explain why and preserve the path to the requested POC. For a request limited to an initial adapter correction or source review, deliver that requested work and state which build, native execution and comparison steps remain unperformed. Source review and CPU simulation cannot establish acceptance of the native POC. Gather inputs and choose sources Before editing, identify: the target engine or adapter code and build entry point; the data source or fixture, its schema, and how the engine reads it today (its own scan layer, or none); the query, operator sequence, or CPU implementation; the expected output or CPU/reference result and target-engine semantics; and the target-engine language, any existing libcudf C++ or cuDF Java integration code, and the cuDF version when identifiable from the code or build environment. Determine the cuDF entry and exit interfaces from the supplied engine code. Define schema conversion, buffer ownership and release, lifetime, and producer/consumer readiness as part of the POC. Ask the engineer only when the code and tests cannot establish a required choice. Ask only when a missing input changes the code, correctness, safety, or ability to build and run. Gather only the environment facts needed for this POC. If the supplied query, CPU behavior, target-engine semantics, and expected result disagree, ask which behavior controls. Do not choose silently. Use target-engine code and tests, installed public headers, and version-matched official cuDF documentation and source. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/cudf-query-engine-builder