Neon

What it does

When your agent uses it

• Neon is mentioned for an overview of how to work with Neon and how to get started
• Tasks that involve File uploads and storage
• Tasks that involve Serverless

Example prompts

• “object storage”
• “S3-compatible storage”
• “serverless functions”
• “/neon”

Requirements

• Node.js

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

1. 1Append .md to the URL (simplest): https://neon.com/docs/introduction/branching.md
2. 2Request text/markdown on the standard URL: curl -H "Accept: text/markdown" https://neon.com/docs/introduction/branching

What it can do on your machine

Read from SKILL.md and the folder at commit 3852296. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npx
  • npm
  • curl
  • cursor
  • terraform

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • neon.com
  • mcp.neon.tech

  Also links to:

  • varlock.dev

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Neon loads about 3.9k tokens when it runs. Until then it costs about 145 tokens; SKILL.md has 1,943 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~145

When it runs · the whole SKILL.md, loaded when a task matches

~3.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:95

  - Existence of a `.env` file and `DATABASE_URL` environment variable

• NoteMentions a .env fileSKILL.md:125

  t's already configured (MCP connection, `.env` with `DATABASE_URL`, dependencies, schema) and continue from the next inc

• NoteMentions a .env fileSKILL.md:137

  (`DATABASE_URL`, …) into your existing `.env`, or `.env.local` if you don't have one (override the target with `--file`

• NoteMentions a .env fileSKILL.md:146

  ch's `DATABASE_URL` lands in your local `.env` automatically — build against it, then `checkout` the next branch and rep

• NoteMentions a .env fileSKILL.md:161

  into the child process at runtime — no `.env` file needed. This is the runtime counterpart to the on-disk `env pull`.

• NoteMentions a .env fileSKILL.md:162

  ://varlock.dev) can bulk-load it from a `.env.schema` with `@setValuesBulk(exec("neon-env export --format json"), format

• NoteMentions a .env fileSKILL.md:166

  When an agent should not write a local `.env`, instruct it (for example in your `AGENTS.md`) to run `neonctl checkout <b

• NoteMentions a .env fileSKILL.md:201

  you already have (typically pulled into `.env` by `checkout` / `env pull`); for fetching env at runtime without a file,

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 1,943 words (~3,933 tokens).

name

neon

Read the full SKILL.md on GitHub

Files

Just SKILL.md in external_plugins/neon/skills/neon of xai-org/plugin-marketplace.

Open the folder on GitHubat commit 3852296