@netlify/agent-runner-cli 1.150.0 → 1.151.0

package/dist/skills/netlify-database/SKILL.ask.md

@@ -0,0 +1,54 @@
+---
+name: netlify-database
+description: Read the project's Netlify Database (managed Postgres) to answer questions about its schema or its data. Read-only - this run cannot create, migrate, or modify a database. Use when a question is about what data the project stores, what the schema looks like, or what is currently in a table.
+---
+
+# Netlify Database (read-only)
+
+Netlify Database is a fully managed Postgres database built into the Netlify platform. This run is read-only: you can
+inspect the schema and read data to answer the question, and nothing else.
+
+If the run has database access, the branch you are connected to is named in the "Netlify Database (read-only)" section
+of your context. If that section is absent, this project has no database available to this run - say so rather than
+guessing at a schema.
+
+## Querying
+
+Use `netlify db connect` with `--query` for one-shot execution. Never run it without `--query`: that opens an
+interactive session which never returns and will hang the run.
+
+```bash
+# List tables
+netlify db connect --query "SELECT table_name FROM information_schema.tables WHERE table_schema = 'public'"
+
+# Describe a table
+netlify db connect --query "SELECT column_name, data_type, is_nullable FROM information_schema.columns WHERE table_name = 'users'"
+
+# Count rows
+netlify db connect --query "SELECT count(*) FROM users"
+
+# Read a few rows as JSON
+netlify db connect --query "SELECT id, created_at FROM users ORDER BY created_at DESC LIMIT 5" --json
+```
+
+Prefer `information_schema` queries and aggregates. When you do read rows, use a `LIMIT` and select only the columns
+you need - leave out columns holding personal data, credentials, or tokens. Query output is shown to the user and
+stored with the session.
+
+## What this run cannot do
+
+- No writes. The connection uses a read-only role, so `INSERT`, `UPDATE`, `DELETE`, and DDL are refused by Postgres.
+- No migrations. Do not run `drizzle-kit`, `netlify db migrations reset`, or `netlify db migrate`, and do not write
+  migration files. If answering the question means describing a schema change, describe it - the change itself belongs
+  to a later run that is allowed to edit the project.
+- No provisioning. If the project has no database, this run cannot create one.
+
+## Reading schema from the codebase
+
+The schema definition in the repository is often the better answer for "what does the schema look like" questions, and
+it is cheaper to read than the database. Look for `db/schema.ts` (Drizzle) or SQL files in
+`netlify/database/migrations/`. Query the database when the question is about the data itself, or when you need to
+confirm what is actually applied to the branch rather than what the code intends.
+
+Migration files on disk are not necessarily applied to the branch you are reading, so treat the repository as intent
+and the database as the current state.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@netlify/agent-runner-cli",
   "type": "module",
-  "version": "1.150.0",
+  "version": "1.151.0",
   "description": "CLI tool for running Netlify agents",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",