cuda-webdoc-search
Original:🇺🇸 English
Translated
12 scripts
Search CUDA-X library documentation (cuBLAS, cuTENSOR, cuTensorNet, cuSOLVER, etc.) to find API symbols, functions, and types. Use when you need to look up CUDA library APIs, discover available functions, or find documentation URLs for specific operations.
5installs
Sourceultimatile/cuda-x-skills
Added on
NPX Install
npx skill4agent add ultimatile/cuda-x-skills cuda-webdoc-searchTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →CUDA-X Documentation Search Guide
Overview
Search and discover APIs across CUDA-X library documentation by querying Sphinx inventory files. Use this skill when you need to find specific CUDA library functions, check available APIs, or get documentation links.
Setup
bash
uv tool install "cuda-webdoc-search @ git+https://github.com/ultimatile/cuda-x-skills.git#subdirectory=skills/cuda-webdoc-search"After installation, is available as a standalone command. For one-shot usage without installing:
cwsbash
uvx --from "cuda-webdoc-search @ git+https://github.com/ultimatile/cuda-x-skills.git#subdirectory=skills/cuda-webdoc-search" cws search cublas --statsWhen to Use
- Finding CUDA library APIs (e.g., "what SVD functions does cuTensorNet have?")
- Checking if a specific function exists in a library
- Getting documentation URLs for CUDA APIs
- Exploring available operations in a library
Quick Reference
Check Available Domains First
Before searching, check what domains (API types) are available:
bash
cws search <library> --statsThis returns domain counts: (C++ APIs), (C APIs), (Python bindings), (doc labels).
cppcpystdSearch for APIs
bash
cws search <library> --domains <domain> --keywords "<terms>" --fuzzy --limit 20Keyword Syntax (fzf subset)
- Space-separated terms are AND (all must match):
--keywords "SVD batch" - Use for OR (requires shell quoting):
|--keywords "SVD | QR" - AND binds tighter than OR: = (a AND b) OR c
--keywords "a b | c" - Note: Only AND/OR via is supported. fzf operators
|,^,',!are not available.$
Available Libraries
See for the full list. Common ones:
registry.toml- - cuTensorNet, cuStateVec (quantum/tensor network)
cuquantum - - BLAS operations
cublas - - Dense/sparse solvers
cusolver - - Sparse matrix operations
cusparse - - FFT operations
cufft - - Deep learning primitives
cudnn - - GEMM templates
cutlass - - Math functions
cuda_math
Workflow
- Identify the library: Determine which CUDA library likely contains the API
- Check domains: Run to see available domain types
--stats - Search: Use with
--keywordsfor flexible matching--fuzzy - Filter by domain: Use for C++ APIs,
--domains cppfor C APIs--domains c - Extract details: Use to get full documentation content
cws get
Examples
Find tensor decomposition APIs in cuTensorNet
bash
cws search cuquantum --stats
# Shows: cpp:3179, py:1172, std:3378, c:4
cws search cuquantum --domains cpp --keywords "SVD" --fuzzy --limit 10
# Returns: cutensornetTensorSVD, etc. (functions ranked above enumerators)
cws search cuquantum --domains cpp --keywords "SVD | QR" --fuzzy
# Returns: entries matching SVD OR QRSearch across multiple libraries
bash
# "Where is SVD in CUDA-X?" — search cuSOLVER and cuDSS together
cws search cusolver cudss --keywords "svd" --fuzzy --limit 10
# Mix any number of sources
cws search cusolver cusparse cudss --keywords "solve" --fuzzyMulti-source output uses (list) instead of (string), and becomes a per-source dict.
"sources""source""total_found"Find GEMM functions in cuBLAS
bash
cws search cublas --stats
# Shows: std:36 (only doc labels, no cpp/c domain)
cws search cublas --domains std --keywords "gemm"
# Returns: cublas-t-gemm, cublas-t-gemmex, etc. (doc section labels)Extract API documentation details
After finding a function URL, extract its full documentation:
bash
cws get <url> --section <function_name>Example:
bash
cws get \
"https://docs.nvidia.com/cuda/cuquantum/latest/cutensornet/api/functions.html" \
--section "cutensornetTensorSVD"Output is a brace-delimited text tree:
{
cutensornetTensorSVD
{
cutensornetStatus_t cutensornetTensorSVD {
const cutensornetHandle_t handle
const cutensornetTensorDescriptor_t descTensorIn
...
}
Performs SVD decomposition of a tensor. { ... }
Parameters { ... }
}
}List available sources
bash
cws list # table format
cws list --json # JSON formatAudit registry health
bash
cws audit # audit all sources
cws audit --source cublas # audit single sourceOutput Format
cws search
JSON output includes:
Single source:
- : Library name (string)
source - : Total APIs in filtered domains
total_found - : APIs matching keywords
filtered_count - : List of matching APIs with
candidates(name),group,url,domainrole
Multi-source ():
cws search A B- : Library names (list)
sources - : Per-source totals (dict)
total_found - : Total APIs matching keywords across all sources
filtered_count - : Merged list (k-way merge by score if
candidates, else concatenated)--fuzzy
cws get
Brace-delimited text tree where:
{denote hierarchy}- Text content is preserved
- Inline elements (code, links) are flattened to text
Options:
- : Extract only a specific section
--section <id> - : Extract only the main content area
--main-only
Files
- - Unified CLI entry point (
cli.py)cws - - Search APIs across library inventories
search.py - - Audit registry entries for endpoint health
audit.py - - Extract documentation content as text tree
get.py - - Data fetching for Sphinx/Doxygen sources
fetchers.py - - Search ranking and filtering logic
scoring.py - - Registry loading utility
registry.py - - Library metadata (URLs, doc types)
registry.toml