deno-tools

Automate Deno TypeScript utility and CLI development with standardized runtimes, permissions, and testing.

9|Updated Feb 15, 2026

Search Tags:#typescript #testing #cli #permissions #deno #cliffy

Ready to run

npx skills add https://github.com/gwenwindflower/dotfiles --skill deno-tools

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deno-tools
Source: https://github.com/gwenwindflower/dotfiles/tree/main/dot_agents/exact_skills/deno-tools
Command: npx skills add https://github.com/gwenwindflower/dotfiles --skill deno-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Build TypeScript scripts and CLIs on Deno—from quick one-off utilities to multi-command CLIs—while keeping consistent typing, testing, formatting, and permissions.

Core Features & Use Cases

Single-file script shape: quick, focused tasks with a minimal footprint.
Multi-file utilities: clean separation of logic in lib/ with a thin entry point.
Cliffy CLI: create subcommands with typed options and helpful auto-generated help.
Project scaffolding: deno.json with common tasks for run, test, check, fmt, and lint.

Quick Start

Create a small deno script.ts and wire it in deno.json to run with a deno task.

Frequently Asked Questions about deno-tools

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I scaffold a Deno TypeScript CLI project with standardized testing and formatting?▼

Scaffold a Deno TypeScript CLI by generating a deno.json with run, test, check, fmt, and lint tasks. This standardizes typing, formatting, and permissions across single-file scripts, multi-file utilities, and Cliffy-powered CLIs.

What's the best way to structure multi-file Deno utilities?▼

Structure multi-file Deno utilities by separating logic into a lib/ directory with a thin, frontmatter-driven entry point. This clean separation maintains consistent typing and test conventions across the project.

Do I need deno.json to manage runtime permissions for TypeScript scripts?▼

Use deno.json to manage runtime permissions and standardize task layouts for TypeScript scripts. It enforces a frontmatter-driven entry point and wires common tasks like run, test, and check for consistent execution.

Can I use this approach for quick single-file Deno scripts?▼

Create single-file Deno scripts with a minimal footprint and focused tasks. The approach applies a frontmatter-driven entry point and standardized formatting to keep quick utilities clean and consistent.

What are the limitations of frontmatter-driven entry points in Deno projects?▼

Frontmatter-driven entry points enforce a consistent project skeleton but require adherence to specific typing and test conventions. This structured approach may add overhead for extremely simple, throwaway scripts.