neon-access

Executes arbitrary PostgreSQL SQL against the Neon database through an authorized GitHub Actions workflow.

2.3k|421|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/radixark/miles --skill neon-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neon-access
Source: https://github.com/radixark/miles/tree/main/.claude/skills/neon-access
Command: npx skills add https://github.com/radixark/miles --skill neon-access

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Repository writers need to query, inspect, or modify the Miles Neon PostgreSQL database without ever handling the NEON_DATABASE_URL secret, which must remain stored only in GitHub Actions secrets.

Core Features & Use Cases

  • Authorized SQL Execution: Dispatches any PostgreSQL statement (DDL, DML, multi-statement, transactions) through the repository's neon-access.yml workflow after verifying the caller has GitHub write or admin permission.
  • Encrypted Result Delivery: Compresses and hashes the SQL, generates a one-time RSA key pair locally, and receives results encrypted via OpenSSL CMS so public logs contain metadata only.
  • Audit and Integrity Validation: Attaches an audit reason, request ID, and SHA-256 of the SQL, then validates the returned result identity before reporting.
  • Use Case: A maintainer asks to run SELECT now() or apply a schema migration; the skill saves the exact SQL to a file, dispatches the workflow, watches the run, decrypts the result, and returns the JSON output with the workflow URL.

Quick Start

Use $neon-access to run the SQL statement I provide against the Miles Neon database and return the decrypted result.

Frequently Asked Questions about neon-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run SQL against a Neon PostgreSQL database without the connection string?

Save the exact SQL to a .sql file and run the run_neon_workflow.py script with an audit reason. It dispatches the repository's neon-access.yml GitHub Actions workflow, which uses the stored NEON_DATABASE_URL secret, and returns the decrypted JSON result.

What permissions are required to execute SQL through the GitHub workflow?

The caller must have write or admin permission on the radixark/miles repository, verified via the GitHub collaborators API before dispatch. The workflow also checks both the original and triggering actors on the server side.

Can I run multiple statements, DDL, or transactions in one request?

Yes, any PostgreSQL SQL accepted by the server is allowed, including multiple statements, DDL, DML, functions, and explicit transaction control. Execution uses autocommit with no implicit transaction wrapping, so a later error can leave earlier statements committed.

Are psql backslash commands supported by this workflow?

No, psql backslash commands are client-side commands, not PostgreSQL SQL, and are unsupported. Only server-executable PostgreSQL statements can be dispatched.

What are the size limits for SQL requests and query results?

The compressed dispatch payload must fit within GitHub's 65,535 character input limit. Returned rows are capped at 4 MiB by default, configurable via --max-result-bytes, and this cap does not limit or cancel SQL execution.

How are query results kept confidential in workflow logs?

The script generates a one-time RSA key pair locally and uploads the certificate with the request. Results and database errors are encrypted for that key via OpenSSL CMS before artifact upload, so public logs and summaries contain metadata only.