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

91%

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

SKILL.md
Quality
Evals
Security

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.

A high-quality, dense reference body: executable code for every pattern, exact platform limits, and symptom-to-fix debugging guidance with almost no filler. The main improvements are structural — moving reference-grade API/monitoring detail into separate files — and isolating time-sensitive version and billing information so it can age without misleading.

Suggestions

Split reference-grade detail (the Context field/type list, monitoring and log-drain instructions, and the configuration key table) into one-level-deep files under references/ with clearly signaled links, keeping SKILL.md as a lean overview.

Move time-sensitive statements (Node.js 24+, CLI 27.17.0+, Early Access pricing/GA billing plans) into a dedicated compatibility/versions section so future changes are localized and the rest of the skill stays evergreen.

Add an explicit pre-deploy validation step in the entry-file section (e.g., confirm exactly one netlify/server/index.* file exists and the default export matches a row in the detection table before running netlify deploy) to close the workflow's only feedback-loop gap.

DimensionReasoningScore

Conciseness

The body is dense with platform-specific facts Claude cannot know ("Outbound connections are closed after 60 s without data", "Self-started servers must listen within 10 s", concurrency-by-size table, 7-step shutdown sequence) and assumes competence about Express/Fastify/WebSockets themselves. It falls short of 5 because time-sensitive material — "Node.js 24+", "Netlify CLI 27.17.0+", "It is free during Early Access... At GA it will bill credits" — is not isolated in an old-patterns/deprecated section, and some billing/plan framing could be trimmed. Not 3, since there is essentially no padding or explanation of known concepts.

4 / 5

Actionability

Every major pattern ships copy-paste-ready code: the handler export with config, Express and Fastify self-started apps, waitUntil, both WebSocket styles (upgradeWebSocket and ws-on-listen) with the "return response; // return as is" caveat, SSE ReadableStream, lifecycle hooks, edge-cache headers, and netlify logs CLI invocations. Config keys, limits, and a status-code-to-fix table give exact values, matching the fully-executable level-5 anchor.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced (startup steps 1-4, shutdown sequence 1-7, request routing order 1-5) and debugging has strong feedback loops: the "Server gets no requests?" checklist, the 429/500/501/502 table mapping symptoms to causes and fixes, and "failed-start warnings" in the Instances table. It misses 5 because there is no explicit validate-before-proceeding checkpoint in the build/deploy path itself (e.g., verify the entry file's default export shape before deploying); not 3 because sequences are complete and error recovery is well covered.

4 / 5

Progressive Disclosure

A single 364-line file with no bundle; the body has clear, well-ordered sections (detection, examples, config, routing, lifecycle, limits, errors, local dev) with tables and warning callouts that make navigation easy, matching the level-4 anchor of good structure with minor gaps. It misses 5 because reference-grade material (the full Context field list and exported types, monitoring/log-drain details, the config key table) is inlined in SKILL.md rather than split into one-level-deep reference files, which would keep the overview leaner; not 3 because nothing is buried and the organization is consistently strong.

4 / 5

Total

17

/

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: explicit what and when, concrete triggers covering frameworks, real-time protocols, and specific error symptoms, all in dense specific language with no fluff. The only weakness is mild overlap risk with general Netlify deployment/CLI skills via the ancillary topics (netlify dev, logs, region settings).

DimensionReasoningScore

Specificity

Quotes 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", "background work after responding with waitUntil", "startup and graceful shutdown hooks", "edge caching of server responses". Coverage is comprehensive across build, runtime, config, testing, logs, and debugging, matching the level-5 anchor (multiple specific concrete actions); it is dense with specifics rather than padded, so not lower.

5 / 5

Completeness

Explicitly answers both questions: the first sentence states what it does ("Build and deploy a long-lived Node.js backend on Netlify Server (Early Access) from netlify/server/index.ts") and "Use this skill whenever someone wants to..." lists concrete when-triggers, exactly matching the level-5 exemplar pattern. Not 4, because the 'when' clause is fully explicit with multiple concrete trigger phrases, not merely adequate.

5 / 5

Trigger Term Quality

Includes the natural phrases users would say: framework names ("Express, Fastify, Hono or Koa"), "REST/GraphQL API", "chat, live dashboards or multiplayer", "WebSockets or Server-Sent Events", "stream AI responses", "netlify dev", "netlify logs", "drops database connections after a minute", "429/500/501/502". This covers synonyms and concrete failure symptoms, matching the comprehensive level-5 anchor; no common variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

The core niche is distinct (long-lived Node backends, warm DB pools, WebSockets/SSE on Netlify Server, clearly separated from Functions), but the trailing coverage — "local testing with netlify dev, reading server logs with netlify logs or log drains", "region/size/scale settings" — overlaps with generic Netlify deploy/CLI skills, matching the level-4 anchor (mostly distinct; minor overlap risk with closely related skills). Not 5 because of that overlap with adjacent Netlify skills; not 3 because the primary triggers are unmistakably server-specific.

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

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.