claimable-postgres
Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASE_URL for prototyping/tests, or "just give me a DB now". Triggers include: "quick postgres", "temporary postgres", "no signup database", "no credit card database", "instant DATABASE_URL", "npx neon-new", "neon.new", "neon.new API", "claimable postgres API".
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/andrelandgraf/claimable-postgresWhat This Skill Does
The claimable-postgres skill enables OpenClaw to provision instant, fully functional PostgreSQL databases without the friction of account creation, logins, or credit cards. Utilizing the neon.new infrastructure, the skill generates a ready-to-use DATABASE_URL, which the agent can inject directly into your project's environment variables. This is perfect for rapid prototyping, CI/CD testing, or demonstrating database-backed applications on the fly. Databases created through this skill are temporary, expiring automatically after 72 hours unless they are explicitly claimed to a permanent Neon account, ensuring you don't accumulate unnecessary resources.
Installation
To integrate this skill into your environment, run the following command in your terminal:
clawhub install openclaw/skills/skills/andrelandgraf/claimable-postgres
Once installed, the agent will recognize prompts related to database provisioning and trigger the appropriate integration logic.
Use Cases
This skill is designed for scenarios where speed is the priority. Developers can use it for:
- Rapidly scaffolding a database for a new feature branch.
- Providing a clean, isolated database for running test suites.
- Creating a demo environment for a prospective client or stakeholder.
- Quickly checking if a specific SQL migration or query runs as expected.
- Bypassing the setup delay when a user says "just give me a DB now."
Example Prompts
- "I need to test my new Prisma schema quickly. Can you provision a temporary Postgres database and set the DATABASE_URL for me?"
- "I'm working on a local demo, but I don't have a database ready. Can you use neon.new to get me a quick Postgres connection string?"
- "Spin up a no-signup Postgres instance for my integration tests so I can run my project without configuring local Docker containers."
Tips & Limitations
- Persistence: Databases are ephemeral. Always remember to click the provided
claim_urlif you intend to keep your data beyond 72 hours. - Connectivity: The returned connection string is pooled by default. If your tools require a non-pooled connection, simply remove
-poolerfrom the hostname string. - Automation: The agent can automatically update your
.envfile, but ensure you have file-write permissions enabled for the agent within your local environment. - Best Practices: Use this primarily for ephemeral tasks. For production environments, utilize the official Neon dashboard to provision long-term, managed database clusters.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-andrelandgraf-claimable-postgres": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: network-access, file-write, external-api
Related Skills
neon-postgres
Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
neon-postgres-egress-optimizer
Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT * optimization, query overfetching, reduce Neon costs, optimize database usage, or wants to reduce data sent from their database to their application. Also use when reviewing query patterns for cost efficiency, even if the user doesn't explicitly mention egress or data transfer.