skills.rest
lewing
lewingCOMMUNITY
Explore all skills by this author →
𝕏@lewingGitHub

wasm-binary-analysis

Analyze WebAssembly binaries from .NET builds to verify SIMD and diagnose regressions.

4|1|Updated Feb 19, 2026
Search Tags:#dotnet#wasm#webassembly#simd#binary-analysis#wasm-objdump
One-click install
npx skills add https://github.com/lewing/agent-plugins --skill wasm-binary-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wasm-binary-analysis
Source: https://github.com/lewing/agent-plugins/tree/main/plugins/dotnet-performance/skills/wasm-binary-analysis
Command: npx skills add https://github.com/lewing/agent-plugins --skill wasm-binary-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze WebAssembly binaries from .NET WASM builds to verify SIMD presence, compare versions, and diagnose regressions at the binary level.

Core Features & Use Cases

  • Compare dotnet.native.wasm across runtime packs to detect SIMD changes and file size differences.
  • Inspect disassembly with wasm-objdump to quantify SIMD usage and track execution-mode differences.
  • Use in regression workflows to surface binary-level anomalies between builds.

Quick Start

Run a quick comparison between two wasm binaries to surface SIMD counts and size differences.

Frequently Asked Questions about wasm-binary-analysis

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

FAQPage Schema
How do I check for SIMD instructions in a .NET WebAssembly binary?▼

You can verify SIMD presence in .NET WASM binaries by using wasm-objdump to inspect disassembly and count v128 instructions within the dotnet.native.wasm file across different runtime packs.

What is the best way to compare .NET WASM binaries for size regressions?▼

Comparing dotnet.native.wasm across different runtime packs allows you to detect file size differences and surface binary-level anomalies, making it effective for diagnosing .NET WASM size regressions.

Why does my .NET WASM build show different SIMD usage between runtime packs?▼

Differences in SIMD usage occur due to changes in dotnet.native.wasm between runtime packs, which can be diagnosed by quantifying SIMD counts and tracking execution-mode differences through binary-level disassembly inspection.

Can I use wasm-objdump to diagnose binary-level regressions in WebAssembly builds?▼

Yes, wasm-objdump inspects disassembly and quantifies SIMD usage to track execution-mode differences, allowing you to surface binary-level anomalies and diagnose regressions between dotnet.native.wasm builds.

Does binary analysis detect execution-mode differences in .NET WASM binaries?▼

Binary analysis detects execution-mode differences by inspecting disassembly with wasm-objdump to quantify SIMD usage and track changes across dotnet.native.wasm versions in different runtime packs.

Related Skills

Explore More Software Engineering Skills→
multiversxmultiversx
12

multiversx-wasm-debug

Analyzes .wasm files for size optimization and defects using Twiggy and other tools.

Official
Advanced
bug-opsbug-ops
11

live-testing

Automate live testing for Rust projects with real binary execution and anomaly detection.

Community
Advanced
hdkz-devhdkz-dev

wasm-optimizer

Optimize WebAssembly modules with wasm-opt to reduce binary size and improve load times.

Community
Intermediate
JCE-Joshhh77JCE-Joshhh77
16

wasm

Implement and verify Rust-to-WebAssembly modules with wasm-pack and wasm-bindgen.

Community
Advanced