<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sql on Vibe Coding</title><link>https://vibecoding.rest/tags/sql/</link><description>Recent content in Sql on Vibe Coding</description><generator>Hugo</generator><language>en</language><atom:link href="https://vibecoding.rest/tags/sql/index.xml" rel="self" type="application/rss+xml"/><item><title>Postgres</title><link>https://vibecoding.rest/mcp-servers/postgres/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/mcp-servers/postgres/</guid><description>&lt;p&gt;The Postgres server gives an agent introspection into a database&amp;rsquo;s schema — tables, columns, relationships — and the ability to run read-only queries against it.&lt;/p&gt;&#10;&lt;h2 id="why-it-matters"&gt;Why it matters&lt;/h2&gt;&#10;&lt;p&gt;Without this, an agent writing SQL is guessing at your schema from memory or from whatever you paste in. With direct, read-only access, it can verify a query actually runs and returns the shape of data you expect before you ever run it yourself.&lt;/p&gt;</description></item><item><title>Postgres Query Skill</title><link>https://vibecoding.rest/skills/postgres-query-skill/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://vibecoding.rest/skills/postgres-query-skill/</guid><description>&lt;p&gt;This skill executes safe, read-only SQL queries against PostgreSQL databases, with multi-connection support and defense-in-depth safeguards against destructive statements.&lt;/p&gt;&#10;&lt;h2 id="why-a-skill-for-this"&gt;Why a skill for this&lt;/h2&gt;&#10;&lt;p&gt;Letting a model run arbitrary SQL against a real database is risky without hard guardrails. Restricting the skill to read-only queries with explicit safeguards makes database exploration usable without risking accidental writes.&lt;/p&gt;</description></item></channel></rss>