Install
$ agentstack add skill-gertsylvest-meta-team-wasm-pack-build ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
wasm-pack Build
The canonical Rust→WASM build path for browser audio. Builds with wasm-pack against wasm32-unknown-unknown, applies wasm-opt for size and performance, and runs wasm-module-inspect on the output to confirm exports are minimal, SIMD is present, and the module validates.
The flag set is fixed by this skill so every Rust WASM build in the project produces a binary with the same characteristics — no ad-hoc differences between developer machines or CI.
Requirements
- rustup with stable toolchain and the
wasm32-unknown-unknowntarget:
``bash rustup target add wasm32-unknown-unknown ``
- wasm-pack — install via
cargo install wasm-packor from https://rustwasm.github.io/wasm-pack/installer/. - wasm-opt (Binaryen) — install via
brew install binaryen(macOS) orapt install binaryen(Linux). - The
wasm-module-inspectskill from this library (the script invokes it for the final verification step).
What it does
- Verifies prerequisites (
wasm-pack,wasm-opt, target installed). - Sets
RUSTFLAGS="-C target-feature=+simd128"so WASM SIMD is enabled. - Runs
wasm-pack build --target web --release(or--devif--devis passed) on the crate. - Runs
wasm-opt -O3 --enable-simd /_bg.wasm -oto apply Binaryen's optimisation pass over the wasm-bindgen-emitted module. - Invokes
wasm-module-inspecton the optimised.wasm.
Release builds also implicitly use the project's [profile.release] settings — the crate is expected to declare panic = "abort", lto = "fat", codegen-units = 1, opt-level = 3 per the rust-audio-engineer agent's standards.
Instructions
The arguments are in $ARGUMENTS. Pass them directly to the build script:
bash "$(dirname "$0")/build.sh" $ARGUMENTS
Argument 1 is the crate directory. Optional second argument --dev switches to a debug build with source maps for browser debugging.
Output sections
| Section | What it reports | |---|---| | PREREQ | Whether wasm-pack, wasm-opt, and the wasm32 target are present | | BUILD | wasm-pack invocation result | | OPTIMISE | wasm-opt size reduction | | INSPECT | Full output of wasm-module-inspect |
Typical usage
# Release build
bash build.sh ./rust/audio-wasm
# Debug build with DWARF source maps for browser debugging
bash build.sh ./rust/audio-wasm --dev
What to look for
PREREQfailing — the script tells you exactly what to install.BUILDfailing — usually a Rust compile error or a missing[lib] crate-type = ["cdylib", "rlib"]in the crate'sCargo.toml.OPTIMISEshowing no size reduction — wasm-opt may not have anything to do if wasm-pack already optimised aggressively, or LTO already collapsed the dead code. Not necessarily a problem.INSPECTshowing unexpected exports — review the#[wasm_bindgen]and#[no_mangle] extern "C"exports in the Rust source. The worklet should only see the minimal API surface (init,process,destroy, and any control-plane functions).INSPECTshowing no SIMD despite a release build —RUSTFLAGSdid not propagate. Check that the script ran in an environment where it can set env vars, and check the crate does not overrideRUSTFLAGSvia.cargo/config.tomlin a conflicting way.
Why a wrapper instead of raw wasm-pack
The flag set matters: +simd128, --target web, the wasm-opt post-pass, and the inspect step are all easy to forget individually. A wrapper makes the build reproducible across the team and CI without each caller having to remember the recipe.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: gertsylvest
- Source: gertsylvest/meta-team
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.