
Deno Skills
https://github.com/denoland/skills- Category
- Developer Tools
- Rank
- No. 1418Tools index
Previous survey · No. 1424 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- denoland
- GitHub
- 98 stars
- Date
About
Modern Deno skills for AI coding assistants. Covers Deno, JSR imports, Fresh, Deno Deploy, and best practices.
What it does
Deno Skills installs focused guidance packs into compatible coding assistants. The assistant selects them from project context, then applies specific advice for dependencies, permissions, migration, deployment, frontend work, and isolated code execution.
Why it's ranked here
The project combines unusually concrete operational guidance with automated checks against documentation decay. It teaches incremental migration instead of demanding rewrites, distinguishes npm compatibility from Deno-specific permissions, and verifies commands and selected TypeScript examples. Coverage is incomplete, however, because only two skill sets receive full snippet verification.
What's good
The migration guidance is practical and reversible: adopt Deno first as a package manager, then runtime, then tighten permissions, and only optionally replace existing tools. It also names common failure modes, explains lifecycle-script approval, preserves lockfile pins, and recommends narrowly scoped access grants.
Tradeoffs
The guidance targets Deno 2.9 or newer, so it is not designed for older installations. Automated snippet checking currently covers only the core and migration skills. Frontend, deployment, and sandbox material contains project-dependent fragments that the verifier explicitly skips.
How to use it well
Install the complete bundle for teams regularly maintaining Deno applications, or select one skill for a focused migration or deployment task. It fits assistants that support the Agent Skills specification. Keep framework documentation nearby for ordinary React, Svelte, or similar APIs, and use platform-specific guidance for non-Deno deployment or isolation systems.
Technical notes+
README.md defines five skills and the supported installation surfaces. Each skill is a Markdown package under skills/, with frontmatter metadata and scoped instructions. deno.json exposes verify and check tasks, while scripts/verify_skills.ts walks Markdown, extracts fenced blocks, type-checks eligible TypeScript snippets, and probes documented Deno subcommands through the installed CLI. Its VERIFIED list currently contains deno and migrate-to-deno. .github/workflows/verify.yml runs deno ci followed by the composed check task, and .github/workflows/fmt.yml separately checks formatting. .claude-plugin/plugin.json and .claude-plugin/marketplace.json provide Claude plugin packaging.
Observed
- License
- MIT License
- Primary content
- Markdown skill documents, supported by a TypeScript verification script
- Packaging
- Agent Skills specification packages plus a Claude Code plugin and marketplace entry
- Install surface
- Plugin commands, npx skills, or manual directory copying
- Supported assistants
- Claude Code, Cursor, VS Code with GitHub Copilot, and other Agent Skills-compatible assistants
- Verification scope
- Command validation and TypeScript snippet checking cover the core Deno and migration skills
Read from README.md, deno.json, scripts/verify_skills.ts, LICENSE, deno.lock, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, skills/deno/SKILL.md, .github/workflows/fmt.yml, skills/deno-deploy/SKILL.md, .github/workflows/verify.yml, skills/deno-sandbox/SKILL.md, skills/deno-frontend/SKILL.md, skills/migrate-to-deno/SKILL.md, skills/deno/references/CLI.md.
What it can do
Teach Deno runtime fundamentals
Learning queries about Deno → Deno knowledge and best practices
Generate JSR import statements
Package requirements → JSR-compatible import code
Create Fresh framework applications
Application specifications → Fresh application code and structure
Configure Deno Deploy deployments
Deployment requirements → Deno Deploy configuration and setup
Review and improve Deno code quality
Deno source code → Optimized code with best practices applied
Troubleshoot Deno development issues
Error messages and code problems → Solutions and debugging guidance
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.