# Build with Neon Serverless Postgres

Choosing safe Neon connection and deployment patterns can be difficult across runtimes. This skill guides setup, drivers, branching, authentication, scaling, and automation using current Neon documentation.

## Install

```bash
npx skillstore add sickn33/neon-postgres
```

## Metadata

- Status: approved
- Slug: sickn33-neon-postgres
- Skillstore revision: r2
- Version status: missing
- Tree hash: 4f0cd6b02f91b5f009e684897aa9556f2168cf17225cc16ed562cf8f918da35b
- Author: sickn33
- GitHub username: sickn33
- License: Apache-2.0
- Repository: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/neon-postgres
- Ref: 81e05e636292629114b76cbb3922fbe57672fc02
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sickn33-neon-postgres
- Manifest: https://skillstore.pages.dev/api/skills/sickn33-neon-postgres/manifest

## Capabilities

- Selects Neon connection drivers for persistent, edge, and isolated serverless runtimes.
- Guides project setup with the Neon CLI, MCP server, environment variables, and supported ORMs.
- Explains database branching, instant restore, read replicas, autoscaling, and scale-to-zero.
- Provides connection pooling guidance for PgBouncer, node-postgres, and Neon serverless drivers.
- Covers Neon Auth, REST API, TypeScript SDK, Python SDK, and infrastructure configuration.
- Links recommendations to official Neon documentation for current implementation details.

## Use Cases

- Connect a web application: Choose a compatible driver, configure DATABASE\_URL, add an ORM, and apply safe pooling for the deployment runtime.
- Design preview environments: Plan isolated Neon branches, migration testing, expiration policies, and deployment integration for development teams.
- Scale a Postgres workload: Evaluate autoscaling, scale-to-zero, read replicas, recovery, and logical replication for production requirements.

## Prompt Templates

### Choose a connection

```
Review my [framework] application deployed on [platform]. Recommend the correct Neon driver, environment variables, and a safe setup checklist.
```

### Add database branching

```
Design a Neon branching workflow for [team and deployment platform]. Include branch creation, migration testing, expiration, and cleanup steps.
```

### Configure production access

```
Recommend pooling, role permissions, IP restrictions, and secret handling for this [runtime and traffic profile]. Explain operational trade-offs.
```

### Audit a Neon architecture

```
Audit this Neon architecture for connection limits, pooling, autoscaling, scale-to-zero, recovery, and least privilege. Cite current official documentation for every recommendation.
```

## Limitations

- The skill does not provide Neon credentials, accounts, subscriptions, or project access.
- Commands and service behavior require verification against current Neon documentation before execution.
- Examples require adaptation and testing for each framework, runtime, security model, and deployment platform.
- Cloud changes, credential handling, and package installation require user review and approval.

## Best Practices

- Verify commands and product behavior with current official Neon documentation.
- Keep credentials in environment variables, redact secret values, and use least-privilege database roles.
- Review plans and request approval before installing packages or changing cloud resources.

## Anti Patterns

- Do not commit connection strings, API keys, or populated environment files.
- Do not create a new connection pool for every request in a shared runtime.
- Do not run unpinned installation or cloud-changing commands without reviewing their source and effects.

## Security Audit

- Audited at: 2026-08-04T15:32:22.025\+00:00
- Summary: Most static alerts are false positives caused by Markdown backticks, code fences, official links, and standard process.env examples. Confirmed risks are unattended remote installation, cloud-changing Neon CLI commands, and instructions to inspect .env files containing database credentials. No prompt injection or exfiltration intent was found.

## Stats

- Views: 167
- Downloads: 11
- Favorites: 0
- Popularity score: 0