neon-clilisted
Install: claude install-skill arthjean/skills
# Neon CLI
Operate Neon through `bunx neonctl@latest`, `psql`, and the bundled shell helpers. Keep the working directory in the user's project so `neonctl` can resolve the nearest local `.neon` context.
## Operating contract
1. Use the absolute directory containing this `SKILL.md` as `NEON_SKILL_DIR`. In a standard user installation:
```bash
NEON_SKILL_DIR="${NEON_SKILL_DIR:-$HOME/.agents/skills/neon-cli}"
```
2. Do not `cd` into the skill directory before running Neon commands. The current project directory determines which `.neon` context is active.
3. Use `bunx neonctl@latest`. Do not install `neonctl` globally and do not use npm, npx, pnpm, or yarn.
4. Prefer native `neonctl` commands. Use bundled scripts only for SQL workflows that need `psql`.
5. Preserve secrets. Never print, log, commit, or return `NEON_API_KEY`, database passwords, connection strings, or generated `.env` values.
6. Keep browser use opt-in. Do not run interactive `neonctl auth` unless the user explicitly requested browser authentication.
7. Require an explicit destructive intent and an unambiguous target before project deletion, branch deletion, reset, restore, `DROP`, or destructive DML. Do not infer these actions from a general request to manage or fix a database.
## Preflight
Run the bundled preflight only when the task actually needs Neon access:
```bash
bash "$NEON_SKILL_DIR/scripts/neon-ensure.sh"
```
It checks `bun`, current `neonctl`, `psql`, `jq`, `NEON_API_KEY`, local conte