Create benchmark scenarios for new openzl codec nodes in unitBench.
The material indicates a prompt/documentation-only skill for creating benchmark scenarios, with no required secrets and no declared remote endpoints or local execution capability, so overall risk is low. The main caveat is supply-chain confidence: it is open-source on GitHub, but adoption and maintenance signals are limited.
The material explicitly states that no keys or environment variables are required, and it does not request API tokens, account credentials, or other sensitive authentication data, so credential exposure and misuse risk is low.
No remote endpoints or network services are declared; the content is mainly local benchmark scenario structure and authoring guidance, with no indication that user data is sent to external hosts.
The system flags it as prompt-only, and the material itself is documentation rather than an executable tool interface; although it mentions `dd if=/dev/urandom` as an example for test data, that is documentation content and not evidence that the skill itself gains code-execution privileges.
The material only describes source file locations to edit and a test data location, and does not declare any capability to automatically read, write, or enumerate local files, databases, or system resources; therefore no expanded data-access scope is evident.
The source is an open-source GitHub repository, which materially lowers risk because the code is auditable; however, the license is unspecified, community adoption is 0 stars, maintenance status is unknown, and the README is truncated, so supply-chain trust still warrants manual review.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "unitbench-openzl-scenarios" skill from askskill: 1. Download https://raw.githubusercontent.com/facebook/openzl/dev/.claude/skills/unitbench-scenarios/SKILL.md 2. Save it as ~/.claude/skills/unitbench-scenarios/SKILL.md 3. Reload skills and tell me it's ready
Create a kernel-level encode benchmark scenario for a new openzl bitsplit codec node in unitBench. Include the test name, input data patterns, parameter configuration, warmup and iteration settings, and throughput/latency metrics, while matching the style of existing scenarios.
A draft kernel-level encode benchmark scenario for unitBench with key configuration and metric definitions.
Design a graph-level compress/decompress benchmark scenario in unitBench for an openzl delta + entropy node chain. Cover the compression path, decompression path, input sample types, correctness validation, and compression ratio/performance metrics.
A graph-level compression and decompression benchmark scenario outlining flow, validation, and output metrics.
I added a new openzl transpose codec node. Generate benchmark scenarios following existing unitBench conventions, including kernel-level encode/decode tests and optional graph-level compress/decompress test recommendations.
A set of benchmark scenario recommendations aligned with current conventions, covering kernel-level and graph-level testing.
Create benchmark scenarios for openzl codec nodes. Two benchmark types exist: kernel (test encode/decode kernel functions directly) and graph (test a node within a full compress/decompress pipeline).
Before creating scenarios, ask the user:
Does this node have a standalone kernel function? (e.g., ZL_bitSplitEncode, ZL_bitSplitDecode)
Should the node be tested in a graph?
What data types/widths does the node operate on?
| What | Where |
|---|---|
| Kernel benchmarks | benchmark/unitBench/scenarios/codecs/<name>.c and .h |
| Graph benchmarks | benchmark/unitBench/scenarios/<name>_graph.c and .h |
| Scenario registration | benchmark/unitBench/benchList.h |
| BUCK file | benchmark/unitBench/BUCK |
| Test data | /tmp/ (use dd if=/dev/urandom) |
All paths relative to the openzl dev root.
Test encode/decode kernel functions directly. Requires a standalone kernel API.
.h)Add declarations to existing scenarios/codecs/<codec>.h or create a new one:
// Decode
size_t <codec>Decode_<type>_prep(void* src, size_t srcSize, const BenchPayload* bp);
size_t <codec>Decode_<type>_outSize(const void* src, size_t srcSize);
size_t <codec>Decode_<type>_wrapper(const void* src, size_t srcSize, void* dst, size_t dstCapacity, void* customPayload);
// Encode
size_t <codec>Encode_<type>_prep(void* src, size_t srcSize, const BenchPayload* bp);
size_t <codec>Encode_<type>_outSize(const void* src, size_t srcSize);
size_t <codec>Encode_<type>_wrapper(const void* src, size_t srcSize, void* dst, size_t dstCapacity, void* customPayload);
.c)Decode scenario: prep packs split streams contiguously into src, wrapper recomputes pointers and calls the decode kernel, outSize returns (srcSize / sumSrcElt) * dstEltWidth.
Encode scenario: prep fills src with random values, wrapper calls the encode kernel writing streams contiguously into dst, outSize returns (srcSize / srcEltWidth) * sumDstElt.
Reference implementation: See scenarios/codecs/bitSplit.c for the complete pattern with multiple data type examples.
Test a node within a full compress/decompress graph. Required when no standalone kernel exists. Also useful alongside kernel benchmarks to measure graph overhead.
.h)// Copyright (c) Meta Platforms, Inc. and affiliates.
#ifndef GUARD_MACRO_H
#define GUARD_MACRO_H
#include "openzl/shared/portability.h"
#include "openzl/zl_compressor.h"
ZL_BEGIN_C_DECLS
ZL_GraphID <name>_graph(ZL_Compressor* cgraph);
ZL_END_C_DECLS
#endif
.c)Build the graph using ZL_Compressor_registerStaticGraph_fromNode1o. Typical pattern: tokenize input -> apply node -> downstream graph.
#include "openzl/codecs/zl_<codec>.h" // ZL_NODE_<YOUR_NODE>
#include "openzl/zl_compressor.h"
#include "openzl/zl_public_nodes.h" // ZL_NODE_INTERPRET_AS_LE*
ZL_GraphID my_graph(ZL_Compressor* cgraph)
{
if (ZL_isError(ZL_Compressor_setParameter(
cgraph, ZL_CParam_formatVersion, ZL_MAX_FORMAT_VERSION))) {
abort();
}
if (ZL_isError(ZL_Compressor_setParameter(
cgraph, ZL_CParam_compressionLevel, 1))) {
abort();
}
return ZL_Compressor_registerStaticGraph_fromNode1o(
cgraph,
…
Design, modify, and review OpenZL codecs with consistent patterns and requirements.
Create and maintain design docs for the OpenZL component registry.
Get idiomatic Relay guidance for React code, debugging, and code reviews.
Write and run Markdown-driven end-to-end tests for Relay apps.
Debug Pysa false negatives by comparing outputs and locating lost taint flows.
Understand the Pyre/Pysa architecture and locate key implementations quickly.