Deno
v1.0.0Build with Deno runtime avoiding permission gotchas, URL import traps, and Node.js migration pitfalls.
⭐ 2· 622·3 current·3 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the content: all files are Deno-focused guidance (permissions, imports, Node migration). The only runtime requirement is the 'deno' binary, which is appropriate for a Deno troubleshooting/authoring skill.
Instruction Scope
SKILL.md and supporting docs contain best-practice commands and examples (deno run, deno cache, deno vendor, etc.) and focus on Deno-specific risks. The documents include illustrative examples (e.g., showing that broad --allow-read could expose /etc/passwd) but do not instruct the agent to read unrelated host files or to exfiltrate data; all commands and file/path references are relevant to Deno usage and deployment.
Install Mechanism
No install spec and no included code files — instruction-only. That minimizes risk: nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables or credentials. The docs discuss how to scope runtime permission flags (e.g., --allow-env=API_KEY) as guidance, which is appropriate and proportional for a Deno-focused guide.
Persistence & Privilege
always is false and there is no mechanism to persist or modify other skills or global agent settings. Model invocation is allowed (normal default) but the skill itself does not request elevated platform privileges.
Assessment
This skill is a documentation-only helper for using Deno; it does not include code or request secrets. Before enabling it, ensure the agent environment actually has a trusted deno binary (the skill assumes deno is present) and be aware that any agent action that runs deno with broad permission flags (e.g., --allow-all or --allow-read without paths) could allow access to files and environment variables — that risk comes from how you run deno, not from this skill. If you plan to let the agent execute commands on your machine, enforce least-privilege when invoking deno and prefer vendoring and lockfiles for production as the docs recommend.Like a lobster shell, security has layers — review code before you run it.
latestvk973m1mdeejp9tekvf954x2cw5817w32
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🦕 Clawdis
OSLinux · macOS · Windows
Binsdeno