deno-script

Write or modify Cataclysm-BN Deno/TypeScript scripts. Use for scripts, tools, migrations, generators, git hooks, and CLI utilities.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/deno-script/SKILL.md

Quality

Content

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

The content is highly actionable with comprehensive executable examples and clean section organization, but it is somewhat verbose due to restating conventions in the Must Do/Must Not Do lists and lacks an explicitly sequenced script-creation workflow with a validate-fix feedback loop.

Suggestions

Collapse the 'Must Do' and 'Must Not Do' lists into the relevant convention sections to remove duplication and improve conciseness.

Add a short sequenced 'Creating a new script' workflow (scaffold shebang -> implement -> deno fmt -> deno lint -> deno check, fix and re-check until clean -> chmod +x) with an explicit validation feedback loop.

Trim explanatory prose such as the per-flag permission descriptions, keeping just the flag list and a one-line note for non-obvious ones.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable snippets, but it duplicates guidance (the 'Must Do'/'Must Not Do' sections restate conventions already shown) and includes explanatory prose like 'Common permission flags' that could be trimmed, placing it between efficient and noticeably verbose.	3 / 5
Actionability	Every convention is backed by complete, copy-paste-ready TypeScript code (shebang, imports, Valibot schema, Cliffy CLI, Deno.Command, file ops, error handling, colors) plus concrete commands (deno check/fmt/lint, chmod), fully covering common cases.	5 / 5
Workflow Clarity	Conventions are listed as a numbered reference rather than a sequenced script-creation workflow, and the 'Testing' section provides commands but no validate-then-fix feedback loop; while deno check is required, there is no explicit 'fix and re-check until it passes' checkpoint, which caps clarity at 3 per the batch/destructive guidance.	3 / 5
Progressive Disclosure	No bundle files are provided and the skill is well under the threshold where external references are needed; content is organized into clearly headed sections (Required Conventions, Common Patterns, When to Write) making navigation easy, so the simple-skill exception applies.	5 / 5
	Total	16 / 20 Passed

Description

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

The description is specific, well-scoped to Cataclysm-BN Deno/TypeScript scripts, and lists concrete use categories. Its main weakness is that the explicit 'Use when...' trigger phrasing lives in the body rather than the frontmatter description, slightly weakening completeness and trigger-term immediacy.

Suggestions

Fold an explicit 'Use when the user asks to create or modify a Deno/TypeScript script' trigger clause into the frontmatter description so completeness does not depend on the body.

Add natural synonyms and file extensions (e.g. '.ts', 'tooling', 'automation script') to broaden trigger-term coverage.

Mention a couple more concrete actions (e.g. 'check with deno check', 'format with deno fmt') to push specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Write or modify ... scripts, tools, migrations, generators, git hooks, and CLI utilities'), giving good action coverage with minor gaps (no mention of e.g. testing or build tasks explicitly as actions).	4 / 5
Completeness	Clearly states 'what' (write/modify Cataclysm-BN Deno/TypeScript scripts) and 'when' (use for scripts, tools, migrations, generators, git hooks, CLI utilities), but the 'when' is a category list rather than explicit 'Use when...' trigger phrasing in the frontmatter itself.	4 / 5
Trigger Term Quality	Includes natural user phrases like 'create deno script', 'write deno script', 'add typescript script', 'new deno tool' providing good keyword coverage, though it lacks synonyms like 'tooling' or explicit file extensions like '.ts'.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific project (Cataclysm-BN) and a specific runtime (Deno/TypeScript scripts), giving it a clear niche with minimal conflict risk against general coding skills.	5 / 5
	Total	17 / 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: 7 missing	Warning

	Total	15 / 16 Passed

Repository: cataclysmbn/Cataclysm-BN
Path: .agents/skills/deno-script/SKILL.md
Commit: b782646

Reviewed: 1 day 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.