module-context

Loads relevant cudf, rmm, duckdb, and cucascade API documentation based on task keywords.

1.1k|121|Updated Jun 19, 2024
One-click install
npx skills add https://github.com/sirius-db/sirius --skill module-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: module-context
Source: https://github.com/sirius-db/sirius/tree/main/.claude/skills/module-context
Command: npx skills add https://github.com/sirius-db/sirius --skill module-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When implementing GPU operators or fixing bugs in the Sirius GPU SQL engine, developers often lack accurate knowledge of dependency library APIs (cudf, rmm, duckdb, cucascade), leading to incorrect signatures, missed usage patterns, and version incompatibilities.

Core Features & Use Cases

  • Task-to-Module Routing: Analyzes a task description against keyword mappings (joins, aggregations, sorting, memory management, pipelines, I/O) to identify which library modules are relevant.
  • API Documentation Loading: Reads pre-generated per-module docs containing signatures, descriptions, and existing usage examples from the codebase.
  • Structured Context Output: Produces a context block listing loaded modules, key APIs with existing usage patterns, and gap flags for unused or missing functionality.
  • Use Case: When asked to implement a new hash join operator, the skill loads cudf/join, duckdb/planner, rmm/cuda_streams, and cucascade/data docs so the implementing agent follows established patterns.

Quick Start

Ask the assistant to implement a GPU aggregation operator and it will automatically load the relevant cudf, rmm, and duckdb module documentation before writing code.

Frequently Asked Questions about module-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right cudf API for implementing a GPU operator?

Describe your task using keywords like join, aggregate, sort, or filter, and the skill maps them to the relevant cudf module docs. It loads API signatures plus existing usage examples from the Sirius codebase so you follow established patterns.

How to load duckdb and rmm documentation before writing Sirius code?

The skill automatically selects 3-6 relevant modules across duckdb, rmm, cudf, and cucascade based on your task description. It reads the pre-generated module docs and presents key APIs with file and line references to existing call sites.

Does the skill cover cudf version differences between releases?

Yes, the skill surfaces version gotchas when loading APIs that differ between cudf 25.04 and 26.04+. It explicitly notes version-conditional behavior in the structured context output.

What happens when a task needs functionality not in any documented module?

The skill flags the gap explicitly in its output. If the functionality exists in an unused module it suggests loading those docs; if it exists nowhere, it reports that the capability is missing from the documented libraries.

Which libraries are covered by the module documentation?

The docs cover cudf (25 modules), rmm (17 modules), duckdb (13 modules), cucascade (3 modules), and libkvikio (7 modules). Each library has a README module map plus per-module API references with usage examples.