CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

netlify-server

Build and deploy a long-lived Node.js backend on Netlify Server (Early Access) from netlify/server/index.ts. Use this skill whenever someone wants to run an Express, Fastify, Hono or Koa app on Netlify as it is, add a backend or REST/GraphQL API that keeps database pools and caches warm, build real-time features such as chat, live dashboards or multiplayer with WebSockets or Server-Sent Events, or stream AI responses and run agent loops. It also covers background work after responding with waitUntil, startup and graceful shutdown hooks, load-aware health checks, edge caching of server responses, region/size/scale settings, local testing with netlify dev, reading server logs with netlify logs or log drains, and debugging a server that gets no requests, fails to start, drops database connections after a minute, or returns 429/500/501/502.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is netlify-server in netlify/context-and-tools

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 high-quality, information-dense body: nearly everything is platform-specific, executable, and organized around real failure modes with concrete fixes. The main structural weakness is that it is a single monolithic ~340-line file with zero progressive disclosure — the API reference, config tables, and monitoring details could live in one-level-deep reference files — and there are small patches of general-knowledge content that could be trimmed.

Suggestions

Split detailed reference material into one-level-deep bundle files (e.g., references/config.md for the configuration key table, references/context-api.md for the context fields and types, references/monitoring.md for the Server page and log-drain walkthrough), keeping SKILL.md as a lean overview with clearly signaled links.

Trim or shorten content Claude already knows, such as the client-reconnect example ("Browser WebSocket doesn't reconnect on its own; EventSource does") — keep only the platform-specific detail like closing with code 1012.

Add a brief end-to-end sequence (install @netlify/server → write entry file → export correctly → set config → verify locally with netlify dev → deploy → check the Server page/logs) so the reference sections hang off an explicit build-and-verify workflow.

DimensionReasoningScore

Conciseness

The body is dense platform-specific fact (entry-file detection table, 60 s outbound idle rule, shutdown sequence, error table, house rules) that Claude cannot know, with almost no padding or explanation of known concepts. Minor trimmable spots remain: the client-reconnect section largely restates general browser knowledge ("Browser WebSocket doesn't reconnect on its own; EventSource does") and the monitoring UI walkthrough narrates page layouts in detail. This matches "efficient; minor instances of over-explanation that could be trimmed" rather than 5's "every token earns its place".

4 / 5

Actionability

Guidance is copy-paste ready throughout: working handler and framework starter code, executable waitUntil/WebSocket/SSE/hook examples with the exact API calls, a concrete config TOML, CLI commands with flags ("netlify logs --source server --since 30m"), and an error table mapping each status code to a specific fix. Common cases (Express, Fastify, Hono, ws, self-started servers) are each covered by example. This matches the fully-executable anchor; not 4 because there are no significant gaps in code completeness.

5 / 5

Workflow Clarity

Key processes are explicitly sequenced with numbered lists (startup: PORT → import → onStart → export inspection; shutdown: 7 ordered steps with timeouts) and troubleshooting is checklist-driven ("Server gets no requests? Check these causes...", the Errors table, the 60 s connection-notice symptom→fix). However, there is no single end-to-end build→test→deploy→verify path; guidance is organized as reference sections rather than a sequenced procedure, and verification steps (e.g., confirming a deploy started) are implicit. This fits "clear sequence with most checkpoints present; minor validation gaps"; the destructive/batch cap does not apply since the skill involves no batch/destructive operations.

4 / 5

Progressive Disclosure

The file is well-organized with clear section headers, but there are no bundle files at all — references/, scripts/, and assets/ do not exist — so nothing is split out. Detailed reference material that plausibly belongs in separate files is inlined in the ~340-line body: the Context API field/type listing, the full configuration key table, the monitoring/logs UI walkthrough, and log-drain details. With no external references and substantial inlined reference content, this matches "some structure... content that should be separate is inline" rather than 4's "most content is appropriately placed".

3 / 5

Total

16

/

20

Passed

Description

96%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: concrete, comprehensive, third-person, with an explicit "Use this skill whenever" trigger clause covering frameworks, feature types, and debugging symptoms. The only weakness is mild overlap risk with a hypothetical Netlify Functions skill on generic "run my app on Netlify" triggers.

DimensionReasoningScore

Specificity

The description lists many concrete actions — "Build and deploy a long-lived Node.js backend on Netlify Server... from netlify/server/index.ts", "run an Express, Fastify, Hono or Koa app", "build real-time features such as chat, live dashboards or multiplayer with WebSockets or Server-Sent Events", "stream AI responses and run agent loops", plus caching, hooks, logging, and specific debugging symptoms ("drops database connections after a minute, or returns 429/500/501/502"). Coverage is comprehensive across build, deploy, real-time, background work, config, local dev, logs, and troubleshooting, matching the anchor for multiple specific concrete actions. Not 4: there are no meaningful coverage gaps — even failure modes and tooling commands are named.

5 / 5

Completeness

It explicitly answers "what" ("Build and deploy a long-lived Node.js backend on Netlify Server (Early Access) from netlify/server/index.ts") and "when" with an explicit trigger clause ("Use this skill whenever someone wants to run an Express, Fastify, Hono or Koa app..., add a backend or REST/GraphQL API..., build real-time features..., or stream AI responses"), plus debugging triggers. This matches the anchor for clearly and explicitly answering both what and when with concrete trigger phrases. Not 4: the "when" clause is not merely present but enumerates multiple concrete trigger scenarios.

5 / 5

Trigger Term Quality

Natural trigger phrases a user would actually say are comprehensively covered: framework names ("Express, Fastify, Hono or Koa"), "backend or REST/GraphQL API", "chat, live dashboards or multiplayer", "WebSockets or Server-Sent Events", "stream AI responses", "netlify dev", "netlify logs", and concrete error codes (429/500/501/502). Synonym-level coverage (e.g., both WebSockets and SSE, both REST and GraphQL, multiple real-time use cases) matches the comprehensive-coverage anchor. Not 4: only trivial variations like the "SSE" abbreviation are absent, which does not constitute "a few natural terms missing".

5 / 5

Distinctiveness Conflict Risk

The niche is clear — long-lived Node.js backend on Netlify Server with warm pools, WebSockets/SSE, and waitUntil — which is distinct from generic deploy skills. However, triggers like "run an Express, Fastify, Hono or Koa app on Netlify as it is" and "add a backend... API" overlap with what a Netlify Functions skill would also claim (the body itself notes functions as an alternative), so a closely related skill could compete for the same query. This matches "mostly distinct; minor overlap risk with closely related skills" rather than 5's "minimal conflict risk".

4 / 5

Total

19

/

20

Passed

Validation

100%

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

netlify/context-and-tools

Path

codex/skills/netlify-server/SKILL.md

Reviewed

Table of Contents

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.