Persist and query tenant-scoped EOS state in Neon serverless Postgres.
npx skills add https://github.com/antonyfmunoz/OS --skill neon-postgres-antonyfmunoz
Please help me install this Agent Skill. Skill: neon_postgres Source: https://github.com/antonyfmunoz/OS/tree/main/skills/tools/neon_postgres Command: npx skills add https://github.com/antonyfmunoz/OS --skill neon-postgres-antonyfmunoz
It solves the challenge of reliably reading and writing tenant-scoped persistent state for AI agents using a serverless PostgreSQL backend without leaking credentials or mixing org data.
app.current_org_id per transaction, so reads/writes remain scoped to the correct org.get_conn() + RealDictCursor workflow that returns rows as dictionaries and manages transactions safely.Use the neon_postgres skill when your agent needs to query or store EOS state in Neon Postgres, and ask it to “write the correct psycopg2 code using get_conn() with tenant RLS for an org_id-scoped SELECT from the skills table.”
High-intent search queries and answers about installing and using this skill.
You can persist tenant-scoped agent state by using a psycopg2 connection that sets `app.current_org_id` per transaction, enforcing row-level security so reads and writes remain strictly scoped to the correct organization.
Row-level security for multi-tenant memory works by setting the `app.current_org_id` configuration parameter locally within each transaction, ensuring all subsequent queries only access rows belonging to that specific organization.
The best way to run parameterized queries is using a standard `get_conn()` pattern with `RealDictCursor` to return rows as dictionaries, executing SQL with `%s` placeholders, and managing transactions safely across pooled or direct Neon endpoints.
Yes, you can use Neon serverless Postgres for upsert operations and agent interaction logging by executing parameterized SQL queries through the standard psycopg2 connection pattern within tenant-isolated transactions.
You need to set `LOCAL app.current_org_id` to activate row-level security policies for that specific transaction, preventing cross-tenant data leakage and ensuring all persistent memory writes are correctly scoped.
Pooled and direct Neon endpoints have transaction handling constraints that require consistent connection management; using the correct `get_conn()` pattern ensures safe transaction handling across both endpoint types for agent workflows.
tonehqProvision Neon databases and configure Infisical secrets for deployment environments.
kwt00Decompose queries into facets and synthesize parallel agent search results.
robotijnImplement Postgres Row-Level Security policies to enforce tenant scoping in multi-tenant SaaS databases.
vecearEnforce tenant isolation with PostgreSQL Row Level Security and automated tests.