[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6F9B82Z7PVGDYA2Q5NM2RTF":3,"skill-same:01M6F9B82Z7PVGDYA2Q5NM2RTF":84},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":30,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":34,"commitSha":64,"skillDirectory":65,"forksCount":66,"repositoryHtmlUrl":67,"repositoryHomepageUrl":6,"ownerHtmlUrl":68,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":69,"install":70,"resources":83},"01M6F9B82Z7PVGDYA2Q5NM2RTF","neon-postgres",null,"Guides and best practices for working with Neon Serverless Postgres. Covers setup, connection methods, branching, autoscaling, scale-to-zero, read replicas, connection pooling, Neon Auth, and the Neon CLI, MCP server, REST API, TypeScript SDK, and Python SDK.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-neon-postgres\u002FSKILL.md",[17,22,25],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":26,"categoryName":27,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"neon postgres","neon","postgres","main","serverless postgres","pooling","autoscaling","neon cli","neon serverless","guides","neon auth","critical","connection pooling","wed","MCP","read","python sdk","api","server","official","auth","mcp server","typescript","cli","2026-11-10 10:12:30",false,"---\nname: neon-postgres\ndescription: \"Guides and best practices for working with Neon Serverless Postgres. Covers setup, connection methods, branching, autoscaling, scale-to-zero, read replicas, connection pooling, Neon Auth, and the Neon CLI, MCP server, REST API, TypeScript SDK, and Python SDK.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fneon-postgres\nsource_repo: neondatabase\u002Fagent-skills\nsource_type: official\ndate_added: 2026-07-01\nlicense: Apache-2.0\nlicense_source: https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Neon Serverless Postgres\n## When to Use\n\nUse this skill when you need guides and best practices for working with Neon Serverless Postgres. Covers setup, connection methods, branching, autoscaling, scale-to-zero, read replicas, connection pooling, Neon Auth, and the Neon CLI, MCP server, REST API, TypeScript SDK, and Python SDK. Use for concrete Neon database or tooling questions.\n\n\nGuide the user through any Neon-related task: setup, connections, branching, and advanced features. Deliver a working Neon connection, a completed feature configuration, or a specific answer from the official Neon docs.\n\nNeon is a serverless Postgres platform that separates compute and storage to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.\n\n## Neon Documentation\n\nThe Neon documentation is the source of truth for all Neon-related information. Always verify claims against the official docs before responding. Neon features and APIs evolve, so prefer fetching current docs over relying on training data.\n\n### Fetching Docs as Markdown\n\nAny Neon doc page can be fetched as markdown in two ways:\n\n1. **Append `.md` to the URL** (simplest): https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching.md\n2. **Request `text\u002Fmarkdown`** on the standard URL: `curl -H \"Accept: text\u002Fmarkdown\" https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching`\n\nBoth return the same markdown content. Use whichever method your tools support.\n\n### Finding the Right Page\n\nThe docs index lists every available page with its URL and a short description:\n\n```\nhttps:\u002F\u002Fneon.com\u002Fdocs\u002Fllms.txt\n```\n\nCommon doc URLs are organized in the topic links below. If you need a page not listed here, search the docs index: https:\u002F\u002Fneon.com\u002Fdocs\u002Fllms.txt. Don't guess URLs.\n\n## What Is Neon\n\nUse this for architecture explanations and terminology (organizations, projects, branches, endpoints) before giving implementation advice.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Farchitecture-overview.md\n\n## Getting Started\n\nUse this section when guiding a user through first-time Neon setup.\n\n### Check Status Quo\n\nBefore starting setup, inspect the user's codebase and environment:\n\n- Existing database connection code\n- Existing Neon MCP server or Neon CLI configuration\n- Existence of a `.env` file and `DATABASE_URL` environment variable\n- Existing ORM (Prisma, Drizzle, TypeORM) configuration\n\n### Self-Driving Setup With Neon's CLI or MCP Server\n\nOffer to inspect existing connected Neon projects or create new ones using the Neon CLI or MCP server. If neither is set up, first explain installation, API-key creation and host configuration changes and obtain authorization for that scope. Review a pinned CLI release and its current help before using the `--agent` flag. Auth is handled automatically. If the user is not logged in, it opens their browser for OAuth and waits for completion before proceeding.\n\n```bash\nnpx -y neon@latest init --agent \u003Cagent-name>\n```\n\nSupported `--agent` values: `cursor`, `copilot`, `claude`, `claude-desktop`, `codex`, `opencode`, `cline`, `gemini-cli`, `goose`, `zed`.\n\nThis installs the Neon extension (for Cursor\u002FVS Code) or MCP server (for other agents), creates an API key, and adds the `neon-postgres` agent skill to the project.\n\nIf `init` is not suitable, the individual steps can be run non-interactively:\n\n- **Extension:** `cursor --install-extension databricks.neon-local-connect`\n- **MCP server:** `npx -y add-mcp https:\u002F\u002Fmcp.neon.tech\u002Fmcp -g -n Neon -y -a \u003Cagent-name>`\n- **Agent skill:** `npx skills add neondatabase\u002Fagent-skills --skill neon-postgres --agent \u003Cagent-name> -y`\n\nFor full CLI installation options, see https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fcli-install.md\n\n### Setup Flow\n\n**1. Select Organization and Project**\n\nUse MCP server or CLI to list organizations and projects. Let the user select an existing project or create a new one.\n\n**2. Get Connection String**\n\nUse MCP server or CLI to get the connection string. Store it in a private, gitignored `.env` as `DATABASE_URL`, preserving existing keys. Inspect key names without printing credential values to chat\u002Flogs. Use a secret manager for deployment.\n\n**3. Pick Connection Method & Driver**\n\nRefer to the connection methods guide to pick the correct driver based on deployment platform: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md\n\n**4. User Authentication with Neon Auth (if needed)**\n\nSkip for CLI tools, scripts, or apps without user accounts. If the app needs auth: use MCP server `provision_neon_auth` tool, then see the auth overview (https:\u002F\u002Fneon.com\u002Fdocs\u002Fauth\u002Foverview.md) for setup. For auth + database queries, see the JavaScript SDK reference (https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fjavascript-sdk.md).\n\n**5. ORM Setup (optional)**\n\nCheck for existing ORM (Prisma, Drizzle, TypeORM). If none, ask if they want one. For Drizzle integration, see https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Fdrizzle.md.\n\n**6. Schema Setup**\n\n- Check for existing migration files or ORM schemas\n- If none: offer to create an example schema or design one together\n\n### Resume Support\n\nIf resuming setup, check what's already configured (MCP connection, `.env` with `DATABASE_URL`, dependencies, schema) and continue from the next incomplete step.\n\n### Security Reminders\n\nRemind users to use environment variables for credentials, never commit connection strings, and use least-privilege database roles.\n\n## Connection Methods & Drivers\n\nUse this when you need to pick the correct transport and driver based on runtime constraints (TCP, HTTP, WebSocket, edge, serverless, long-running).\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md\n\n### Recommended: Drizzle + the right driver for your runtime\n\nOptionally pair Neon with an ORM such as **Drizzle** for easy schema management and migrations. Pick the driver based on how the runtime treats your code:\n\n- **Long-running or shared-runtime environments → node-postgres (`pg`).** Neon Functions, and any host where the function runtime is shared across requests \u002F runs on fluid compute (e.g. **Vercel** with Fluid compute), keep a module-scope process alive across many requests. Open a `pg` pool **once at module scope** and reuse it across requests.\n- **Fully isolated serverless (Lambda-style) → Neon's serverless driver (`@neondatabase\u002Fserverless`).** Do not assume a host destroys every instance per request; check reuse and concurrency for the actual deployment. the serverless driver queries over HTTP and is built for this.\n\n**Neon Functions \u002F Vercel \u002F fluid compute — Drizzle + node-postgres:**\n\n```typescript\nimport { drizzle } from \"drizzle-orm\u002Fnode-postgres\";\nimport { Pool } from \"pg\";\nimport * as schema from \".\u002Fschema\";\n\n\u002F\u002F Created once at module scope; reused by every request the instance handles.\nconst pool = new Pool({ connectionString: process.env.DATABASE_URL, max: 5 });\nconst db = drizzle({ client: pool, schema });\n```\n\nOn **Vercel** (Fluid compute) also attach the pool with `attachDatabasePool` from `@vercel\u002Ffunctions`, so the function runtime drains idle connections before an instance suspends:\n\n```typescript\nimport { drizzle } from \"drizzle-orm\u002Fnode-postgres\";\nimport { Pool } from \"pg\";\nimport { attachDatabasePool } from \"@vercel\u002Ffunctions\";\nimport * as schema from \".\u002Fschema\";\n\nconst pool = new Pool({ connectionString: process.env.DATABASE_URL });\nattachDatabasePool(pool); \u002F\u002F let the Vercel runtime manage the pooled connections\nconst db = drizzle({ client: pool, schema });\n```\n\n**Netlify and other fully-isolated serverless — Drizzle + Neon serverless driver:**\n\n```typescript\nimport { drizzle } from \"drizzle-orm\u002Fneon-http\";\nimport { neon } from \"@neondatabase\u002Fserverless\";\n\nconst sql = neon(process.env.DATABASE_URL!);\nconst db = drizzle({ client: sql });\n```\n\n### Serverless Driver\n\nUse this for `@neondatabase\u002Fserverless` patterns, including HTTP queries, WebSocket transactions, and runtime-specific optimizations.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fserverless\u002Fserverless-driver.md\n\n### Neon JS SDK\n\nUse this for combined Neon Auth + Data API workflows with PostgREST-style querying and typed client setup.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fjavascript-sdk.md\n\n## Developer Tools\n\nUse this for local development enablement with `npx -y neon@latest init --agent \u003Cagent-name>`, VSCode extension setup, and Neon MCP server configuration.\n\n| Tool             | URL                                             |\n| ---------------- | ----------------------------------------------- |\n| CLI Init Command | https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fcli-init.md     |\n| VSCode Extension | https:\u002F\u002Fneon.com\u002Fdocs\u002Flocal\u002Fvscode-extension.md |\n| MCP Server       | https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fneon-mcp-server.md     |\n| Neon CLI         | https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fneon-cli.md     |\n\n### Neon CLI\n\nUse this for terminal-first workflows, scripts, and CI\u002FCD automation with `neon`.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fneon-cli.md\n\n## Neon Admin API\n\nThe Neon Admin API can be used to manage Neon resources programmatically. It is used behind the scenes by the Neon CLI and MCP server, but can also be used directly for more complex automation workflows or when embedding Neon in other applications.\n\n### Neon REST API\n\nUse this for direct HTTP automation, endpoint-level control, API key auth, rate-limit handling, and operation polling.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fapi-reference.md\n\n### Neon TypeScript SDK\n\nUse this when implementing typed programmatic control of Neon resources in TypeScript via `@neondatabase\u002Fapi-client`.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Ftypescript-sdk.md\n\n### Neon Python SDK\n\nUse this when implementing programmatic Neon management in Python with the `neon-api` package.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fpython-sdk.md\n\n## Neon Auth\n\nUse this for managed user authentication setup, UI components, auth methods, and Neon Auth integration pitfalls in Next.js and React apps.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fauth\u002Foverview.md\n\nNeon Auth is also embedded in the Neon JS SDK. Depending on your use case, you may want to use the Neon JS SDK instead of Neon Auth alone. See https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md for more details.\n\n## Neon Infrastructure as Code (`neon.ts`)\n\n`neon.ts` is Neon's branch config and infrastructure-as-code file: declare which services your branches have, get type-safe env vars, and program per-branch compute — all in TypeScript (see the `neon` skill for the full reference). Postgres always exists on every branch, so you never declare the database itself; what you codify here is the Postgres-adjacent surface — Neon Auth, the Data API, and per-branch compute settings (autoscaling and scale-to-zero).\n\nAdd it with `@neon\u002Fconfig`:\n\n```bash\nnpm i @neon\u002Fconfig\n```\n\n```typescript\n\u002F\u002F neon.ts\nimport { defineConfig } from \"@neon\u002Fconfig\u002Fv1\";\n\nexport default defineConfig({\n  auth: true, \u002F\u002F Neon Auth (adds NEON_AUTH_* env vars)\n  dataApi: true, \u002F\u002F Data API (adds NEON_DATA_API_URL); requires auth: true (or an external IdP)\n  \u002F\u002F Postgres exists on every branch; tune its compute per branch:\n  branch: (branch) => {\n    if (branch.exists) return {}; \u002F\u002F leave existing branches untouched\n    if (branch.isDefault) return { protected: true }; \u002F\u002F prod keeps default compute\n    return {\n      ttl: \"7d\", \u002F\u002F non-prod branches auto-expire (max 30d)\n      postgres: {\n        computeSettings: {\n          autoscalingLimitMinCu: 0.25, \u002F\u002F active compute floor; suspension is configured separately\n          autoscalingLimitMaxCu: 1, \u002F\u002F keep dev\u002Fpreview cheap\n          suspendTimeout: \"5m\",\n        },\n      },\n    };\n  },\n});\n```\n\nReconcile the declaration from the CLI — the Neon equivalent of `terraform plan` \u002F `apply`:\n\n```bash\nneon config status   # print the branch's live config\nneon config plan     # dry-run diff of what apply would change\nneon config apply    # provision the declared services \u002F settings\nneon deploy          # alias for `neon config apply`\n```\n\nBecause `neon checkout` applies the policy as it **creates** a branch, a fresh branch comes up with these compute settings (and Auth \u002F Data API) already in place. Checking out an _existing_ branch never reconciles it — run `neon deploy` to apply changes.\n\nSince `neon.ts` is TypeScript, invalid combinations fail to compile with an actionable message: the Data API verifies requests with Neon Auth by default, so `dataApi: true` without `auth: true` is a type error (the fix — `auth: true`, or `authProvider: 'external'` with a `jwksUrl` — is in the message). See the `neon` skill's type-safe config note.\n\nRead the resulting env back, typed and validated against the policy, with `parseEnv` from `@neon\u002Fenv`:\n\n```typescript\nimport { parseEnv } from \"@neon\u002Fenv\";\nimport config from \".\u002Fneon\";\n\nconst env = parseEnv(config);\nenv.postgres.databaseUrl; \u002F\u002F typed; enabling auth \u002F dataApi above surfaces env.auth \u002F env.dataApi\n```\n\n## Branching\n\nUse this when the user is planning isolated environments, schema migration testing, preview deployments, or branch lifecycle automation.\n\nKey points:\n\n- Branches are instant, copy-on-write clones (no full data copy).\n- Branches may have attached compute endpoints; inspect the actual branch and endpoint state rather than assuming each branch already has one.\n- Use the neon CLI or MCP server to create, inspect, and compare branches.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching.md\n\nFor detailed branch creation workflows (normal vs schema-only branches, reset-from-parent, CLI\u002FMCP selection), use the `neon-postgres-branches` skill if available\n\nOr fetch the full branching skill from the following URL:\n\nhttps:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon-postgres-branches\u002FSKILL.md\n\nIf this skill is not installed you can use the following command to install it:\n\n```bash\nnpx skills add neondatabase\u002Fagent-skills --skill neon-postgres-branches\n```\n\n## Autoscaling\n\nUse this when the user needs compute to scale automatically with workload and wants guidance on CU sizing and runtime behavior.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fautoscaling.md\n\n## Scale to Zero\n\nUse this when optimizing idle costs and discussing suspend\u002Fresume behavior, including cold-start trade-offs.\n\nKey points:\n\n- Idle computes suspend automatically (default 5 minutes, configurable) (unless disabled - launch & scale plan only)\n- First query after suspend typically has a cold-start penalty (around hundreds of ms)\n- Storage remains active while compute is suspended.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fscale-to-zero.md\n\n## Instant Restore\n\nUse this when the user needs point-in-time recovery or wants to restore data state without traditional backup restore workflows.\n\nKey points:\n\n- History windows for instant restore depend on plan limits.\n- Users can create branches from historical points-in-time.\n- Time Travel queries can be used for historical inspection workflows.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranch-restore.md\n\n## Read Replicas\n\nUse this for read-heavy workloads where the user needs dedicated read-only compute without duplicating storage.\n\nKey points:\n\n- Replicas are read-only compute endpoints sharing the same storage.\n- Creation is fast and scaling is independent from primary compute.\n- Typical use cases: analytics, reporting, and read-heavy APIs.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fread-replicas.md\n\n## Connection Pooling\n\nUse this when the user is in serverless or high-concurrency environments and needs safe, scalable Postgres connection management.\n\nKey points:\n\n- Neon pooling uses PgBouncer.\n- Add `-pooler` to endpoint hostnames to use pooled connections.\n- Pooling is especially important in serverless runtimes with bursty concurrency.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fconnection-pooling.md\n\n## IP Allow Lists\n\nUse this when the user needs to restrict database access by trusted networks, IPs, or CIDR ranges.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fip-allow.md\n\n## Logical Replication\n\nUse this when integrating CDC pipelines, external Postgres sync, or replication-based data movement.\n\nKey points:\n\n- Neon supports native logical replication workflows.\n- Useful for replicating to\u002Ffrom external Postgres systems.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Flogical-replication-guide.md\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream product or API scope.\n- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.\n- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n\nCommands that install integrations, create branches or reconcile configuration mutate local\u002Fremote state and may incur cost. Read-only status\u002Fplan precedes an authorized apply; branch clones may contain production personal data, so prefer schema-only or sanitized fixtures for previews. This bundle contains no CLI implementation or companion `neon` skill. Product APIs, host behavior and examples must be checked against the linked current docs before use; documentation retrieval may fail and must not be reported as verification.\n","# Neon Serverless Postgres\n## When to Use\n\nUse this skill when you need guides and best practices for working with Neon Serverless Postgres. Covers setup, connection methods, branching, autoscaling, scale-to-zero, read replicas, connection pooling, Neon Auth, and the Neon CLI, MCP server, REST API, TypeScript SDK, and Python SDK. Use for concrete Neon database or tooling questions.\n\n\nGuide the user through any Neon-related task: setup, connections, branching, and advanced features. Deliver a working Neon connection, a completed feature configuration, or a specific answer from the official Neon docs.\n\nNeon is a serverless Postgres platform that separates compute and storage to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.\n\n## Neon Documentation\n\nThe Neon documentation is the source of truth for all Neon-related information. Always verify claims against the official docs before responding. Neon features and APIs evolve, so prefer fetching current docs over relying on training data.\n\n### Fetching Docs as Markdown\n\nAny Neon doc page can be fetched as markdown in two ways:\n\n1. **Append `.md` to the URL** (simplest): https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching.md\n2. **Request `text\u002Fmarkdown`** on the standard URL: `curl -H \"Accept: text\u002Fmarkdown\" https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching`\n\nBoth return the same markdown content. Use whichever method your tools support.\n\n### Finding the Right Page\n\nThe docs index lists every available page with its URL and a short description:\n\n```\nhttps:\u002F\u002Fneon.com\u002Fdocs\u002Fllms.txt\n```\n\nCommon doc URLs are organized in the topic links below. If you need a page not listed here, search the docs index: https:\u002F\u002Fneon.com\u002Fdocs\u002Fllms.txt. Don't guess URLs.\n\n## What Is Neon\n\nUse this for architecture explanations and terminology (organizations, projects, branches, endpoints) before giving implementation advice.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Farchitecture-overview.md\n\n## Getting Started\n\nUse this section when guiding a user through first-time Neon setup.\n\n### Check Status Quo\n\nBefore starting setup, inspect the user's codebase and environment:\n\n- Existing database connection code\n- Existing Neon MCP server or Neon CLI configuration\n- Existence of a `.env` file and `DATABASE_URL` environment variable\n- Existing ORM (Prisma, Drizzle, TypeORM) configuration\n\n### Self-Driving Setup With Neon's CLI or MCP Server\n\nOffer to inspect existing connected Neon projects or create new ones using the Neon CLI or MCP server. If neither is set up, first explain installation, API-key creation and host configuration changes and obtain authorization for that scope. Review a pinned CLI release and its current help before using the `--agent` flag. Auth is handled automatically. If the user is not logged in, it opens their browser for OAuth and waits for completion before proceeding.\n\n```bash\nnpx -y neon@latest init --agent \u003Cagent-name>\n```\n\nSupported `--agent` values: `cursor`, `copilot`, `claude`, `claude-desktop`, `codex`, `opencode`, `cline`, `gemini-cli`, `goose`, `zed`.\n\nThis installs the Neon extension (for Cursor\u002FVS Code) or MCP server (for other agents), creates an API key, and adds the `neon-postgres` agent skill to the project.\n\nIf `init` is not suitable, the individual steps can be run non-interactively:\n\n- **Extension:** `cursor --install-extension databricks.neon-local-connect`\n- **MCP server:** `npx -y add-mcp https:\u002F\u002Fmcp.neon.tech\u002Fmcp -g -n Neon -y -a \u003Cagent-name>`\n- **Agent skill:** `npx skills add neondatabase\u002Fagent-skills --skill neon-postgres --agent \u003Cagent-name> -y`\n\nFor full CLI installation options, see https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fcli-install.md\n\n### Setup Flow\n\n**1. Select Organization and Project**\n\nUse MCP server or CLI to list organizations and projects. Let the user select an existing project or create a new one.\n\n**2. Get Connection String**\n\nUse MCP server or CLI to get the connection string. Store it in a private, gitignored `.env` as `DATABASE_URL`, preserving existing keys. Inspect key names without printing credential values to chat\u002Flogs. Use a secret manager for deployment.\n\n**3. Pick Connection Method & Driver**\n\nRefer to the connection methods guide to pick the correct driver based on deployment platform: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md\n\n**4. User Authentication with Neon Auth (if needed)**\n\nSkip for CLI tools, scripts, or apps without user accounts. If the app needs auth: use MCP server `provision_neon_auth` tool, then see the auth overview (https:\u002F\u002Fneon.com\u002Fdocs\u002Fauth\u002Foverview.md) for setup. For auth + database queries, see the JavaScript SDK reference (https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fjavascript-sdk.md).\n\n**5. ORM Setup (optional)**\n\nCheck for existing ORM (Prisma, Drizzle, TypeORM). If none, ask if they want one. For Drizzle integration, see https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Fdrizzle.md.\n\n**6. Schema Setup**\n\n- Check for existing migration files or ORM schemas\n- If none: offer to create an example schema or design one together\n\n### Resume Support\n\nIf resuming setup, check what's already configured (MCP connection, `.env` with `DATABASE_URL`, dependencies, schema) and continue from the next incomplete step.\n\n### Security Reminders\n\nRemind users to use environment variables for credentials, never commit connection strings, and use least-privilege database roles.\n\n## Connection Methods & Drivers\n\nUse this when you need to pick the correct transport and driver based on runtime constraints (TCP, HTTP, WebSocket, edge, serverless, long-running).\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md\n\n### Recommended: Drizzle + the right driver for your runtime\n\nOptionally pair Neon with an ORM such as **Drizzle** for easy schema management and migrations. Pick the driver based on how the runtime treats your code:\n\n- **Long-running or shared-runtime environments → node-postgres (`pg`).** Neon Functions, and any host where the function runtime is shared across requests \u002F runs on fluid compute (e.g. **Vercel** with Fluid compute), keep a module-scope process alive across many requests. Open a `pg` pool **once at module scope** and reuse it across requests.\n- **Fully isolated serverless (Lambda-style) → Neon's serverless driver (`@neondatabase\u002Fserverless`).** Do not assume a host destroys every instance per request; check reuse and concurrency for the actual deployment. the serverless driver queries over HTTP and is built for this.\n\n**Neon Functions \u002F Vercel \u002F fluid compute — Drizzle + node-postgres:**\n\n```typescript\nimport { drizzle } from \"drizzle-orm\u002Fnode-postgres\";\nimport { Pool } from \"pg\";\nimport * as schema from \".\u002Fschema\";\n\n\u002F\u002F Created once at module scope; reused by every request the instance handles.\nconst pool = new Pool({ connectionString: process.env.DATABASE_URL, max: 5 });\nconst db = drizzle({ client: pool, schema });\n```\n\nOn **Vercel** (Fluid compute) also attach the pool with `attachDatabasePool` from `@vercel\u002Ffunctions`, so the function runtime drains idle connections before an instance suspends:\n\n```typescript\nimport { drizzle } from \"drizzle-orm\u002Fnode-postgres\";\nimport { Pool } from \"pg\";\nimport { attachDatabasePool } from \"@vercel\u002Ffunctions\";\nimport * as schema from \".\u002Fschema\";\n\nconst pool = new Pool({ connectionString: process.env.DATABASE_URL });\nattachDatabasePool(pool); \u002F\u002F let the Vercel runtime manage the pooled connections\nconst db = drizzle({ client: pool, schema });\n```\n\n**Netlify and other fully-isolated serverless — Drizzle + Neon serverless driver:**\n\n```typescript\nimport { drizzle } from \"drizzle-orm\u002Fneon-http\";\nimport { neon } from \"@neondatabase\u002Fserverless\";\n\nconst sql = neon(process.env.DATABASE_URL!);\nconst db = drizzle({ client: sql });\n```\n\n### Serverless Driver\n\nUse this for `@neondatabase\u002Fserverless` patterns, including HTTP queries, WebSocket transactions, and runtime-specific optimizations.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fserverless\u002Fserverless-driver.md\n\n### Neon JS SDK\n\nUse this for combined Neon Auth + Data API workflows with PostgREST-style querying and typed client setup.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fjavascript-sdk.md\n\n## Developer Tools\n\nUse this for local development enablement with `npx -y neon@latest init --agent \u003Cagent-name>`, VSCode extension setup, and Neon MCP server configuration.\n\n| Tool             | URL                                             |\n| ---------------- | ----------------------------------------------- |\n| CLI Init Command | https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fcli-init.md     |\n| VSCode Extension | https:\u002F\u002Fneon.com\u002Fdocs\u002Flocal\u002Fvscode-extension.md |\n| MCP Server       | https:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fneon-mcp-server.md     |\n| Neon CLI         | https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fneon-cli.md     |\n\n### Neon CLI\n\nUse this for terminal-first workflows, scripts, and CI\u002FCD automation with `neon`.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fneon-cli.md\n\n## Neon Admin API\n\nThe Neon Admin API can be used to manage Neon resources programmatically. It is used behind the scenes by the Neon CLI and MCP server, but can also be used directly for more complex automation workflows or when embedding Neon in other applications.\n\n### Neon REST API\n\nUse this for direct HTTP automation, endpoint-level control, API key auth, rate-limit handling, and operation polling.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fapi-reference.md\n\n### Neon TypeScript SDK\n\nUse this when implementing typed programmatic control of Neon resources in TypeScript via `@neondatabase\u002Fapi-client`.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Ftypescript-sdk.md\n\n### Neon Python SDK\n\nUse this when implementing programmatic Neon management in Python with the `neon-api` package.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Freference\u002Fpython-sdk.md\n\n## Neon Auth\n\nUse this for managed user authentication setup, UI components, auth methods, and Neon Auth integration pitfalls in Next.js and React apps.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fauth\u002Foverview.md\n\nNeon Auth is also embedded in the Neon JS SDK. Depending on your use case, you may want to use the Neon JS SDK instead of Neon Auth alone. See https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fchoose-connection.md for more details.\n\n## Neon Infrastructure as Code (`neon.ts`)\n\n`neon.ts` is Neon's branch config and infrastructure-as-code file: declare which services your branches have, get type-safe env vars, and program per-branch compute — all in TypeScript (see the `neon` skill for the full reference). Postgres always exists on every branch, so you never declare the database itself; what you codify here is the Postgres-adjacent surface — Neon Auth, the Data API, and per-branch compute settings (autoscaling and scale-to-zero).\n\nAdd it with `@neon\u002Fconfig`:\n\n```bash\nnpm i @neon\u002Fconfig\n```\n\n```typescript\n\u002F\u002F neon.ts\nimport { defineConfig } from \"@neon\u002Fconfig\u002Fv1\";\n\nexport default defineConfig({\n  auth: true, \u002F\u002F Neon Auth (adds NEON_AUTH_* env vars)\n  dataApi: true, \u002F\u002F Data API (adds NEON_DATA_API_URL); requires auth: true (or an external IdP)\n  \u002F\u002F Postgres exists on every branch; tune its compute per branch:\n  branch: (branch) => {\n    if (branch.exists) return {}; \u002F\u002F leave existing branches untouched\n    if (branch.isDefault) return { protected: true }; \u002F\u002F prod keeps default compute\n    return {\n      ttl: \"7d\", \u002F\u002F non-prod branches auto-expire (max 30d)\n      postgres: {\n        computeSettings: {\n          autoscalingLimitMinCu: 0.25, \u002F\u002F active compute floor; suspension is configured separately\n          autoscalingLimitMaxCu: 1, \u002F\u002F keep dev\u002Fpreview cheap\n          suspendTimeout: \"5m\",\n        },\n      },\n    };\n  },\n});\n```\n\nReconcile the declaration from the CLI — the Neon equivalent of `terraform plan` \u002F `apply`:\n\n```bash\nneon config status   # print the branch's live config\nneon config plan     # dry-run diff of what apply would change\nneon config apply    # provision the declared services \u002F settings\nneon deploy          # alias for `neon config apply`\n```\n\nBecause `neon checkout` applies the policy as it **creates** a branch, a fresh branch comes up with these compute settings (and Auth \u002F Data API) already in place. Checking out an _existing_ branch never reconciles it — run `neon deploy` to apply changes.\n\nSince `neon.ts` is TypeScript, invalid combinations fail to compile with an actionable message: the Data API verifies requests with Neon Auth by default, so `dataApi: true` without `auth: true` is a type error (the fix — `auth: true`, or `authProvider: 'external'` with a `jwksUrl` — is in the message). See the `neon` skill's type-safe config note.\n\nRead the resulting env back, typed and validated against the policy, with `parseEnv` from `@neon\u002Fenv`:\n\n```typescript\nimport { parseEnv } from \"@neon\u002Fenv\";\nimport config from \".\u002Fneon\";\n\nconst env = parseEnv(config);\nenv.postgres.databaseUrl; \u002F\u002F typed; enabling auth \u002F dataApi above surfaces env.auth \u002F env.dataApi\n```\n\n## Branching\n\nUse this when the user is planning isolated environments, schema migration testing, preview deployments, or branch lifecycle automation.\n\nKey points:\n\n- Branches are instant, copy-on-write clones (no full data copy).\n- Branches may have attached compute endpoints; inspect the actual branch and endpoint state rather than assuming each branch already has one.\n- Use the neon CLI or MCP server to create, inspect, and compare branches.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranching.md\n\nFor detailed branch creation workflows (normal vs schema-only branches, reset-from-parent, CLI\u002FMCP selection), use the `neon-postgres-branches` skill if available\n\nOr fetch the full branching skill from the following URL:\n\nhttps:\u002F\u002Fneon.com\u002Fdocs\u002Fai\u002Fskills\u002Fneon-postgres-branches\u002FSKILL.md\n\nIf this skill is not installed you can use the following command to install it:\n\n```bash\nnpx skills add neondatabase\u002Fagent-skills --skill neon-postgres-branches\n```\n\n## Autoscaling\n\nUse this when the user needs compute to scale automatically with workload and wants guidance on CU sizing and runtime behavior.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fautoscaling.md\n\n## Scale to Zero\n\nUse this when optimizing idle costs and discussing suspend\u002Fresume behavior, including cold-start trade-offs.\n\nKey points:\n\n- Idle computes suspend automatically (default 5 minutes, configurable) (unless disabled - launch & scale plan only)\n- First query after suspend typically has a cold-start penalty (around hundreds of ms)\n- Storage remains active while compute is suspended.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fscale-to-zero.md\n\n## Instant Restore\n\nUse this when the user needs point-in-time recovery or wants to restore data state without traditional backup restore workflows.\n\nKey points:\n\n- History windows for instant restore depend on plan limits.\n- Users can create branches from historical points-in-time.\n- Time Travel queries can be used for historical inspection workflows.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fbranch-restore.md\n\n## Read Replicas\n\nUse this for read-heavy workloads where the user needs dedicated read-only compute without duplicating storage.\n\nKey points:\n\n- Replicas are read-only compute endpoints sharing the same storage.\n- Creation is fast and scaling is independent from primary compute.\n- Typical use cases: analytics, reporting, and read-heavy APIs.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fread-replicas.md\n\n## Connection Pooling\n\nUse this when the user is in serverless or high-concurrency environments and needs safe, scalable Postgres connection management.\n\nKey points:\n\n- Neon pooling uses PgBouncer.\n- Add `-pooler` to endpoint hostnames to use pooled connections.\n- Pooling is especially important in serverless runtimes with bursty concurrency.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fconnect\u002Fconnection-pooling.md\n\n## IP Allow Lists\n\nUse this when the user needs to restrict database access by trusted networks, IPs, or CIDR ranges.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fintroduction\u002Fip-allow.md\n\n## Logical Replication\n\nUse this when integrating CDC pipelines, external Postgres sync, or replication-based data movement.\n\nKey points:\n\n- Neon supports native logical replication workflows.\n- Useful for replicating to\u002Ffrom external Postgres systems.\n\nLink: https:\u002F\u002Fneon.com\u002Fdocs\u002Fguides\u002Flogical-replication-guide.md\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream product or API scope.\n- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.\n- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n\nCommands that install integrations, create branches or reconcile configuration mutate local\u002Fremote state and may incur cost. Read-only status\u002Fplan precedes an authorized apply; branch clones may contain production personal data, so prefer schema-only or sanitized fixtures for previews. This bundle contains no CLI implementation or companion `neon` skill. Product APIs, host behavior and examples must be checked against the linked current docs before use; documentation retrieval may fail and must not be reported as verification.\n",{"name":5,"risk":42,"source":60,"license":14,"date_added":61,"description":7,"source_repo":62,"source_type":50,"license_source":63},"https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fneon-postgres",1782864000000,"neondatabase\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fneondatabase\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fantigravity-neon-postgres",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-11 14:20:43",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add boisenoise\u002Fskills-collections --skill neon-postgres",{"tool":76,"command":77},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill neon-postgres",{"tool":79,"command":80},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill neon-postgres","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-neon-postgres\u002FSKILL.md",true,[],[85,111,133,157,176,199],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":55},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[93,94,95,50,96,97,98,99,100,46,101,102,103,104,105,42,106,107,108,109,110],"web","access","web access","development","browser","search","data","Tools","fetch","only","youtube","free tools","platform","free","cover","normal","when","2026",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":55},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[118],{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},[113,45,54,120,50,96,121,100,122,123,124,125,126,127,128,42,129,130,131,132,110],"github","license","Budget","credentials","team","catalog","use","call","discover","external tools","with","scoped","blob",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":143,"publishedAt":55},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[140],{"categoryNo":141,"categoryName":142,"taxonomyType":28,"taxonomyTypeDesc":29},"01JBSEEDCAT000000000000038","人力资源",[135,120,50,121,144,145,146,147,148,149,42,150,151,152,130,153,154,155,156,132,113,110],"https","email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":161,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":55},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[165,166,167,120,50,121,168,169,144,170,122,171,172,173,148,42,174,175,132,113,110],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":55},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[184,185,120,186,50,187,121,188,189,190,191,192,42,193,194,195,196,197,198,132],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":55},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[207,208,209,120,50,121,210,211,147,212,213,42,214,215,216,217,218,219,220,132],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]