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.
When an app or agent needs to call an LLM and the user wants one credential, model portability, or branch-scoped AI without managing multiple provider accounts.
preview.aiGateway in neon.ts and run neon deploy to provision the gateway on a branch.NEON_AI_GATEWAY_* env vars; use @neon/ai-sdk-provider or Mastra neon/<model> for zero-config access.A working inference request or configured agent using a single Neon credential across multiple model providers, with branch isolation and streaming support.
Use Cases
A startup builds a chatbot and wants to avoid managing separate OpenAI and Anthropic accounts. Using this skill, they enable aiGateway in neon.ts, deploy with `neon deploy`, and call Claude or GPT via the Neon credential. They get one billing relationship, branch-isolated preview environments, and can switch models by changing one field — accelerating development without infra overhead.
A team runs CI preview branches and needs isolated AI calls per branch. With this skill they use neon.ts checkout to auto-enable the gateway per branch, inject credentials to .env.local, and build agents via @neon/ai-sdk-provider. Each preview branch gets its own gateway host, so AI requests are scoped like DB data — making testing safe and self-contained without cross-branch leakage.
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