Skip to content
Agent Orchestration
Skill

/deno

If the project uses deno, use this skill. Use this skill to initialize and work with Deno projects, add/remove dependencies (JSR and npm), run tasks and scripts with appropriate permissions, and use built-in tooling (fmt/lint/test).

BOOST
From plugin
extensions
17185 skills4 commands
Install
$ npx -y skills add openhands/extensions --skill deno --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/deno

Context preview

The summary Claude sees to decide when to auto-load this skill.

If the project uses deno, use this skill. Use this skill to initialize and work with Deno projects, add/remove dependencies (JSR and npm), run tasks and scripts with appropriate permissions, and use built-in tooling (fmt/lint/test).

SKILL.md

deno.SKILL.md
name: deno
description: If the project uses deno, use this skill. Use this skill to initialize and work with Deno projects, add/remove dependencies (JSR and npm), run tasks and scripts with appropriate permissions, and use built-in tooling (fmt/lint/test).
triggers:
- deno
- deno.json
- deno.jsonc
- deno.lock

Deno

Use Deno as the default runtime/tooling when the repo contains `deno.json`/`deno.jsonc`, uses `deno.lock`, or scripts/documentation reference `deno task`, `deno run`, `deno test`, etc.

Quick decision rules

  • Prefer `deno task <name>` if the repo defines tasks.
  • Use `deno add` / `deno remove` to manage dependencies (writes to config).
  • Be explicit about permissions for `deno run` / `deno test`.

Common operations

Initialize a new project

deno init

Add dependencies (JSR and npm)

# JSR (recommended for Deno-first packages)
deno add jsr:@std/path

# npm packages are supported too
deno add npm:react

# multiple at once
deno add jsr:@std/assert npm:chalk

Remove dependencies

deno remove jsr:@std/path

Run a script

# Minimal permissions: only what the program needs
# Examples:
#   --allow-net=api.example.com
#   --allow-read=./data
#   --allow-env=FOO,BAR

deno run --allow-net --allow-read main.ts

Run tasks

# list tasks
deno task

# run a task defined in deno.json/deno.jsonc
deno task dev

Formatting, linting, testing

deno fmt
deno lint
deno test

# common permissioned test run
deno test --allow-net --allow-read

Install / run CLIs

# Run a JSR or npm package's CLI without installing globally
deno x jsr:@std/http/file-server -p 8080

# Install globally (requires choosing permissions at install time)
# Prefer the smallest set of permissions; avoid blanket flags unless necessary.
deno install -g -N -R jsr:@std/http/file-server -- -p 8080

Notes / pitfalls

  • Deno is secure-by-default: missing permissions cause runtime errors; add the smallest set of `--allow-*` flags needed.
  • Dependency specifiers:
  • `jsr:` for JSR registry packages
  • `npm:` for npm packages
  • URL imports are also supported (and cached)
  • Lockfile: `deno.lock` helps ensure reproducible dependency resolution.
Read more
Ships withextensions

This repository is the public extensions registry for OpenHands. It contains reusable, shareable skills, plugins, and Agent Canvas Apps that customize agent behavior and interfaces. Skills overview docs: SDK skill guide:

Get the whole plugin

Other skills on extensions.