Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Build with Deno runtime avoiding permission gotchas, URL import traps, and Node.js migration pitfalls.
Build with Deno runtime avoiding permission gotchas, URL import traps, and Node.js migration pitfalls.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
User needs Deno expertise โ secure TypeScript runtime with permissions model. Agent handles permission configuration, dependency management via URLs/npm, and migration from Node.js.
TopicFilePermission systempermissions.mdImports and dependenciesimports.mdNode.js migrationnode-compat.md
--allow-all in development โ then production crashes because you don't know what permissions you actually need --allow-read without path โ grants access to entire filesystem, security hole --allow-run without list โ subprocess can run anything, specify: --allow-run=git,npm --allow-env without list โ leaks all env vars, specify: --allow-env=API_KEY,DATABASE_URL --allow-net without list โ can connect anywhere, specify hosts: --allow-net=api.example.com Missing permission in CI โ hangs waiting for prompt that never comes, add --no-prompt
Remote URLs in production โ network failure = app won't start, vendor dependencies locally No lockfile by default โ deps can change between runs, always use deno.lock @^1.0.0 semver syntax doesn't exist โ use exact URLs or import maps Import maps in wrong place โ must be in deno.json, not separate file (Deno 2.x) HTTPS required โ HTTP imports blocked by default, most CDNs work but self-hosted may not URL typo โ no error until runtime when import fails
.ts extension required in imports โ model generates extensionless imports that fail tsconfig.json paths ignored โ Deno uses import maps in deno.json, not tsconfig Type-only imports โ must use import type or bundler may fail Decorators โ experimental, different from tsc behavior /// <reference> โ handled differently than tsc, may be ignored
deno compile includes runtime โ binary is 50MB+ minimum --cached-only requires prior cache โ fresh server needs deno cache first Deno Deploy limitations โ no filesystem, no subprocess, no FFI Environment variables โ different API: Deno.env.get("VAR") not process.env.VAR Signals โ Deno.addSignalListener not process.on("SIGTERM")
Deno.test different from Jest โ no describe, different assertions Async test without await โ test passes before promise resolves Resource leaks โ tests fail if you don't close files/connections Permissions in tests โ test may need different permissions than main code Snapshot testing โ format differs from Jest snapshots
npm: specifier โ works for most packages but native addons fail node: specifier required โ import fs from 'fs' fails, need import fs from 'node:fs' node_modules optional โ enable with "nodeModulesDir": true in deno.json package.json scripts โ not automatically supported, use deno.json tasks Peer dependencies โ handled differently, may get wrong versions
Deno.readTextFile vs fs.readFile โ different API, different error types fetch is global โ no import needed, unlike Node 18- Top-level await โ works everywhere, no wrapper needed Permissions at runtime โ can request dynamically but user must approve
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.