Neon CLI

Run bunx neonctl@latest from the user's project directory, where the nearest .neon context resolves. Never install neonctl globally or through npm, npx, pnpm, or yarn. Helpers live under the skill directory:

NEON_SKILL_DIR="${NEON_SKILL_DIR:-$HOME/.agents/skills/neon-cli}"

Explicit user instructions override anything below.

Access

NEON_API_KEY in the environment authenticates everything. Keys, database passwords, connection strings, and generated .env values never appear in output, logs, or commits. bash "$NEON_SKILL_DIR/scripts/neon-ensure.sh" checks Bun, neonctl, psql, jq, the key, local context, and authentication with one read-only request; run it only when the task needs live access. Interactive neonctl auth opens a browser and needs the user's explicit request. Missing clients are reported with the OS-appropriate package, never installed automatically.

Some neonctl versions render environment-backed defaults in help output, so inspect help with the key removed: env -u NEON_API_KEY bunx neonctl@latest <command> --help. Current help beats any example here; for version-sensitive behavior beyond it, use Context7 with official Neon docs.

Target one-off commands with --project-id "$PID" and --output json. Link only for repeated repository work, and since link and checkout pull env vars into .env by default, pass --no-env-pull unless the user wants that: