agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/postgresql/SKILL.md

postgresql

Skill4 starsChanged 10 days agoMITView on GitHub

Engineer PostgreSQL from workload evidence. Use for SQL pull requests, schemas, indexes, transactions, migrations, performance, security/RLS, backup/PITR, reports, and generated Drizzle or Jet SQL.

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use redis, mongodb and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Sorcha-PlatformSkill

    redis

    Implements Redis caching, session management, and distributed coordination for the Sorcha platform. Use when: Adding caching layers, token revocation, rate limiting, SignalR backplane, or distributed state.

    Also in 3 projects that use this

  • hoodiniSkill

    mongodb

    Work with MongoDB databases using best practices. Use when designing schemas, writing queries, building aggregation pipelines, or optimizing performance. Triggers on MongoDB, Mongoose, NoSQL, aggregation pipeline, document database, MongoDB Atlas.

    Also in 3 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Evidence: verify DB and user outcomes, record before/after window, check recovery, name uncertainty.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Fit SQL to one measured workload, version, provider, and recovery contract. PostgreSQL semantics and actual SQL outrank ORM/query-builder/provider claims.

Workflow

  1. Mode: author/review SQL; schema/index; transactions/queues; migration; tune; operate/recover; secure/tenant; report; or Jet.
  2. Contract: version/fork/provider, extensions/topology/pooler, workload, volume/skew/growth, concurrency, SLO, RPO/RTO, security, and change window. Mark unknowns; never invent production facts.
  3. Ground truth: exact SQL/parameters, transaction boundary, schema/catalog, representative data, plan/stats, waits/locks, resources, and deploy/config history.
  4. Smallest reversible change: evidence, hypothesis, expected effect, write/storage/lock/WAL cost, unhappy paths, version/provider caveats, rollback/forward-fix, abort criteria, verification.
  5. Live gate: production diagnosis defaults read-only, bounded, time-limited. Get explicit approval for writes, DDL, cancellation, role/policy/config changes, failover, restore, or destructive commands; reconfirm target.
  6. Execute once: preserve exact SQL/transaction boundaries; observe rollout and stop on abort criteria.
  7. Evidence: verify DB and user outcomes, record before/after window, check recovery, name uncertainty.

Route

WorkRead
SQL PR/diffSQL-PR-REVIEW.md plus touched domains
Queries, joins, pagination, DMLSQL-AUTHORING.md
Types, constraints, indexes, partitionsSCHEMA-INDEXES.md
Isolation, retries, locks, queuesTRANSACTIONS-ORCHESTRATION.md
DDL, backfills, generated migrationsMIGRATIONS.md
Plans, stats, benchmarksPERFORMANCE.md
Pooling, vacuum, WAL, HA, PITROPERATIONS-RECOVERY.md
Roles, RLS, tenant isolationSECURITY-TENANCY.md
Health/weekly reportWEEKLY-REPORT.md
Versions/providersVERSIONS-PROVIDERS.md
DrizzleSQL-AUTHORING.md, migrations, versions/providers
go-jet/jetGO-JET.md
Evidence/corpus refreshEVIDENCE.md

PostgreSQL 19 is preview. Recheck current docs for version-, extension-, provider-, Drizzle-, or Jet-specific behavior.

Output

context -> evidence -> recommendation -> exact SQL/code -> impact/risks -> approval/rollout -> rollback/forward-fix -> verification. Reviews put correctness/safety before style. Without live evidence, give bounded collection queries and stop at hypothesis.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free