Claimable Postgres

ReviewAudited by ClawScan on May 1, 2026.

Overview

The skill is coherent for creating temporary Neon Postgres databases, but users should notice that it can run latest-version tooling and store generated database access URLs in a project .env file.

This appears reasonable for quick temporary Postgres setup. Before using it, decide whether you want the REST API, CLI, or plugin path; avoid committing generated .env values; avoid putting sensitive data into a throwaway database; and consider pinning or reviewing external packages if using the CLI or Vite plugin.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the CLI method is used, the package version may change over time and can modify the project .env file.

Why it was flagged

The documented CLI workflow executes the latest version of an external package rather than a pinned version. This is central to the skill, but users have less control over exactly what code runs.

Skill content
`npx neon-new@latest --yes` ... `Always use @latest and --yes`
Recommendation

Prefer the REST API path for minimal local execution, or pin/review the CLI package version before use in sensitive projects.

What this means

Anyone who can read the .env value may be able to connect to the temporary database until it expires or is rotated.

Why it was flagged

The generated database connection string is an access-bearing credential for the temporary database. Storing it in .env is expected, but it still needs normal secret-handling care.

Skill content
Write `connection_string` to the project's `.env` as `DATABASE_URL`.
Recommendation

Confirm the target .env file, keep generated URLs out of source control, and only use throwaway or non-sensitive data unless the database has been properly secured.

What this means

A future local dev run could create a new temporary database if the environment variable is absent.

Why it was flagged

Installing the optional plugin can create continuing project behavior that provisions a database later when the dev server starts. The artifact discloses this, and it fits the skill purpose.

Skill content
`vite-plugin-neon-new`: Auto-provisions on `vite dev` if `DATABASE_URL` is missing.
Recommendation

Use the plugin only when this automatic behavior is desired, and remove or disable it after the temporary setup is no longer needed.