How do I install the Dune Browser Wasm Troubleshooting skill?

Run npx skillmds@latest add tomevault-io/dune-browser-wasm-troubleshooting in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dune Browser Wasm Troubleshooting safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dune Browser Wasm Troubleshooting?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dune Browser Wasm Troubleshooting free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dune Browser Wasm Troubleshooting?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dune Browser Wasm Troubleshooting by tomevault-io

Name: Dune Browser Wasm Troubleshooting
Author: tomevault-io

Dune Browser Wasm Troubleshooting

Troubleshoot DuneTools browser and WASM failures. Use when seeing SkiaSharp initialization errors, missing WASM assets, 404s for native libraries, publish/runtime startup failures, or incorrect native relink behavior in src/DuneTools/DuneTools.Browser. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Dune Browser WASM Troubleshooting

When To Use

Browser app fails during startup in src/DuneTools/DuneTools.Browser.
Runtime shows 404 for native libraries or framework artifacts.
SkiaSharp or HarfBuzz initialization fails at runtime.
A change to browser packaging, runtime config, or publish output breaks loading.

Procedure

Confirm failure details first. Collect the exact error text, failing URL, and whether the issue appears in local run, publish output, or deployed hosting.
Verify browser project configuration. Check src/DuneTools/DuneTools.Browser/DuneTools.Browser.csproj and confirm:

Target framework is net10.0-browser.
WasmBuildNative is enabled.
Project reference to src/DuneTools/DuneTools/DuneTools.csproj remains intact.

Verify dependency consistency. Confirm Avalonia package versions remain synchronized in src/DuneTools/Directory.Packages.props.
Verify local tooling. If native WASM build behavior looks wrong, ensure wasm-tools workload is installed and current.
Reproduce with minimal commands. Use a focused build or publish command for src/DuneTools/DuneTools.Browser/DuneTools.Browser.csproj, then inspect output artifacts under publish directories and framework payload files.
Fix the smallest root cause. Prioritize targeted changes in browser project config or package/version alignment. Avoid broad refactors.
Validate end-to-end. Confirm the app starts, no missing asset requests remain, and browser console no longer reports initialization/type failures.

Output Checklist

Root cause summary.
Exact files changed.
Validation commands run.
Remaining risk, if any.

Source: OpenRakis/OpenRakis — distributed by TomeVault.

---name: dune-browser-wasm-troubleshootingdescription: Troubleshoot DuneTools browser and WASM failures. Use when seeing SkiaSharp initialization errors, missing WASM assets, 404s for native libraries, publish/runtime startup failures, or incorrect native relink behavior in src/DuneTools/DuneTools.Browser. Use when this capability is needed.---# Dune Browser WASM Troubleshooting## When To Use- Browser app fails during startup in [src/DuneTools/DuneTools.Browser](src/DuneTools/DuneTools.Browser).- Runtime shows 404 for native libraries or framework artifacts.- SkiaSharp or HarfBuzz initialization fails at runtime.- A change to browser packaging, runtime config, or publish output breaks loading.## Procedure1. Confirm failure details first.Collect the exact error text, failing URL, and whether the issue appears in local run, publish output, or deployed hosting.2. Verify browser project configuration.Check [src/DuneTools/DuneTools.Browser/DuneTools.Browser.csproj](src/DuneTools/DuneTools.Browser/DuneTools.Browser.csproj) and confirm:- Target framework is net10.0-browser.- WasmBuildNative is enabled.- Project reference to [src/DuneTools/DuneTools/DuneTools.csproj](src/DuneTools/DuneTools/DuneTools.csproj) remains intact.3. Verify dependency consistency.Confirm Avalonia package versions remain synchronized in [src/DuneTools/Directory.Packages.props](src/DuneTools/Directory.Packages.props).4. Verify local tooling.If native WASM build behavior looks wrong, ensure wasm-tools workload is installed and current.5. Reproduce with minimal commands.Use a focused build or publish command for [src/DuneTools/DuneTools.Browser/DuneTools.Browser.csproj](src/DuneTools/DuneTools.Browser/DuneTools.Browser.csproj), then inspect output artifacts under publish directories and framework payload files.6. Fix the smallest root cause.Prioritize targeted changes in browser project config or package/version alignment. Avoid broad refactors.7. Validate end-to-end.Confirm the app starts, no missing asset requests remain, and browser console no longer reports initialization/type failures.## Output Checklist- Root cause summary.- Exact files changed.- Validation commands run.- Remaining risk, if any.---> Source: [OpenRakis/OpenRakis](https://github.com/OpenRakis/OpenRakis) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions