alcyone-labs/jazz-runtime-wasm-compat
skills/jazz-runtime-wasm-compat/SKILL.md
Build Jazz runtime bootstrap that is correct across browser, worker, edge, and Node crypto environments
$ install --global
skillsauthnpx skillsauth add alcyone-labs/agent-skills jazz-runtime-wasm-compatInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 2, 2026, 4:51 AM58.1s12 files scanned
SKILL.md
- name:
- jazz-runtime-wasm-compat
- description:
- Build Jazz runtime bootstrap that is correct across browser, worker, edge, and Node crypto environments
Jazz Runtime WASM Compatibility
Use this skill for runtime bootstrap correctness: import order, crypto backend, worker startup, and credentials boundaries.
Runtime Matrix
- Browser main thread
- Service worker (MV3)
- Dedicated worker
- Edge runtime (Cloudflare/Vercel edge)
- Node/Deno server runtime
- Constrained native/WebView runtime
Critical Invariants
- In edge/worker-sensitive contexts, import
jazz-tools/load-edge-wasmbefore any Jazz import. startWorker()credentials must remain server/worker-only (accountSecretnever exposed to client).startWorker()can run account migrations at worker start whenAccountSchemais provided.- Node-API (
NapiCrypto) is optional optimization on supported Node runtimes, not a universal baseline. - Prefer single-worker instance per server process for predictable behavior where required by workload invariants.
- Use
asActiveAccount: falseexplicitly if you must avoid active-account side effects.
When to Use WASM vs Node-API
- WASM: broad compatibility, required in edge runtimes.
- Node-API: higher performance on supported Node 20+ platforms, unavailable on edge.
Fallback Strategy
If worker/WASM runtime is unstable in constrained environments, move Jazz transport to main thread and preserve protocol semantics.
Verification Checklist
- Confirm import graph order (
load-edge-wasmfirst where needed). - Confirm runtime supports selected crypto backend.
- Confirm worker credentials are environment-scoped and never shipped to client.
- Confirm worker migration behavior if
AccountSchemais supplied. - Confirm behavior in target deployment runtime, not only local dev.
Related Skills
alcyone-labs/skill-forge
development
VerifiedTrustedCommunity
Builds precise production-ready custom Agent Skills following AgentSkills.io guidelines. Use when user requests to create, refine or package Skills
1SKILL.mdUpdated Apr 2, 2026
alcyone-labs/simple-logger-usage
development
VerifiedTrustedCommunity
Best practices for using simple-logger in TypeScript applications
1SKILL.mdUpdated Apr 2, 2026
alcyone-labs/sauve-jazz-extension
tools
VerifiedTrustedCommunity
Implement Sauve-specific Jazz extension behavior on top of worker-authority architecture and typed popup-worker protocol
1SKILL.mdUpdated Apr 2, 2026
alcyone-labs/playwright-chrome-extension-testing
tools
VerifiedTrustedCommunity
Test Chrome extensions (Manifest V3) headlessly with Playwright — load unpacked extensions, extract the extension ID, test popups/content scripts/background, run reliably in CI, and use the correct headless mode that actually supports extensions.
1SKILL.mdUpdated Apr 2, 2026