feat(deno): add deno plugin bundling official denoland/skills - #276
Conversation
Bundle the 5 official skills from github.com/denoland/skills (MIT, maintained by Deno Land) via skills.sh with a pinned skills-lock.json, so the existing weekly update-skills workflow tracks upstream. Registered in the Claude, Codex, and Cursor marketplaces and in release-please.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Up to standards ✅🟢 Issues
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a new official Deno plugin to the marketplace, including skills for core Deno usage, migration, deployment, frontend development, and sandboxing. It registers the plugin across various manifests, updates the main documentation, and configures release automation. The review feedback suggests improving the plugin's README documentation by preferring package.json scripts over direct script execution (such as bun scripts/cli.ts and bun scripts/update-skills.ts) to maintain consistency.
Use the defined package.json scripts in the plugin README instead of invoking script files directly: bun run plugins:multi-format and bun run skills:update-locks <dir>. Addresses gemini-code-assist review threads on PR #276.
|
/gemini review |
# Conflicts: # .release-please-manifest.json
There was a problem hiding this comment.
Code Review
This pull request adds the official Deno plugin to the marketplace, introducing several Deno skills under the agents directory and updating the marketplace manifests, release configurations, and documentation. The review feedback identifies an inconsistency in the keywords defined for the Deno plugin between the main marketplace manifest and the plugin's individual manifest, suggesting aligning both files to ensure consistent search and discovery behavior.
|
/gemini review |
The marketplace entry still carried the keyword set from before the switch to the official denoland/skills content. Align all five manifests on the union: adds fresh and deno-deploy to the marketplace entry, and test-runner to the plugin manifests (regenerated via multi-format). Addresses gemini-code-assist review threads on PR #276.
🔍 Tessl Skill Review
|
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ███░░ 3/5 | Mostly efficient with executable commands and tables, but contains some over-explanation (e.g., explaining what preview deployments do, restating tunnel use cases) and time-sensitive version detail (Deno >= 2.4.2) that adds tokens without a deprecated section. |
| actionability | █████ 5/5 | Fully executable copy-paste-ready commands throughout: deploy, create with all flags, env management, database provisioning, tunnel usage, with specific examples covering common cases. |
| workflow clarity | █████ 5/5 | Clear sequenced deployment workflow (locate app dir, pre-flight checks, startup-dependency handling with --no-wait, then deploy) with validation checkpoints (verify config saved, check version) and error-recovery feedback (provision database then redeploy when warmup fails). |
| progressive disclosure | █████ 5/5 | Well-structured overview with one-level-deep references to real bundle files (AUTHENTICATION, DATABASES, DENO_KV, DOMAINS, FRAMEWORKS, ORGANIZATIONS, RUNTIME, TROUBLESHOOTING), all verified present in references/, with clear inline summaries and signaled links. |
Suggestions:
- Move the version requirement (Deno >= 2.4.2) and the deployctl-vs-deno-deploy deprecation note into a dedicated 'Requirements / Deprecated' section so time-sensitive detail doesn't dilute the core workflow.
- Trim explanatory asides like the preview-deployment sentence and the tunnel use-case bullets, since Claude can infer these from the command context.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | ████░ 4/5 | Lists several concrete actions (deployment workflows, environment variables, KV database access, custom domains, --tunnel flag, command reference) with only minor gaps in coverage. |
| completeness | █████ 5/5 | Clearly answers both 'what' (covers deployment workflows, env vars, KV, domains, tunnel, command reference) and 'when' (Use when deploying Deno apps, asking about Deno Deploy, or working with deno deploy CLI). |
| trigger term quality | █████ 5/5 | Comprehensive natural terms including 'deploying Deno apps to production', 'Deno Deploy', and the concrete 'deno deploy' CLI command users would actually say. |
| distinctiveness conflict risk | █████ 5/5 | Clear niche scoped to Deno Deploy with distinct triggers tied to a specific CLI command; minimal conflict risk with other deployment skills. |
plugins/deno/.agents/skills/deno-frontend/SKILL.md
An exemplary lean SKILL.md: assumes competence, gives executable commands, splits depth cleanly into two real reference files, and frames the work as a clear two-path decision. It falls just short of perfect actionability and workflow clarity only because the inline handler/route example and explicit verify-checkpoints are delegated rather than shown.
Full review details
Validation Checks
16/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | █████ 5/5 | Lean and efficient throughout — 'Two paths. Pick by what the project already uses.' and 'deno create is npm create' assume Claude's competence; every token earns its place with no concept padding. |
| actionability | ████░ 4/5 | Provides executable commands (deno create vite, deno run -Ar jsr:@fresh/init) and a runnable Counter island example, but defers the concrete handler/route example to the reference rather than showing it inline, a minor gap. |
| workflow clarity | ████░ 4/5 | Clear two-path decision flow with concrete setup steps for each path; no destructive or batch operations so the validation cap does not apply, but there are no explicit verification checkpoints (e.g. confirm the dev server is serving) to reach a 5. |
| progressive disclosure | █████ 5/5 | Clear overview pointing one level deep to real, existing files (references/FRESH.md and references/FRESH_MIGRATION.md), well signaled both inline and in a 'Further reading' list — easy to navigate with no nesting. |
Suggestions:
- Include one minimal inline handler/route example (beyond the island component) so the Fresh path is fully actionable without loading the reference.
- Add an explicit verification step after
deno task dev(e.g. 'confirm http://localhost:5173 serves the page') to give the workflow a concrete checkpoint.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | ████░ 4/5 | Lists several specific capabilities — 'Fresh 2.x routes, handlers, islands, Preact signals, Tailwind, and Fresh 1.x to 2.x migration' — but these are framed more as topic coverage than concrete action verbs, leaving minor gaps versus a fully action-oriented enumeration. |
| completeness | █████ 5/5 | Explicitly answers both what ('running ... frameworks under Deno ... Covers ... routes, handlers, islands ...') and when ('Use when building a web frontend with Deno') with concrete trigger phrasing. |
| trigger term quality | █████ 5/5 | Comprehensive coverage of natural terms users actually say — 'React, Vite, Astro, SvelteKit, Next.js, Nuxt', 'Fresh', 'web frontend with Deno' — including framework names and the Deno-specific trigger. |
| distinctiveness conflict risk | ████░ 4/5 | The 'with Deno' framing plus Fresh carve out a clear niche with minimal conflict risk; only minor overlap with generic frontend skills that do not name Deno. |
Suggestions:
- Lead the capability list with action verbs (e.g. 'Build React/Vite/Astro/Next.js frontends under Deno, scaffold Fresh apps, write routes/handlers/islands, configure Tailwind, migrate Fresh 1.x to 2.x') to lift specificity toward 5.
plugins/deno/.agents/skills/deno-sandbox/SKILL.md
The content is highly actionable with comprehensive executable examples and clear usage patterns, making it immediately usable. Its weaknesses are verbosity from repeated await using emphasis and a Common Mistakes section that re-treads earlier points, plus a monolithic single-file structure with no progressive disclosure to reference files.
Full review details
Validation Checks
16/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ███░░ 3/5 | Mostly efficient with extensive useful code, but the await using guidance is repeated across Lifecycle, Basic Usage, and Common Mistakes, the Common Mistakes section re-treads points already made, and the Overview explains Firecracker/AWS-Lambda context Claude already knows, so it could be tightened. |
| actionability | █████ 5/5 | Fully executable, copy-paste-ready code throughout — installation, basic usage, streaming I/O, process killing, running user code safely, playground, and AI agent tool execution — with a Quick Reference table covering the common cases, matching the 5 anchor. |
| workflow clarity | ████░ 4/5 | Patterns like "Running User Code Safely" give a clear sequence (create sandbox, write file, run with restricted perms, check exit code) with most checkpoints present (exit-code validation, timeout kill), but lack an explicit validate→fix→retry feedback loop, leaving minor validation gaps. |
| progressive disclosure | ███░░ 3/5 | The body is well-sectioned with clear headers, but it is a ~400-line monolithic full guide rather than an overview pointing to detailed materials; no references/scripts/assets bundle files exist, and content such as the Common Patterns examples that could live in reference files is inlined. |
Suggestions:
- Consolidate the repeated
await usingguidance into one authoritative section and trim the Common Mistakes entries that merely restate points already covered in Core Concepts, to reduce redundancy. - Move the longer worked examples (Code Playground, AI Agent Tool Execution) into a references/ file and link to it from a concise overview, so SKILL.md becomes a leaner entry point.
- Add an explicit validate→fix→retry feedback loop to the Running User Code Safely pattern (e.g., re-run on exit-code failure after diagnosing stderr) to strengthen workflow checkpoints for risky untrusted-code execution.
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | ████░ 4/5 | Names the domain and several concrete scenarios ("execute untrusted user code, AI-generated code, or need isolated code execution environments") plus the specific SDK, but stops short of enumerating comprehensive concrete actions, fitting the 4 anchor with minor coverage gaps. |
| completeness | █████ 5/5 | Explicitly states both what it covers ("execute untrusted user code, AI-generated code, or need isolated code execution environments. Covers the @deno/sandbox SDK") and when to use it via a concrete "Use when building features that..." trigger clause, matching the 5 anchor. |
| trigger term quality | ████░ 4/5 | Includes natural developer trigger phrases like "untrusted user code", "AI-generated code", and "isolated code execution environments", but omits common synonyms such as "sandbox", "playground", or "code execution", so a few natural terms are missing. |
| distinctiveness conflict risk | ████░ 4/5 | The explicit "@deno/sandbox SDK" pin and sandboxing-specific triggers give it a clear niche with minimal conflict risk, but the broader phrase "isolated code execution environments" could lightly overlap with container/VM isolation skills, keeping it just below 5. |
plugins/deno/.agents/skills/deno/SKILL.md
A well-structured, highly actionable reference skill that uses code, tables, and a clearly signaled CLI.md reference efficiently. It is strong across the board, with only minor conciseness trimming opportunities and the lack of an explicit multi-step validation loop.
Full review details
Validation Checks
16/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ████░ 4/5 | Dense, code-and-table-forward prose that assumes Claude's competence and adds little padding; a few one-liners (deno why, deno outdated, deno list) and minor explanatory clauses could live in the reference file, leaving it just short of the leanest anchor. |
| actionability | █████ 5/5 | Pervasive copy-paste-ready commands, real config JSON, concrete permission flags, and executable code (e.g. Deno.serve) that cover the common cases directly. |
| workflow clarity | ████░ 4/5 | A concrete 'Reviewing Deno code' checklist plus validation cues (deno ci fails on stale lockfile, --check for CI) provide clear guidance, but there is no explicit validate->fix->retry loop, leaving it below the top anchor. |
| progressive disclosure | █████ 5/5 | A lean, well-sectioned overview that pushes subcommand/flag detail to a single well-signaled one-level-deep reference (references/CLI.md, which exists), with external docs collected under 'Further reading'. |
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | █████ 5/5 | Lists multiple concrete capabilities (dependency management with deno install/add, permissions, workspaces, the fmt/lint/test/check/bench/compile toolchain, publishing), matching the 'comprehensive coverage' anchor. |
| completeness | █████ 5/5 | Explicitly answers both 'what' ('Covers dependency management... permissions... workspaces... publishing') and 'when' ('Use when writing, running, configuring, reviewing, or debugging code in a Deno project, or when scaffolding a new one') with concrete trigger phrases. |
| trigger term quality | ████░ 4/5 | Strong natural trigger terms ('writing, running, configuring, reviewing, or debugging code in a Deno project', 'scaffolding a new one'), but no file-extension or synonym triggers like '.ts'/package.json-as-trigger, leaving it just below the comprehensive anchor. |
| distinctiveness conflict risk | █████ 5/5 | Scoped specifically to 'a Deno project', a clear niche with distinct triggers and minimal overlap risk against generic Node/bun/JavaScript skills. |
plugins/deno/.agents/skills/migrate-to-deno/SKILL.md
A well-structured, executable migration guide: a staged rung workflow with back-out steps, a comprehensive command-equivalents table, and a focused breakdown of failure modes. Detail is correctly pushed to one-level-deep reference files, and the only blemish is a bare version pin that the conciseness guideline lightly penalizes.
Full review details
Validation Checks
16/16 checks passed.
Review Details
| Dimension | Score | Detail |
|---|---|---|
| conciseness | ████░ 4/5 | The body is lean, assumes Claude's competence, and avoids re-explaining what Node/Deno are; however the time-sensitive version pin 'Requires Deno 2.9 or later' sits at the top rather than in a deprecated/old-patterns section, which the guideline flags as a minor conciseness penalty. |
| actionability | █████ 5/5 | Commands are copy-paste ready and cover the common cases — 'deno install', 'deno run -A main.js', 'deno task build', narrow permission flags, 'deno approve-scripts' — plus a full per-tool command-equivalents table the user can lift directly. |
| workflow clarity | ████░ 4/5 | The 'Migrate in rungs' sequence is clearly ordered and reversible ('To back out: delete deno.lock and node_modules'), with 'Commit deno.lock once verified' and a 'four things that actually break' recovery section; a formal verify-then-proceed checkpoint per rung is only implicit, so it falls just short of the top anchor. |
| progressive disclosure | █████ 5/5 | The SKILL.md body is an overview and splits per-tool depth into one-level-deep references — 'references/FROM_NPM.md', 'FROM_YARN.md', 'FROM_PNPM.md', 'FROM_BUN.md', 'NODE_APIS.md' — each with a one-line description, and the reference files contain no further nested pointers, making navigation easy. |
Description Review
| Dimension | Score | Detail |
|---|---|---|
| specificity | █████ 5/5 | The description lists multiple concrete capabilities — 'drop-in package manager, running existing package.json scripts, CommonJS versus ESM, node_modules layout, lockfile migration, permissions' and 'per-tool command equivalents' — giving comprehensive coverage of what the skill does. |
| completeness | █████ 5/5 | It explicitly answers both 'what' (the 'Covers...' clause enumerating capabilities) and 'when' (the 'Use when moving... or when adopting Deno incrementally' trigger), with concrete trigger phrases. |
| trigger term quality | █████ 5/5 | It surfaces the exact natural terms users say when they need this skill — 'Node.js, npm, Yarn, pnpm, or Bun project to Deno', 'adopting Deno incrementally' — covering all relevant tool names and migration phrasings as synonyms. |
| distinctiveness conflict risk | █████ 5/5 | The migrate-Node-ecosystem-to-Deno niche is clear and the triggers (specific tool names plus 'to Deno') are distinct, making conflict with other skills minimal. |
To improve your score, point your agent at the Tessl optimization guide. Need help? Jump on our Discord.
Feedback
Report issues with this review at tesslio/skill-review, or send private feedback from your terminal with tessl feedback.
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request adds a new Deno plugin to the repository, registering it across various marketplace configurations, updating the README with installation instructions, and configuring release-please. It also vendors several official Deno skills (such as core Deno, migration guides, Deno Deploy, frontend development, and sandbox execution) under the plugins/deno/.agents/skills/ directory. Since there are no review comments, I have no feedback to provide.
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces the official Deno plugin to the marketplace, adding configuration manifests for Claude, Codex, Cursor, and Antigravity. It installs the vendor-managed Deno skills (including core Deno, migration, Deno Deploy, frontend, and sandbox skills) under the .agents/skills/ directory, tracked by skills-lock.json. Additionally, it updates the main README with installation instructions and configures release-please for automated versioning of the new plugin. As there are no review comments provided, I have no feedback to provide on the review itself.
|
1 participant
Summary
Adds a new
denoplugin to the marketplace that bundles the official Deno skills from denoland/skills (MIT, maintained by Deno Land, targets Deno 2.9+), using the skills.sh vendoring path — the same house pattern as the existingshadcn-uiplugin.New
plugins/deno/(27 files):.agents/skills/— 5 vendored official skills:deno(core: deps via npm/JSR, permissions,deno.json, built-in toolchainfmt/lint/test/check/bench/compile, publishing)migrate-to-deno(Node/npm/yarn/pnpm/bun migration)deno-deploydeno-frontend(Fresh 2.x, Preact, Tailwind)deno-sandbox(@deno/sandboxSDK)skills-lock.json— pinsdenoland/skillswith a per-skillskillPath, so the repo's existing weekly.github/workflows/update-skills.ymltracks upstream and opens afix:PR when it moves.claude-plugin/plugin.json(source of truth,"skills": "./.agents/skills/") plus the Codex / Cursor / Antigravity manifests generated bybun scripts/cli.ts multi-formatREADME.mdModified: all three marketplace manifests (Claude
.claude-plugin/, Codex.agents/plugins/, Cursor.cursor-plugin/),release-please-config.json+.release-please-manifest.json(plugins/deno@ 1.0.0), and rootREADME.md(Built-in Plugins entry + install list).The Claude marketplace entry carries
relevancesignals: topicDeno, cli["deno"], filesRead["**/deno.json", "**/deno.jsonc", "**/deno.lock"].Verification
claude plugin validate plugins/deno— passedclaude plugin validate .claude-plugin/marketplace.json— passed (warnings are pre-existing; none reference deno)SKILL.mdfiles hash-match upstreamdenoland/skillsHEAD byte-for-byteReviewer notes
.tessl-plugin/manifest was added. The tessl publish workflow is generic and opt-in per plugin; adding one would start publishing this plugin to an external registry on release, which is out of scope for a marketplace addition. Easy to add later if wanted.bun scripts/cli.ts multi-formatrewrites all 74 local plugins, so per.claude/rules/marketplace-sync.mdthe unrelated churn was reverted and only the deno entries inserted. That revert left two pre-existing inconsistencies onmainuntouched: the Codex marketplace (.agents/plugins/marketplace.json) is missing the sevenshunt-*entries from feat(marketplace): add shunt provider plugins #263, and both generated marketplaces have a staletanstack/shadcn-uiordering. Worth a separate follow-up commit.Related issue
None — no matching open issue found for this plugin addition.
Checklist
bun run test) — N/A: content-only plugin addition (vendored skills + manifests); validated withclaude plugin validatebun run lint)README.md+ rootREADME.md)BREAKING CHANGE:note is includedSummary by cubic
Adds a
denoplugin to the marketplace that bundles the five official Deno skills fromdenoland/skills(MIT, maintained by Deno Land). Previously no Deno skills were available; now users can installdeno@pleaseaifor core Deno usage, migration from Node/npm/yarn/pnpm/bun, Deno Deploy, Fresh frontends, and the@deno/sandboxSDK.skills-lock.json, so the existing weeklyupdate-skills.ymlworkflow tracks upstream and opens afix:PR on changes.README.md; keywords are now synced across the marketplace entry and all four plugin manifests.plugins:multi-formatandskills:update-lockspackage scripts instead of invoking script files directly.claude plugin validate; the fiveSKILL.mdfiles hash-match upstream byte-for-byte.Reviewer notes
.tessl-plugin/manifest was added, so the plugin won't publish to the external tessl registry on release.maininconsistencies untouched: the Codex marketplace is missing the sevenshunt-*entries, and both generated marketplaces have a staletanstack/shadcn-uiordering.Written for commit ccf8d24. Summary will update on new commits.