Skip to main content
skill CX Codex

vercel-labs-emulate — Claude Code skill: local API emulation

Spins up local HTTP servers that stand in for Vercel, GitHub and Google APIs. Useful when CI or a sandbox has no network but tests still need real state.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add reason-machines/trending-skills --skill vercel-labs-emulate -a claude-code
Open on GitHub

What vercel-labs-emulate does

The skill covers emulate, a set of local servers that take the place of Vercel, GitHub and Google APIs. State lives in memory, and pagination, OAuth, webhooks and cascading deletes behave the way they do in production. Your tests get real responses instead of stubs.

Start it from the CLI: npx emulate brings up every service, npx emulate --service vercel,github picks two, npx emulate --port 3000 sets the base port. Vercel listens on http://localhost:4000, GitHub on http://localhost:4001, Google on http://localhost:4002. You can also set the port through EMULATE_PORT or PORT. A programmatic API exists too: createEmulator({ service: 'github', port: 4001 }) hands back an object with url, reset() and close().

Seed data comes from emulate.config.yaml at the project root, or from an inline seed object. Run npx emulate init to generate the file. Leave oauth_apps out of the config and any client_id is accepted; configure the apps and validation becomes strict. For GitHub Apps, sign the JWT with RS256 and iss set to app_id — the emulator checks the signature.

What it helps with

  • run GitHub client tests without hitting api.github.com
  • bring up a Vercel API inside a CI job with no outbound traffic
  • exercise an OAuth redirect against a local server
  • wipe state between tests with reset()
  • seed repos and orgs before a test run

Example prompts for the agent

  • Start local GitHub and Vercel emulation for the test suite
  • Generate emulate.config.yaml for the github service
  • Wire vitest.setup.ts so the emulator boots before all tests

How to install vercel-labs-emulate

1Skills CLI (Vercel)

npx skills add reason-machines/trending-skills --skill vercel-labs-emulate -a claude-code

2Manually: put the files in place

~/.claude/skills/vercel-labs-emulate/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/vercel-labs-emulate/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about vercel-labs-emulate

How do I install vercel-labs-emulate in Claude Code?

Run npx skills add reason-machines/trending-skills --skill vercel-labs-emulate -a claude-code. The skill lands in ~/.claude/skills/vercel-labs-emulate/SKILL.md.

What does vercel-labs-emulate do?

It documents local HTTP servers that replace the Vercel, GitHub and Google APIs. State is in-memory, with pagination, OAuth and webhooks.

What do I need to run the emulator?

Launch it with npx emulate, or add it as a dev dependency via npm install --save-dev emulate. Seed data goes in emulate.config.yaml or an inline seed object.

Similar skills

All skills for Testing and QA →

From the same set139

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor