cloudflare-nextjs

Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG/App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker size/runtime/keep_names/FinalizationRegistry/connection-scoping errors.

Quality

93%

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

86%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 strong, dense operational reference: executable commands and exact error fixes throughout, an excellent one-level-deep reference structure with a load-condition table, and no beginner padding. The main weaknesses are duplicated source/version listings that cost tokens and an implicit rather than explicit error-recovery loop around the preview-then-deploy workflow.

Suggestions

Remove the body's 'Sources' section (20 URLs duplicated verbatim from frontmatter metadata), keeping only the live issue-tracker link inline, to reclaim tokens and lift conciseness.

Make the deploy feedback loop explicit: after the scripts section, add a short 'if preview fails → match the error in the Top Errors section / references/error-catalog-extended.md, apply the fix, re-run preview' step so validation-retry is inline rather than implied.

Consolidate scattered version/date strings (requirements table, per-error mentions, footer) into the single 'Critical Requirements' table and reference it from elsewhere in the body.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no padding explaining what Cloudflare or Next.js is), but there is trimmable redundancy: the 20 source URLs are duplicated between frontmatter and the body's 'Sources' section, and version/date strings repeat across the requirements table, error section, and footer. This fits the 4 anchor ('minor instances of over-explanation that could be trimmed') rather than 5 ('every token earns its place').	4 / 5
Actionability	Guidance is copy-paste ready throughout: 'npm create cloudflare@latest -- my-next-app --framework=next --platform=workers', 'npx @opennextjs/cloudflare migrate', complete package.json script definitions, runnable TypeScript snippets, and error fixes with exact edits ('Set "compatibility_date": "2025-05-05" in wrangler.jsonc', '"keep_names": false'). Specific examples cover the common cases, matching the 5 anchor.	5 / 5
Workflow Clarity	The sequence is clear (new vs. existing project → four scripts → deploy) with an explicit checkpoint ('preview — runs in the actual Workers runtime... Always run before deploy to catch runtime-only issues'). It falls short of the 5 anchor because the validate→fix→retry feedback loop is implicit — failures route to a separate error catalog rather than an inline recovery step.	4 / 5
Progressive Disclosure	Structure is exemplary: a 'When to Load References' table maps all 12 real reference files (verified present in ./references/) to specific load conditions, all one level deep, with condensed inline summaries ('Full patterns → references/bindings-and-services.md'). This matches the 5 anchor — clear overview, well-signaled references, content appropriately split.	5 / 5
	Total	18 / 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 exemplary description: third-person, concrete, and specific, with an explicit 'Use for' trigger clause covering deployment topics, bindings, caching, and exact error strings. It is clearly distinguishable from adjacent Next.js and Cloudflare skills because every trigger is scoped to the Workers platform via the OpenNext adapter.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions and capabilities — 'Deploy Next.js to Cloudflare Workers via the OpenNext adapter', 'getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars' — with comprehensive coverage spanning setup, API access, caching, integrations, and error scenarios. It clearly matches the 5 anchor rather than 4, which only allows minor gaps in coverage.	5 / 5
Completeness	It explicitly answers both: what ('Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare)') and when ('Use for SSR/ISR/SSG/App or Pages Router, getCloudflareContext, bindings...') with concrete trigger phrases. This is the exact shape of the 5 anchor; the 'when' clause is explicit, not merely present as at 4.	5 / 5
Trigger Term Quality	Natural user phrasing is comprehensively covered: 'Deploy Next.js to Cloudflare Workers', 'SSR/ISR/SSG', 'App or Pages Router', 'env vars', plus verbatim error names users would paste ('worker size', 'keep_names', 'FinalizationRegistry', 'connection-scoping'). This matches the 5 anchor's bar of synonyms and exact technical triggers; it is not merely 'good coverage with a few missing' (4).	5 / 5
Distinctiveness Conflict Risk	The niche is clear — Next.js on Cloudflare Workers via this specific adapter — and Workers-specific triggers (getCloudflareContext, worker size, skew protection) make it unlikely to fire for a generic nextjs or cloudflare-workers skill. Minor theoretical overlap with adjacent skills is not enough to drop to the 4 anchor.	5 / 5
	Total	20 / 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
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/cloudflare-nextjs/skills/cloudflare-nextjs/SKILL.md
Commit: 8837836

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