configure-deno-commands

Configure and maintain Deno development commands (check, test, dev, prod). Use when the user wants to set up or update the standard command interface in deno.json and scripts/ directory.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%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.

Highly actionable content with executable examples and a clear workflow plus verification checklist, weakened mainly by verbose, dated incident rationale in the rules that could be tightened or moved to a changelog section.

Suggestions

Tighten rules 12-14 by trimming the historical incident anecdotes and fork-bomb/flushing rationale Claude already knows, or relocate dated notes to a 'Past incidents' or 'Changelog' section to satisfy the time-sensitive conciseness guideline.

Add an explicit fix-and-retry loop to the Workflow's Verify step (e.g., 'If `deno task check` fails, read the buffered failed-check output, fix, and re-run until it passes') to reach the top workflow-clarity anchor.

Consider extracting the long rules 12-14 into a referenced file (e.g. references/edge-cases.md) so SKILL.md stays a lean overview, improving progressive disclosure for this over-50-line skill.

Dimension	Reasoning	Score
Conciseness	Mostly dense and high-value, but rules 12-14 include lengthy rationale Claude partly already knows (fork-bomb mechanics, stdout flushing) plus dated incident anecdotes (2026-05-09, 2026-09-06) embedded inline rather than in a deprecated section, which the guideline penalizes.	3 / 5
Actionability	Provides concrete commands (deno task check/test/dev/prod), a copy-paste-ready deno.json tasks block, and a complete executable scripts/test.ts with the import.meta.main re-entry guard covering the common wrapper case.	5 / 5
Workflow Clarity	A clear 4-step sequence (Analyze, Scaffold, Configure, Verify) with an explicit verification step and a final checklist, but it lacks an explicit fix-and-retry error-recovery loop that the anchor-5 example requires.	4 / 5
Progressive Disclosure	Single self-contained file with well-organized sections and no nested references, but it exceeds 50 lines and rules 12-14 are dense enough that minor organization gaps remain versus a fully split structure.	4 / 5
	Total	16 / 20 Passed

Description

87%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.

A strong, concise description that clearly answers both what the skill does and when to use it, with a distinct Deno-specific niche. Minor room to add synonyms like 'Deno tasks' and more specific maintenance actions.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates the four concrete commands (check, test, dev, prod), but the verbs 'Configure and maintain' are somewhat generic, leaving minor gaps in coverage of what maintenance entails.	4 / 5
Completeness	Explicitly states what it does ('Configure and maintain Deno development commands (check, test, dev, prod)') and when to use it ('Use when the user wants to set up or update the standard command interface in deno.json and scripts/ directory').	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('set up or update', 'deno.json', 'scripts/ directory', 'Deno development commands') but misses common synonyms like 'Deno tasks' or 'deno task'.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Deno command interface in deno.json/scripts/) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 9 missing	Warning

	Total	15 / 16 Passed

Repository: korchasa/flowai-plugins
Path: plugins/flowai/skills/configure-deno-commands/SKILL.md
Commit: ad81ae6

Reviewed: 8 hours ago

Table of Contents

Discovery Implementation Validation

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.