skilld
All skills
neondatabase avatar

/neon

@b4016a3 official
by neondatabaseneondatabase/agent-skills96 stars
20

Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, and the AI Gateway. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASE_URL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.

Ask your Agent

Use this Skill: https://skilld.dev/gh/neondatabase/agent-skills/neon

This session only. Nothing lands on disk.

referencesfunction-triggers.md

≈813 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Function Triggers (CLI, MCP, REST)

A Function Trigger is a branch-scoped rule that POSTs to a Neon Function on a cron (type: "schedule") or when an object is created in a bucket (type: "storage_object_created"). Same regions as Functions (aws-us-east-2, aws-us-east-1, aws-eu-central-1, and aws-ap-southeast-1).

Prefer neon.ts. Declare a triggers map. The record key is the trigger name. neon deploy applies triggers after the functions they target. Names must be unique among every trigger visible on the branch. Triggers that exist remotely but are omitted from neon.ts are left alone; delete with neon triggers delete.

import { defineConfig } from "@neon/config/v1";

export default defineConfig({
  functions: {
    ingest: { name: "Object ingest", source: "src/index.ts" },
    cron: { name: "Cron", source: "src/cron.ts" },
  },
  buckets: { assets: { access: "public_read" } },
  triggers: {
    "on-upload": {
      type: "storage_object_created",
      function: "ingest",
      bucket: "assets",
      prefix: "logos/",
      functionPath: "/object",
    },
    "every-minute": {
      type: "schedule",
      function: "cron",
      cron: "* * * * *",
      functionPath: "/cron",
    },
  },
});

Needs Neon CLI 4.21 or newer (@neon/config 1.7.0).

CLI when you are not applying neon.ts, or to list, enable, disable, or delete. create takes --cron or --bucket, not both:

neon triggers create --function-slug cron --name hourly --cron '0 * * * *' --function-path /cron
neon triggers create --function-slug ingest --name on-upload --bucket assets --prefix 'logos/' --function-path /object
neon triggers list
neon triggers update <id> --branch <branch> --cron '*/30 * * * *'
neon triggers update <id> --branch <branch> --bucket assets --prefix 'incoming/'
neon triggers enable <id> --branch <branch>
neon triggers disable <id> --branch <branch>
neon triggers delete <id> --branch <branch>

Inspect a trigger with neon triggers list --output json. Pass --branch on get/update/enable/disable/delete: without it the CLI resolves the trigger id as a branch name. Inherited triggers (created on a parent branch) show Inherited true on the child and start disabled. neon deploy of a neon.ts that declares the same trigger enables that copy; omit it to leave the inherited trigger disabled.

MCP backup (Neon MCP server, ?category=functions): list_triggers, get_trigger, create_trigger, update_trigger, delete_trigger. create_trigger takes project_id, branch_id (a br-… id, not a name), and body with "type": "schedule", function_slug, name, and schedule: { cron }. REST if neither CLI nor MCP is available: POST /projects/{project_id}/branches/{branch_id}/triggers. Schedule body matches MCP. Storage body uses "type": "storage_object_created" and storage_object_created: { bucket_name, prefix }. CLI reference: https://neon.com/docs/cli/triggers.md.

Authenticate a trigger delivery with parseTriggerDelivery from @neon/functions (≥ 0.11.0). parseTrigger / parseTriggerInvocation stay schedule-only. Full type table, payload, and Hono example: the neon-functions skill, references/function-triggers.md.

Source: SKILL.md on GitHub

Third-party checks

No alerts13d3 checks · Risk SAFE
  • Gen Agent Trust Hub13d

    This skill provides a comprehensive toolkit for managing Neon cloud database services, including database provisioning, branching, serverless functions, and AI Gateway integration. It relies on the official Neon CLI and SDK for all operations, ensuring that all downloads and network activities are directed to trusted vendor-controlled domains.

  • Socket13d

    No alerts

  • Snyk13d

    Risk: LOW · No issues

Provenance

Signed by skilld at b4016a3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 weeks ago

Capability

Other metadata
metadata
{
  "source": "https://github.com/neondatabase/agent-skills/tree/main/skills/neon"
}

Topics

  • Auth
  • Backend
  • neon
  • postgres
  • serverless
  • object-storage
  • functions
  • ai-gateway
  • branching

README badge

README badge for neondatabase/agent-skills/neon

What it does

Neon is a backend platform bundling Postgres, Auth, Object Storage, Compute Functions, and an AI Gateway that branch together with your project. Use this skill as the entry point for Neon setup, architecture decisions, and routing to specialized skills for Postgres, Functions, Storage, or the AI Gateway. Early access features (Object Storage, Functions, AI Gateway) require a new project in us-east-2 and private beta enrollment.

Generated from the current SKILL.md.

Frequently asked

What is Neon and how does it fit into my app architecture?
Neon is a backend platform providing Serverless Postgres, Auth, Object Storage, Compute Functions, and an AI Gateway — all branching together with your project. It is not a full-stack host; you deploy your app to Vercel or Netlify and use Neon services as your backend.
Which Neon services are generally available versus preview?
Postgres and Auth are generally available. Object Storage, Compute Functions, and AI Gateway are in preview and only available on new projects created in the us-east-2 region.
How do I access preview features like Object Storage or Compute Functions?
Preview features require a new project in us-east-2. If you don't have early access, sign up at https://neon.com/blog/were-building-backends#access.
What is the branch-first dev flow and how do I use it?
Run `neonctl link` once per project to connect your workspace, then `neonctl checkout <branch-name>` per feature to create or switch branches with isolated databases. Both commands automatically pull the branch's environment variables into your `.env`.
How do I install or switch between individual Neon skills?
Use `npx skills add neondatabase/agent-skills -s <skill-name>` to install a specific skill like neon-postgres, neon-functions, or neon-ai-gateway. Check the skill index in the SKILL.md to find the right skill for your task.

Generated from the current SKILL.md. These answers refresh after source changes.