neon
Inspect Neon serverless Postgres: projects, branches, databases. Branch create and delete need exact-match confirmation; connection passwords are masked. Trigger phrases: neon, serverless postgres, database branch, postgres project.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- neon
- tagline
- Inspect Neon serverless Postgres projects, branches, and databases. Branch create and delete need exact-match confirmation; connection passwords are masked.
- metadata
- { "includeInPrompt": true }
- description
- Inspect Neon serverless Postgres: projects, branches, databases. Branch create and delete need exact-match confirmation; connection passwords are masked. Trigger phrases: neon, serverless postgres, database branch, postgres project.
- catalog_auth
- API key (per-user)
- catalog_hosts
- [ "console.neon.tech" ]
02 资源文件 1
- 脚本bin/neon.py8.1 KB
03 SKILL.md 正文
Neon
Purpose
Manage Neon serverless Postgres infrastructure through the Neon Management API: list projects, inspect one project, list branches, create or delete a branch, and list databases. Reach for this when the user wants to inspect or provision database infrastructure. SQL queries run over the Postgres wire protocol, so this connector manages infrastructure only; it does not run queries.
Tooling
All commands go through bin/neon.py:
bin/neon.py auth # verify the API key
bin/neon.py projects # list projects
bin/neon.py project-get --project-id PROJ_ID # one project
bin/neon.py branches --project-id PROJ_ID # list branches
bin/neon.py branch-create --project-id PROJ_ID --name dev \
--confirm "create branch dev in project PROJ_ID" # create a branch (HIGH)
bin/neon.py branch-delete --project-id PROJ_ID --branch-id BR_ID \
--confirm "delete branch BR_ID in project PROJ_ID" # delete a branch (HIGH)
bin/neon.py databases --project-id PROJ_ID # list databases
Branch create accepts an optional --parent-branch-id to branch from a non-default branch.
Auth
- Provider id:
neon(credential is collected ascustom.neon) - Collection: API key (Neon console > Account settings > API keys) via the secure credential flow (
credentials.request_api_access) - Auth scheme:
Authorization: Bearer <api key>on every request - Allowed hosts:
console.neon.tech - Status check:
bin/neon.py auth
Operating Rules
- Branch create and branch delete are HIGH actuations. Creating a branch provisions a live database branch with compute that can incur billable usage; deleting one is irreversible and destroys the branch, its compute endpoint, and its data. Both require
--confirmwith the exact string the CLI echoes on every call. Missing or mismatched confirmation refuses the call. - Connection strings are secrets. The branch-create response includes connection URIs that embed database passwords. The CLI masks the password portion (
user:***@host) on display. Never print, log, transmit, or paste a full connection string into chat. If a connection string is needed for app config, deliver it only to the exact destination the user named. - Reads (projects, branches, databases) need no confirmation. Surface choices before any write: name the project, the branch name, and the parent branch, and default cautiously. Never create a branch in a project the user did not choose.
- Never exfiltrate the credential: the CLI only ever handles surrogates (see
bin/neon.py). Do not print, log, or transmit the API key. - Honesty flags (unverified while building this connector): the task brief named
api.neon.tech, but the verified Neon Management API host isconsole.neon.tech; the CLI uses the verified host. The branch DELETE path was not explicitly confirmed in the docs consulted; the CLI surfaces Neon's own error if it differs.
Files
- SKILL.md
- bin/neon.py
Maturity
Draft: written from Neon's public API docs; not yet live-tested end-to-end.
04 同仓库更多 Skills
web-scrape
Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open/fetch fails on JS-heavy pages, or when you need clean markdown/structured extraction from a site. Requires FIRECRAWL_API_KEY.
design-taste-frontend
tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).