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

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.

The body is an unusually dense, accurate, and executable reference: concrete code for every feature, exact numeric limits, clear do/don't examples, and well-sequenced platform lifecycles with an error-to-fix table. Its main weaknesses are token efficiency at the margins (generic browser reconnect advice, billing detail, meta-comments) and the absence of any progressive disclosure — everything, including API reference tables, is inlined in one long file.

Suggestions

Move reference-grade material into bundle files (e.g. references/context-api.md for the Context fields and Types list, references/configuration.md for the config key table, references/monitoring.md for the logs walkthrough) and link to them from short sections in SKILL.md.

Cut the client-reconnect subsection (EventSource auto-reconnect is standard browser knowledge Claude already has) and trim the GA billing paragraph to the one actionable fact, keeping only the 1012 close-code convention.

Add a short numbered 'first deploy' sequence near the top (npm install @netlify/server → create netlify/server/index.ts → netlify dev → deploy) so the end-to-end workflow is explicit rather than implied across sections.

DimensionReasoningScore

Conciseness

The body is dense with platform-specific facts Claude cannot know elsewhere ('Outbound connections are closed after 60 s without data... TCP keepalives don't count', 'listen within 10 s', 'Closed sockets with code 1012'), but a few passages restate generic knowledge ('Browser WebSocket doesn't reconnect on its own; EventSource does') and the GA billing paragraph plus trailing gap comments add tokens without runtime value. It sits above anchor 3 ('some unnecessary explanation') but short of anchor 5's 'every token earns its place'.

4 / 5

Actionability

Nearly every section provides copy-paste-ready, complete code or commands with specific values: the handler export, Express/Fastify examples, 'idleTimeoutMillis: 30_000', upgradeWebSocket usage, lifecycle hooks, cache headers, config TOML, and 'netlify logs --source server --follow'. The error table maps each status (429/500/501/502) to a concrete fix, fully matching the anchor-5 'copy-paste ready... common cases' example.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced: startup steps 1-4 ('PORT is set' → import → onStart → inspect export), shutdown sequence 1-7, and the routing order 1-5, plus a 'Server gets no requests?' cause checklist and a status→fix error table that act as feedback loops. It falls short of anchor 5 because there is no single end-to-end 'first deploy' sequence tying install, entry file, local dev, and deploy together.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so all ~360 lines live inline in SKILL.md, including reference-grade material — the Context API field list, the exported Types enumeration, the configuration key table, and the monitoring/logs walkthrough — that clearly belongs in separate files. Sections and headers are well organized (above anchor 2's 'minimal structure'), but the situation matches anchor 3: 'content that should be separate is inline', and the score-5 exception only applies to skills under 50 lines.

3 / 5

Total

16

/

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.

The description is explicit, specific, and trigger-rich: it states what the skill does, gives an explicit 'Use this skill whenever...' clause with concrete natural-language triggers, and covers build, run, operations, and debugging capabilities. It stays in third person and carries no vague filler despite its length. This is an anchor-matching example across all four dimensions.

DimensionReasoningScore

Specificity

The description lists many concrete actions — 'Build and deploy a long-lived Node.js backend', 'run an Express, Fastify, Hono or Koa app', 'background work after responding with waitUntil', 'startup and graceful shutdown hooks', 'edge caching', 'debugging a server that... returns 429/500/501/502' — with comprehensive coverage of build, run, and debug scenarios. Not 4, because anchor 4 requires 'minor gaps in coverage' and no meaningful capability of the skill is absent.

5 / 5

Completeness

It explicitly answers both questions: what ('Build and deploy a long-lived Node.js backend on Netlify Server (Early Access) from netlify/server/index.ts') and when ('Use this skill whenever someone wants to...'), with concrete trigger phrases. This matches the anchor-5 example pattern of 'what + Use when...' exactly.

5 / 5

Trigger Term Quality

It includes the natural terms users would actually say: framework names ('Express, Fastify, Hono or Koa'), 'chat, live dashboards or multiplayer', 'WebSockets or Server-Sent Events', 'stream AI responses', 'netlify dev', 'netlify logs'. Not 3 or 4, because both common variations and specific tool names are covered, matching the comprehensiveness of the anchor-5 example.

5 / 5

Distinctiveness Conflict Risk

'Netlify Server (Early Access)' and 'netlify/server/index.ts' carve out a clear niche with distinct triggers (specific frameworks on Netlify, WebSocket/SSE backends), so it is unlikely to fire for the wrong skill. Not 4, because it even distinguishes its scope from adjacent Netlify features like functions and scheduled work, leaving minimal overlap risk.

5 / 5

Total

20

/

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

agent-plugin/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.