
from extensions108
Tools and guidance for using Deno in projects: init, manage dependencies (jsr/npm), run tasks/scripts with minimal permissions, and run common dev tasks (fmt, l
This skill adds concrete Deno operations and decision rules an agent can follow when working in repositories that use Deno. It explains how to initialize projects, add/remove dependencies (JSR and npm), run scripts and tasks with least-privilege permissions, and run formatting, linting, and tests. The skill collects common commands and permission recommendations so the agent can perform safe dev workflows or instruct a developer.
Use this skill when you detect Deno config files (deno.json/deno.jsonc), a deno.lock, or documentation/scripts referencing deno run, deno task, deno test, or deno add. Trigger when asked to run or modify code, add/remove dependencies, run tests, or produce runtime commands for Deno projects.
references/ (has_references=true).deno task when tasks exist), examples for deno add/remove, guidance for permission flags, and examples for fmt/lint/test and running CLIs.Agents that can run shell commands and edit repo files are compatible (Codex/Copilot-style CLIs, OpenClaw agents with shell access, CLI-enabled assistants).
The 'deno' skill has no SKILL.md content available — the GitHub source returns 404 and skill_md_body is null. No scripts to evaluate. This appears to be a stub or removed entry in the x-cmd/skill repo with only a name, description, and tags but no actual instructions or runnable content.
Empty/stub skill with no content. The GitHub path data/x-cmd/deno/SKILL.md returns 404 — the file likely never existed or was removed. Only metadata (name, description, tags) was present in the DB. Scored as minimal since there's nothing to audit substantively. Security score kept at 85 since there's no code to evaluate for risks — absence of code means no vulnerabilities, but also no value.