Cudf Query Engine Builder

NVIDIAOfficialCreated by Joe SackDistributed by NVIDIA

Skill
Workflow
Software development
Apache-2.0
Medium risk
Has scripts

From the author

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.

— the description by Joe Sack

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured workflow for query-engine engineers to integrate cuDF into their existing systems. It focuses on building a functional, single-GPU proof of concept (POC) that demonstrates native execution, correct buffer management, and proper asynchronous cleanup. The process emphasizes maintaining clear boundaries between the engine's orchestration responsibilities and cuDF's device-wide algorithms, ensuring that memory ownership, lifetime management, and producer-consumer dependencies are handled safely.

What it does

Maps query engine semantics to version-matched cuDF APIs.
Defines buffer ownership, lifetime, and release strategies for GPU data.
Implements adapter glue code to bridge the engine and libcudf or cuDF Java.
Establishes correct asynchronous execution patterns and completion synchronization.
Validates POC correctness against CPU-based reference implementations.
Provides a framework for reporting native execution evidence and identifying blockers.

When to use it

When you need to integrate cuDF into a query engine for the first time.
When developing a new native adapter for libcudf C++ or cuDF Java.
When you need to resolve buffer ownership or asynchronous cleanup issues in an existing integration.
When you need to verify that a query engine is correctly offloading work to a single GPU.

Advantages

Ensures safe memory management and exception handling in asynchronous GPU workflows.
Maintains separation of concerns between engine orchestration and cuDF algorithms.
Provides a clear path for validating native execution versus CPU simulations.
Reduces integration risks by focusing on incremental, verifiable POCs.

Usage examples

“Build a POC for a single-GPU filter operator in our C++ query engine using libcudf.”: The agent will guide you through mapping the filter semantics to cuDF, implementing the adapter glue, managing the buffer ownership, and verifying the result against your CPU reference implementation.
“How do I safely handle buffer cleanup in my cuDF adapter when an asynchronous call might throw?”: The agent will provide a pattern for retaining owners outside of throwing scopes and establishing completion before releasing resources, as detailed in the asynchronous cleanup guidelines.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/cudf-query-engine-builder/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip cudf-query-engine-builder.zip -d .agents/skills

Documentation by Joe Sack

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. Treat partner discussions as problem signals, not technical authority.

Build the POC

Establish the named CPU or reference result. Run the reference implementation when it is executable.
Map the requested semantics to public, version-matched cuDF APIs. Handle relevant null, type, order, error, ownership, lifetime, and stream behavior. When native calls can leave GPU work pending, read cleanup after asynchronous work before implementing ownership and exception paths.
Implement the requested operators and minimal engine or adapter glue without changing cuDF mainline. If the required public cuDF API is missing, preserve any buildable engine-side work, document the smallest cuDF gap, and report BLOCKED when the POC cannot proceed safely.
Build a runnable program and execute the workload on one GPU. Record exact commands and working directories.
State the applicable row-order handling, null and type equality, and floating-point tolerance before comparing the output with the named CPU or reference result.
Fix evidenced defects, then rebuild, rerun, and recompare. Continue until the checks pass or a named blocker remains. Report unsafe boundaries, missing prerequisites, unresolved semantics, and larger engine changes.

Before accepting an asynchronous path, inspect every operation that can throw after submission, including native calls, output allocation and result-wrapper construction. C++ destroys objects declared inside a try block before entering its catch handler: a wait in that handler cannot protect those destroyed owners. Keep input, intermediate and output owners outside the throwing scope, and establish completion before releasing them on failure. On success, wait after the last queued operation, including a device-to-host copy, before the caller reads the result. A wait before the copy does not make its destination ready.

Honor the supplied caller's completion promise even when filtering produces no rows. An empty result can still follow queued work or depend on input readiness. For a result handed between workers, retain its buffer, stream and resource owners and establish the producer-to-consumer dependency. Follow the ownership patterns and validation steps in cleanup after asynchronous work.

Exercise a recoverable allocation failure while work is pending, assert that no owner is released early, and check a subsequent valid call when the engine promises recovery. Treat a failed ownership or readiness check as a failed POC even when normal output values match.

If a required codebase, toolchain, compatible cuDF runtime, GPU, or reference result is unavailable and prevents a required step, report BLOCKED, name the missing prerequisite, preserve completed work, and give the exact next command or check. Do not report the blocked step as run or passed.

POC acceptance criteria and handoff

POC passes only when the source change builds, the program exits successfully, its output matches the named CPU or reference result under the stated comparison policy, and a reliable engine signal or runtime observation confirms that the requested result-producing work ran through cuDF.

