This skill is designed for Lakebase Postgres on Neon: if a DATABASE_URL exists, use it directly; otherwise, use the Neon CLI or MCP to select an organization and project, retrieve the connection string, and write it to .env (read before writing to avoid overwriting). The content covers choosing between pooling and direct connections, migrations, branching with schema-only structures and creating branches per PR, auto-scaling and scaling to zero, instant restore, read replicas, egress traffic optimization, and Lakebase search. Authentication, real-time data, and other features are handled by other Neon skills in the same repository.
Why it matters Use existing database connection strings first to avoid creating duplicate projects, and clarify common pitfalls such as pooling versus direct connections, opening branches per PR, and pausing due to over-quota usage.
skills.sh installs 313997 (+881 / 24h)
Security Audit: Not audited
- Not yet scanned
Rationale
- skills.sh installs 881 in the last 24 hours, with a cumulative total of 313997 (indicating attention only)
- SKILL.md has been read from the repository
Usage
- After installation, say "Create a Neon branch for each PR" or "This query traffic is too high, help me optimize it"
Risks
- It has not yet undergone automated desktop auditing, and the website does not display install commands; a Neon account is required, and it will modify the .env file in your project.
- If the parent neon skill is missing, it will instruct the agent to pull from the Neon website or use the neon command to install, effectively installing another skill.