Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
Use when building long-running request/response handlers (agents, SSE, WebSockets, webhooks) that need to stay close to Neon Postgres and exceed traditional serverless time limits.
neon.ts under preview.functions with slug, name, source.neon dev (hot reload, env injected); deploy via neon deploy or neon functions deploy.DATABASE_URL automatically, branch-scoped with own URL.A deployed public HTTPS function next to the database, a local dev loop, or precise doc answers — scalable, stateful, branch-isolated backend primitives.
Use Cases
A team builds a Next.js app on Vercel but needs a WebSocket server for live collaboration that outlasts Vercel's serverless limits. They use this skill to declare a function in neon.ts, run `neon dev` locally, then `neon deploy` to branch. The function runs next to Postgres with injected DATABASE_URL, giving a stateful, branch-isolated backend without Redis. Value: no timeout, low latency, easy preview per branch.
An AI agent makes multiple LLM and tool calls per request, exceeding ~60s serverless caps. A developer uses this skill to build a long-running Hono fetch handler deployed as a Neon Function. Local `neon dev` validates streaming; `neon functions get` returns the public URL. The agent backend stays alive, holds in-process state, and queries Postgres with zero cross-region lag. Value: supports real agent workloads with open streams.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File