Individual skill
wasm-pro
Ship WebAssembly modules: compile from Rust/C/C++, JS interop, memory management, threading, and performance patterns. Use when moving hot code to the browser or edge.
skills/wasm-pro/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# WASM Pro
A practical guide to WebAssembly: compiling Rust/C/C++ to wasm, JavaScript interop, linear memory management, multithreading with SharedArrayBuffer, and the performance patterns that make wasm worth it.
## Overview
WebAssembly is a portable, near-native-speed bytecode that runs in browsers (and servers/edge runtimes). The use cases that justify it: **compute-heavy work** (codecs, crypto, physics, image processing), **porting existing native libraries**, and **consistent behavior** across platforms. It's not a faster JavaScript — it's for code where JS genuinely can't keep up or where you need to reuse a battle-tested native codebase.
The core interop model: wasm has linear memory (a big byte array) and exported functions; JS and wasm pass numbers directly and complex data via that shared memory.
## When to use
- Porting a Rust/C/C++ library to the browser (parsers, codecs, compression, crypto).
- Hot loops: physics, simulations, audio/video processing, heavy math.