CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deno

Use when writing, running, configuring, reviewing, or debugging code in a Deno project, or when scaffolding a new one. Covers dependency management with deno install and deno add, package.json and node_modules support, npm and JSR packages, permissions, where configuration belongs across package.json, tsconfig.json and deno.json, workspaces, the built-in toolchain (fmt, lint, test, check, bench, compile), and publishing.

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable reference skill: every section leads with executable commands or concrete config, assumes Claude's competence, and pushes the deep flag detail to a well-signaled single reference file. The only soft spot is workflow clarity, where validation checkpoints exist (dry-run, --check, deno ci) but content is structured as per-task reference rather than sequenced workflows with feedback loops.

DimensionReasoningScore

Conciseness

The body is lean and command-first, spending its tokens on Deno-specific facts Claude cannot infer ("deno.json wins" for conflicting tasks, pnpm-style isolated node_modules, "--min-dep-age" supply-chain window, lifecycle scripts not running by default) rather than generic concepts. The one version note ("Needs Deno 2.9+") is a requirement statement, not date-conditional guidance, and legacy URL imports are handled as an explicit old-pattern note ("Deno once used full URL imports ... They still run but aren't recommended"), so the time-sensitivity penalty does not apply.

5 / 5

Actionability

Nearly every section delivers copy-paste-ready commands or config: a full dependency-command block ("deno add jsr:@std/path", "deno ci"), a permissions flag table with short forms and allowlist syntax ("--allow-net=example.com:443"), a concrete deno.json example, and runnable code ("Deno.serve((_req) => new Response(\"Hello\"))"). The common cases — install, run, scaffold, publish — are each covered with specific commands, matching the score-5 anchor.

5 / 5

Workflow Clarity

The content is organized into unambiguous per-task sections and includes real checkpoints ("deno publish --dry-run" before publish, "deno fmt --check" and "deno ci" for CI, "deno ci ... fails if the lockfile is stale") plus a reviewing checklist and an error-recovery hint ("On 'Requires net access to ...', add that specific permission"). It falls short of the score-5 anchor because it is a reference-style skill, not a sequenced multi-step workflow with explicit feedback loops throughout — the guidance is per-command rather than a validate-fix-retry process, leaving minor gaps against the anchor's 'feedback loops for error recovery' bar.

4 / 5

Progressive Disclosure

The SKILL.md body is a concise overview of the common cases, and the one bundle file (references/CLI.md, ~200 lines of fuller subcommand and flag reference) is exactly the right split, clearly signaled under 'Further reading' as "references/CLI.md — fuller subcommand and flag reference" and verified to exist. References are one level deep with no nesting, matching the score-5 anchor's 'clear overview with well-signaled one-level-deep references'.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: it pairs an explicit, action-verb-rich 'Use when' trigger clause with a comprehensive, concrete inventory of what the skill covers, all in third person and without padding. Every dimension lands on its top anchor.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ("writing, running, configuring, reviewing, or debugging code ... or when scaffolding a new one") plus specific commands and artifacts ("deno install and deno add", "package.json and node_modules support", "fmt, lint, test, check, bench, compile"), giving comprehensive coverage of the skill's capabilities. It is not merely naming the domain like the score-4 anchor with gaps — the enumerated coverage spans dependencies, config placement, workspaces, permissions, toolchain, and publishing.

5 / 5

Completeness

It explicitly answers both questions: the "Use when writing, running, configuring, reviewing, or debugging code in a Deno project, or when scaffolding a new one" clause gives concrete trigger phrases for when, and the "Covers dependency management ... permissions ... workspaces ... built-in toolchain ... and publishing" sentence states concretely what it does. This matches the score-5 anchor; the score-4 anchor's 'when could be more explicit' caveat does not apply.

5 / 5

Trigger Term Quality

Natural terms a user would say are comprehensively covered: "Deno project", "deno install", "deno add", "npm and JSR packages", "package.json", "node_modules", "tsconfig.json", "deno.json", "permissions", "workspaces", and toolchain subcommands. These are exactly the phrases someone needing this skill would use, matching the breadth of the score-5 anchor rather than the 'a few natural terms missing' fit of score 4.

5 / 5

Distinctiveness Conflict Risk

The trigger is scoped to "code in a Deno project", a clear niche with distinct triggers (Deno, JSR, deno.json, deno install), so it is unlikely to fire for generic Node/npm skills despite mentioning npm and package.json. This matches the score-5 anchor ('clear niche with distinct triggers; minimal conflict risk') rather than the minor-overlap fit of score 4.

5 / 5

Total

20

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/deno/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.