Connection Import Wasm
feigeCode/navop
A skill your agent uses when implementing, debugging, packaging, or host-enabling onetcli WASM connection importers such as DBeaver, Navicat, Navicat Lite, Termius, connection-import.wit components…
Transpile Wado Wasm components to JS with jco, then run, debug, and benchmark them on Node.
$ npx skills add wado-lang/wado --skill jco -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wado-lang/wado jco --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/wado-lang/wado.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/jco .claude/skills/jco && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jco" agent skill from https://github.com/wado-lang/wado/tree/main/.claude/skills/jco into .claude/skills/jco/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jco", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wado-lang/wado/tree/main/.claude/skills/jcoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wado-lang/wado --skill jco -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wado-lang/wado jco --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wado-lang/wado.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/jco .agents/skills/jco && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jco" agent skill from https://github.com/wado-lang/wado/tree/main/.claude/skills/jco into .agents/skills/jco/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jco", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wado-lang/wado --skill jco -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wado-lang/wado jco --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wado-lang/wado.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/jco .cursor/skills/jco && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jco" agent skill from https://github.com/wado-lang/wado/tree/main/.claude/skills/jco into .cursor/skills/jco/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jco", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wado-lang/wado.git --path .claude/skills/jco--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wado-lang/wado --skill jco -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wado-lang/wado jco --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wado-lang/wado.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/jco .gemini/skills/jco && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jco" agent skill from https://github.com/wado-lang/wado/tree/main/.claude/skills/jco into .gemini/skills/jco/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jco", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wado-lang/wado jcoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wado-lang/wado --skill jco -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wado-lang/wado.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/jco .github/skills/jco && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jco" agent skill from https://github.com/wado-lang/wado/tree/main/.claude/skills/jco into .github/skills/jco/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jco", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wado-lang/wado --skill jco -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wado-lang/wado jco --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wado-lang/wado.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/jco .opencode/skills/jco && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jco" agent skill from https://github.com/wado-lang/wado/tree/main/.claude/skills/jco into .opencode/skills/jco/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jco", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
jcoTranspile Wado Wasm components to JS with jco, then run, debug, and benchmark them on Node.
Jco is an agent skill from wado-lang/wado. Transpile Wado Wasm components to JS with jco, then run, debug, and benchmark them on Node. Use for anything that involves jco, Node, or a browser as the host.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with WebAssembly. The repository describes itself as: The Wado Programming Language. The licence is MIT.
Read from SKILL.md and the folder at commit b1f1e2a. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
misenodeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Jco loads about 2.7k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 1,059 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from wado-lang/wado at commit b1f1e2a, republished under its MIT licence (© wado-lang). 1,059 words, ~2,666 tokens.
.claude/skills/jco/SKILL.md (or your agent's skills folder).jco (bytecodealliance) transpiles a Wasm component into JS + core Wasm so it runs on a plain Wasm engine (V8/Node, browsers) instead of a Component Model runtime. Wado targets WASI P3; this doc covers what the released jco does for Wado today and what is still blocked.
scripts/jco, mise run jco-*).-f no-wide-arithmetic — V8 has no wide-arithmetic
proposal, and float formatting / i128 emit it._setPreopens (see below).mise run jco-hello-released. Benchmark:
mise run jco-bench <program.wado>.WebAssembly.Suspending), so no flag is needed; the repo pins node = "26"
in mise.toml. Node 24 needs --experimental-wasm-jspi; Node 22's older JSPI
fails (WebAssembly.Suspending is not a constructor)./tmp pitfall: outside the repo, node may resolve to a system Node 22
(mise activation is path-scoped). Run inside the repo, or use the pinned
binary's absolute path.-f no-wide-arithmetic (see below).scripts/jco)Released @bytecodealliance/jco as a library. transpile-released.mjs is a
plain transpile() — jco's own preview3-shim serves every import a Wado
program makes, and the output links to it through a node_modules symlink the
script writes beside the files.
The shim writes stdout from a worker that is torn down once the event loop
empties, so lines still queued when run() resolves are lost, and a runner that
calls process.exit on that promise loses more. Hold the loop open for a
second after run() resolves. The lines of one run can also arrive out of
order.
A program that reads files needs a preopen. Set it before importing the
transpiled module, mapping the guest's . to a host directory as
wado run --dir <dir>::. does:
import { _setPreopens } from "@bytecodealliance/preview3-shim/filesystem";
_setPreopens({ ".": "/abs/host/dir" });
const m = await import("./out/prog.js");
await m.run.run();
await new Promise((r) => setTimeout(r, 1000));Import the shim the output links to through its node_modules symlink. A
second copy of the shim holds its own preopen table, which the program never
reads.
mise tasks:
mise run jco-deps # npm install released jco under scripts/jco
mise run jco-transpile-released foo.wasm [out-dir]
mise run jco-hello-released # compile + transpile + run hello on Node
mise run jco-bench <program.wado> [runs] # compile -f no-wide-arithmetic, transpile, self-time| Capability | Status |
|---|---|
| Transpile (GC component) | ✅ works, wasi:http/service included |
| JSPI | ✅ native (Node 26 no flag; Node 24 needs the flag) |
| Wide-arithmetic component | ❌ transpile rejects it (wide arithmetic support is not enabled); even if forced, V8 rejects the opcode at runtime → use -f no-wide-arithmetic |
| Stdout via stream | ✅ jco's own shim delivers it, if the runner holds the event loop open after run() resolves |
| Filesystem read stream | ✅ reads through a preopen set with _setPreopens (zlib benchmark verified) |
-f no-wide-arithmetic)Wado emits the Wasm wide-arithmetic proposal (i64.mul_wide_u/s, i64.add128,
i64.sub128) for float formatting (core:prelude/fpfmt.wado) and i128. No
V8 implements it (checked through Node 26; no flag, --wasm-staging no help),
so any component containing those opcodes fails WebAssembly.compile with
invalid numeric opcode: 0xfc16.
-f no-wide-arithmetic rewrites each such builtin call, before NIR, to a
32-bit-limb software form in core:rt (i64_mul_wide_u_soft and so on;
wado-compiler/src/lower/wide_arith.rs). NIR and WIR then show ordinary calls,
which the optimizer inlines. Compile every Node-bound Wado program with this
flag — a bare println of a float needs it.
BA ships a preview3-shim implementing P3 cli / clocks / filesystem /
http, with a browser build beside the Node one. A plain jco transpile wires
it, and stdout, float formatting, wasi:random, MonotonicClock and an HTTP
handle all run through it unaided. Its browser cli is unimplemented
(throw new Todo()), which is why the playground keeps a hand-written one.
A hand-written clock is where precision goes missing: system-clock.now is an
instant carrying sub-second nanoseconds, and get-resolution a bare duration.
mise run jco-bench <program.wado> [runs] compiles with -f no-wide-arithmetic,
transpiles via the released pipeline, and runs the program self-timed runs
times (default 3; keep the best). The benchmark programs already self-time via
core:benchmark + MonotonicClock and print their own
throughput line, so no host timing is needed.
JCO_PREOPEN names the host directory granted as the program's . (default:
the repository root). The benchmarks read their data relative to benchmark/:
mise run jco-bench benchmark/mandelbrot/mandelbrot.wado
JCO_PREOPEN=benchmark mise run jco-bench benchmark/zlib/zlib_bench.wado| Benchmark | Wado on Node (jco) | Wado on wasmtime |
|---|---|---|
| mandelbrot | ~4.0 M px/s | ~4.2 M |
| sieve | ~150 M numbers/s | ~64 M (V8 ~2.3× faster) |
| fts | ~12 M conv/s | — |
| zlib compress | ~65 MB/s | — |
| zlib decompress | ~220 MB/s | — |
The Node column is mise run jco-bench <program.wado> as above; the wasmtime
column is wado run -O2 <program.wado> from benchmark/, as
benchmark/mise.toml runs it.
Compute throughput on V8 lands within ~5–10% of wasmtime (sieve is much faster on V8). Numbers are indicative on a noisy cloud VM; keep best-of-3.
The other filesystem benchmarks (json-{twitter,canada,catalog}, sqlite-parse, syntax-highlight, cbor) load their data the same way, outside the timed loop, but have not been run on Node yet.
Not jco. Handled by -f no-wide-arithmetic.
An instance serves a couple of calls, then the next suspends on a stream read
whose host injection is never driven (JCO_DEBUG=1 ends at
[StreamEnd#copy()] blocked). cloudflare-worker/ builds one per request.
Transpiled output is one large JS file. Useful canonical-builtin → JS mappings:
| Wasm builtin | jco JS function | Notes |
|---|---|---|
stream.write | streamWrite() | JSPI Suspending |
stream.read | streamRead() | JSPI Suspending |
canon lower (async) | _lowerImportBackwardsCompat() | JSPI Suspending |
task.return | taskReturn() | |
future.new (lift) | _genStreamHostInjectFn / createReadableStreamEnd | host→guest wiring |
Catch swallowed errors — jco's async machinery loses errors as unhandled rejections:
process.on('unhandledRejection', e => { console.error('UNHANDLED:', e); process.exit(1); });JCO_DEBUG=1 node run.mjs — verbose trace of every instruction/trampoline.
A trailing [ComponentAsyncState#suspendTask()] with no progress = a
rendezvous deadlock.
Inject logging by string-replacing a function header in the transpiled JS
(e.g. add console.error(...) to streamRead/generatedStreamHostInject).
Timeout hangs: timeout 12 node run.mjs so a deadlock doesn't wedge.
| Error | Likely cause |
|---|---|
invalid numeric opcode: 0xfc16 | Wide-arithmetic — recompile with -f no-wide-arithmetic |
WebAssembly.Suspending is not a constructor | Node < 24, or Node 22 picked up outside the repo (use Node 26) |
FutureReadableEnd is not defined | Future-end classes not injected (run via transpile-released.mjs) |
| stdout empty or missing lines | The runner exits or empties the event loop before the shim's worker flushes (wait after run()) |
Bare unreachable from a program that reads files | No preopen set (_setPreopens), or a path outside it; the panic message is lost with the exit |
wide arithmetic support is not enabled (transpile) | Compile with -f no-wide-arithmetic; V8 cannot run the opcodes either |
| Hang / timeout | JSPI Suspending missing on a trampoline, or a stream rendezvous deadlock |
© wado-lang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/jco of wado-lang/wado.
Open the folder on GitHubat commit b1f1e2a
Jco next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jco this skillwado-lang/wado | 117 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Connection Import WasmfeigeCode/navop | 1.8k | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| Changesetwhitphx/stlite | 1.7k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Debug Php Wasm Main ModuleWordPress/wordpress-playground | 2k | — | ~3.1k | Automated safety check: Pass | GPL-2.0 | |
| Code Reviewziggy42/epsilon | 439 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Debug Php Wasm Side ModulesWordPress/wordpress-playground | 2k | — | ~2.5k | Automated safety check: Pass | GPL-2.0 |
feigeCode/navop
A skill your agent uses when implementing, debugging, packaging, or host-enabling onetcli WASM connection importers such as DBeaver, Navicat, Navicat Lite, Termius, connection-import.wit components…
whitphx/stlite
Create or update a changeset fragment (.changeset/.md) reflecting the changes made in the current session or branch.
WordPress/wordpress-playground
Debug PHP.wasm main module crashes including Asyncify errors (unreachable, memory access out of bounds), JSPI errors (SuspendError, trying to suspend JS frames), WASM memory growth bugs, and runtime…
ziggy42/epsilon
A skill your agent uses when the user asks for a code review.
WordPress/wordpress-playground
Debug WASM side modules (dynamic PHP extensions) including dlopen failures, SIDEMODULE loading, JSPI suspension crashes in extensions, C++ weak symbol issues, and extension runtime errors.
justrach/merjs
Work with the merjs Zig web framework. An agent skill from justrach/merjs.
wado-lang/wado
Profile the native Rust wado binary (compile/serve/run) for host-side bottlenecks — CPU with a sampling profiler, memory with the span trace's RSS and valgrind DHAT.
wado-lang/wado
Analyze and improve the runtime speed of a Wado program's compiled guest Wasm — profile hot functions, read the generated WIR for allocations and copies, reason about the WasmGC cost model, and…
wado-lang/wado
Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower.
wado-lang/wado
Investigate and improve code coverage for the wado-compiler crate.
wado-lang/wado
The only way to merge origin/main into a branch, conflicts or not.
wado-lang/wado
Task-completion flow: /cr (a /code-review answered with /code-review-response, which ends with /distill), update docs (spec/cheatsheet/compiler/optimizer), then run mise run on-task-done (build…
Works with
Categories
Transpile Wado Wasm components to JS with jco, then run, debug, and benchmark them on Node. Jco is an agent skill from wado-lang/wado. Transpile Wado Wasm components to JS with jco, then run, debug, and benchmark them on Node.
Jco fits situations like: anything that involves jco; A browser as the host.
Run `npx skills add wado-lang/wado --skill jco -a claude-code`. Or copy the skill folder (.claude/skills/jco in wado-lang/wado) into .claude/skills/jco in your project. Claude Code loads it when a task matches its description.
Run `npx skills add wado-lang/wado --skill jco -a codex`. Or copy the skill folder (.claude/skills/jco in wado-lang/wado) into .agents/skills/jco in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wado-lang/wado --skill jco -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jco, .gemini/skills/jco, .github/skills/jco and .opencode/skills/jco in your project.
Going by SKILL.md and its folder, Jco needs the command-line tools its instructions call (mise and node). Our summary lists: Node.js.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Jco is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Jco: Connection Import Wasm (feigeCode/navop, 1.8k stars), Changeset (whitphx/stlite, 1.7k stars), Debug Php Wasm Main Module (WordPress/wordpress-playground, 2k stars) and Code Review (ziggy42/epsilon, 439 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
wado-lang (a GitHub organization) maintains it in wado-lang/wado, which has 117 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on October 9, 2026.
Source: wado-lang/wado on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.