Report the native-execution evidence separately from numerical agreement. If reliable confirmation is unavailable, mark native execution unresolved and do not report an overall POC pass. Do not infer native execution from GPU availability or elapsed time. A profiler is not required when another reliable engine signal or runtime observation establishes native cuDF execution.

Return:

the patch and runnable program path;
exact build and run commands with their working directories;
the inputs, selected binding and cuDF version, named CPU or reference result, comparison policy, and observed result;
any available cuDF-path observation; and
unresolved questions and larger engine work, with facts separated from inference.

Keep cuDF and engine responsibilities separate

cuDF provides device-wide algorithms for one GPU. The engine owns query-plan and pipeline orchestration, spill, production fallback, multi-GPU coordination, and distributed execution.

I/O sits on the boundary, and the POC must pick one of two paths and say which. cuDF ships data sources that read local files, remote files, and remote objects directly. The engine can either pass cuDF a path or data source and let cuDF perform the read, or keep its own I/O stack and hand cuDF the bytes in host buffers, usually pinned. Choose the path that matches the supplied engine code: if the engine already has a scan or storage layer that produces host buffers, feed those buffers to cuDF; if it does not, use a cuDF data source. Record the choice, the buffer type (pinned or pageable), and who frees each buffer in the handoff. Caching, prefetch, retries, credentials, and format negotiation stay with the engine and are out of scope.

Write the engine or adapter code needed for the requested POC, including who owns and releases each buffer and how consumers wait for producer work to complete. Report larger engine work separately; do not implement it in the POC.

Performance and profiling

Profiling is optional for an initial POC and is never a blocker: if Nsight Systems cannot be installed or run, report that and continue. When it is available, capture one nsys profile of the run and check that the GPU is busy in the timed region. Report idle gaps, host-side stalls, and synchronous copies; do not fix them in the POC unless asked. Preserve the exact run command and workload inputs so the run can be profiled later.

When performance work is requested, profiling belongs in the same tuning loop. Benchmark the same logical work under stated conditions. Obvious code changes may be validated with benchmark results, but broader diagnosis and performance claims require profile evidence. If profiling cannot run, report the blocker rather than inferring bottlenecks from code alone.

A GPU result that remains slower than the CPU result is not automatically a failed POC. Preserve the implementation and report the measurements, profile evidence collected, observed bottlenecks, and remaining engine work.

Evaluation files

The evals/ directory is for maintainers evaluating this skill. It contains incomplete adapter starters and CPU models used to test host ownership and readiness; these are not cuDF implementations or native-execution evidence. Do not run these fixtures as part of an engineer's POC unless the user requested skill evaluation. Read evals/EVAL.md before evaluating them and use its isolated execution procedure.

Files

ATTRIBUTION.mdAdded by AutoGineer977 B
BENCHMARK.md10.7 KiB
LICENSE29.8 KiB
LICENSE-APACHE11.2 KiB
LICENSE-CC-BY-4.018.3 KiB
SKILL.md9.1 KiB
THIRD_PARTY_NOTICES.md3.2 KiB
evals/.reference/Dockerfile.cudf-cpp272 B
evals/EVAL.md7.4 KiB
evals/config.yml505 B
evals/evals.json19.7 KiB
evals/files/async-copy-cleanup/TASK.md3.1 KiB
evals/files/async-copy-cleanup/adapter.hpp683 B
evals/files/async-copy-cleanup/run_checks.pyScript4.9 KiB
evals/files/async-copy-cleanup/sim_backend.hpp6.2 KiB
evals/files/async-copy-cleanup/test_adapter.cpp3.6 KiB
evals/files/worker-result-handoff/TASK.md3.3 KiB
evals/files/worker-result-handoff/adapter.hpp1.4 KiB
evals/files/worker-result-handoff/run_checks.pyScript4.9 KiB
evals/files/worker-result-handoff/sim_backend.hpp6.2 KiB
evals/files/worker-result-handoff/test_adapter.cpp4.1 KiB
evals/grader.pyScript11.4 KiB
references/asynchronous-cleanup.md7.7 KiB
skill-card.md5.1 KiB
skill.oms.sig9.1 KiB

LICENSE-APACHE

Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs Python

Security

What our scanner noticed· Medium risk

Large base64-encoded blobs
Scripts that your agent may run

This skill includes scripts that your agent may run. Read them before you use it.

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by

Joe Sack

Publisher

NVIDIA (Official)

Distributed by

NVIDIA

Source

NVIDIA/skills · skills/cudf-query-engine-builder · commit fce3cca

Licence

Apache License 2.0 (redistribution allowed)

ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

AutoGineer is not affiliated with or endorsed by Joe Sack or NVIDIA.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download cudf-query-engine-builder.zip