deploy

Manage Deno Deploy cloud services using both `deno deploy` and `deployctl`. Use this skill for deploying projects, managing Build/Dev/Prod environments, monitoring logs, and troubleshooting issues like private npm dependencies.

Quality

85%

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

82%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 body is an efficient, highly actionable command reference with clear workflows and validation-leaning checkpoints for local debugging and CI/CD. Its weaknesses are minor: a time-sensitive version/date stamp outside a deprecated section and a single-file structure that could offload the command reference to a bundle file.

Suggestions

Move the '(Deno 2.x / 2026)' version/date marker into a clearly labeled 'Current version' or 'Deprecated/old patterns' section so time-sensitive info does not penalize conciseness.

Add an explicit validate-then-proceed feedback loop (e.g. 'deploy locally → verify revision created → only then update CI/CD') to lift workflow clarity toward the top anchor.

Consider splitting the full `deno deploy` / `deployctl` command listings into a references/ file, keeping SKILL.md a concise overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is lean — command lists and code blocks with no padding about what Deno is — but the '(Deno 2.x / 2026)' version/date marker is time-sensitive information placed outside a deprecated section, and the opening line restates the description, giving minor trimmable instances rather than a fully lean result.	4 / 5
Actionability	Provides copy-paste-ready, fully executable commands across the common cases (e.g. 'deno deploy --app=my-app --prod main.ts', 'deno install -gArf jsr:@deno/deployctl', 'deno deploy env set MY_VAR=value --context=production', and a complete GitHub Actions YAML snippet), matching the top anchor.	5 / 5
Workflow Clarity	The 'Local Debugging Protocol (CRITICAL)' and CI/CD sections give clear numbered sequences with a checkpoint ('Verify file uploading and revision creation') and an error→fix loop for unstable APIs, but validation is not as explicit and recurrent as the top anchor requires.	4 / 5
Progressive Disclosure	No bundle files exist, so the skill is a single well-organized file with clear section headers covering overview, commands, troubleshooting, and workflows; it is good structure with content appropriately placed, though a full command reference could arguably live in a separate file, fitting the 'good structure, minor gaps' anchor rather than the split-file top anchor.	4 / 5
	Total	17 / 20 Passed

Description

88%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 strong: it states concrete capabilities, gives an explicit 'Use this skill for' trigger, and anchors on the specific Deno Deploy niche. The only soft spot is that several trigger verbs are generic enough to overlap with other deploy-platform skills.

Suggestions

Add a few more distinctive trigger phrases (e.g. 'roll back a deployment', 'preview/branch deployments', 'Deno Deploy build contexts') to widen natural-term coverage and reduce overlap with generic deploy skills.

Consider naming the platform earlier and more dominantly in the trigger clause so generic verbs read unambiguously as Deno Deploy scoped.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'deploying projects, managing Build/Dev/Prod environments, monitoring logs, and troubleshooting issues like private npm dependencies' — giving comprehensive coverage of the skill's capabilities, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	Clearly answers 'what' ('Manage Deno Deploy cloud services using both deno deploy and deployctl') and 'when' via an explicit 'Use this skill for...' clause with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Strong natural keywords ('Deno Deploy', 'deployctl', 'deploying projects', 'monitoring logs', 'private npm dependencies') that users would say, but a few natural variations (e.g. 'roll back', 'preview deployments') are missing, fitting good-but-not-comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The 'Deno Deploy'/'deployctl' framing carves a clear niche, but generic verbs like 'deploying projects' and 'monitoring logs' carry minor overlap risk with other platform deploy skills, fitting mostly-distinct rather than minimal-conflict.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

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

Reviewed: 6 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.