In brief
This skill guides the choice and setting of Vercel functions: Functions Node.js (full npm ecosystem), Edge Functions (V8 isolates, useful for auth or redirection as close to user), and, in public beta, a runtime Bun (`bunVersion: "1.x"` in `vercel.json`, about 28% less latency on processor-related loads) or Rust (Fluid Compute, HTTP flux, environment variables up to 64 KB). Fluid Compute is the unified execution model. Without this model, the maximum duration indicated is 10 s on the Hobby offer and 300 s by default in Pro, up to 800 s in Fluid Compute Pro or Enterprise; With Fluid, the default time is 300 s on all planes, and up to 800 s in Pro or Enterprise. Edge Functions have a hard limit of 25 s, unconfigurable.Streaming works as well in Node as in Edge: there is no need to force Edge for Server-Sent Events. WebSockets rely on Fluid Compute; There is no lasting state in memory of one instance to another, and Socket.IO must impose `websocket` transport. The `now.json` file is abandoned on March 31, 2026: it is renamed `vercel.json` without changing the content. On Fluid Compute, the package can be up to 5 GB and the query body up to 100 MB. Cold start, with basic connections, is given between 800 ms and 2.5 s. The CPU "Basic" instance has disappeared; Hobby projects use the Standard CPU.
What it does
- Helps to choose the runtime (Node, Edge, Bun or Rust in public beta) according to the API and latency desired.
- Recalls the time limits (Hobby, Pro, Fluid, Edge 25 s) and the size of the package or body on Fluid Compute.
- Configures HTTP feed, background tasks (`waitUntil`, `after`) and Fluid-compatible WebSockets, without durable memory status.
- Report the withdrawal of `now.json` to March 31, 2026 and the transition to `vercel.json`.
Who it is for, and an example
Teams that write or debug server code to Vercel and must separate Node, Edge, Fluid Compute, the feed or a cron, without the wrong time limit.
Example request: " This streaming route sometimes exceeds Hobby's deadline: tell me if Fluid Compute is enough, if you have to stay in Node rather than Edge, and what the 25 s ceiling on Edge's side changes. »
To open to configure, explain or optimize a Vercel function, runtime, cron, stream or WebSocket connection on the platform. Example written by iadujour.fr from the SKILL.md, not tested.
Install
In Codex: codex plugin add vercel@openai-curated (Official Place of Deposit).
codex plugin add vercel@openai-curatedWorks with
- Codex
Source: README: Codex plugin collection; the deposit marketplace is called "Official Codex". Other officers are not appointed.
Level: Beginner
Use in natural language; no code prerequisites are required by the description, beyond the product concerned.
Good to know
SKILL.md excerpt
The original description, which the agent reads to decide whether to load the skill (in English):
Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.
Quoted from SKILL.md at commit 33bd952 . The folder also contains 1 extra file (agents/).
The SKILL.md has 371 lines and 28 main sections:
- Function Types
- Serverless Functions (Node.js)
- Edge Functions (V8 Isolates)
- Bun Runtime (Public Beta)
- Rust Runtime (Public Beta)
- Node.js 24 LTS
- Choosing Runtime
- Fluid Compute
- Instance Sizes
- Background Processing with `waitUntil`
- Next.js `after` (equivalent)
- Streaming
- WebSockets
- `ws` (no extra config)
- Socket.IO
- Next.js
- Reconnects and persistent state
- Cron Jobs
- Configuration via vercel.json
- Timeout Limits
- Common Pitfalls
- Function Runtime Diagnostics
- Timeout Diagnostics
- 500 Error Diagnostics
- Invocation Failure Diagnostics
- Cold Start Diagnostics
- Edge Function Timeout Diagnostics
- Official Documentation
Licence: No licence found
Checked on 10 November 2026 : no licence file in the skill folder or at the repository root.
No licence found: short excerpt quoted only (quotation right). For the full text, see the source.
Comments.
A field note, a question, a precision on this skill? Comments are reviewed before publication.
Published comments
Loading comments…
Leave a comment
Moderation charter. Every comment is reviewed before publication. We refuse hate speech, insulting or discriminatory language, advertising, spam and promotional links, off-topic posts and other people’s personal data.