Guides classifying, gap-analyzing and scaffolding support for a new SQL database in pREST, from Postgres-compatible variants to entirely new dialects.
$ npx skills add prest/prest --skill sql-database-support -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install prest/prest sql-database-support --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/prest/prest.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/sql-database-support .claude/skills/sql-database-support && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sql-database-support" agent skill from https://github.com/prest/prest/tree/main/.cursor/skills/sql-database-support into .claude/skills/sql-database-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sql-database-support", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/prest/prest/tree/main/.cursor/skills/sql-database-supportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add prest/prest --skill sql-database-support -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install prest/prest sql-database-support --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prest/prest.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/sql-database-support .agents/skills/sql-database-support && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sql-database-support" agent skill from https://github.com/prest/prest/tree/main/.cursor/skills/sql-database-support into .agents/skills/sql-database-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sql-database-support", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add prest/prest --skill sql-database-support -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install prest/prest sql-database-support --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prest/prest.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/sql-database-support .cursor/skills/sql-database-support && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sql-database-support" agent skill from https://github.com/prest/prest/tree/main/.cursor/skills/sql-database-support into .cursor/skills/sql-database-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sql-database-support", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/prest/prest.git --path .cursor/skills/sql-database-support--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add prest/prest --skill sql-database-support -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install prest/prest sql-database-support --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prest/prest.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/sql-database-support .gemini/skills/sql-database-support && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sql-database-support" agent skill from https://github.com/prest/prest/tree/main/.cursor/skills/sql-database-support into .gemini/skills/sql-database-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sql-database-support", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install prest/prest sql-database-supportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add prest/prest --skill sql-database-support -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/prest/prest.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/sql-database-support .github/skills/sql-database-support && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sql-database-support" agent skill from https://github.com/prest/prest/tree/main/.cursor/skills/sql-database-support into .github/skills/sql-database-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sql-database-support", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add prest/prest --skill sql-database-support -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install prest/prest sql-database-support --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prest/prest.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/sql-database-support .opencode/skills/sql-database-support && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sql-database-support" agent skill from https://github.com/prest/prest/tree/main/.cursor/skills/sql-database-support into .opencode/skills/sql-database-support/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sql-database-support", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
sql-database-supportGuides classifying, gap-analyzing and scaffolding support for a new SQL database in pREST, from Postgres-compatible variants to entirely new dialects.
The skill is a playbook for thinking through and starting support for a SQL engine in pREST, not for shipping a full product surface in one pass. Phase A classifies the database: a Postgres-wire variant such as TimescaleDB or Citus reuses the postgres adapter and adds compose, seed and catalog quirks, while a new dialect such as MySQL or SQLite needs its own adapter implementing the adapter interface plus driver selection in the app code.
Decision criteria cover the wire protocol and driver, the SQL dialect, the catalog queries behind the listing endpoints, and identifier quoting. Phase B has you write a `DIFFERENCES.md` for the database before any Make or CI targets claim support, answering a worksheet on the runtime image, connection details, quoting, catalog listing, engine-native features, system schemas and access control, and compose ownership. Phase C maps where files and wiring change, with the TimescaleDB integration as the reference and an `examples.md` file in the bundle.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 76d114d. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
makeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
SQL Database Support for pREST loads about 1.6k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 606 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from prest/prest at commit 76d114d, republished under its MIT licence (© prest). 606 words, ~1,638 tokens.
.claude/skills/sql-database-support/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.MUST invariants: .cursor/rules/sql-database-support.mdc. Compose/workflow
package ownership: .cursor/rules/integration-layout.mdc. This skill is the
full analysis → where-to-change → scaffold playbook.
Use this to think through and start support for a SQL engine — not to ship a full product surface in one pass.
Reference engine: integration/timescaledb/ (+ DIFFERENCES.md). See
examples.md. Integration request style: skill prest-integration-tests.
Decide before scaffolding CI or adapters.
| Kind | Examples | Implication |
|---|---|---|
| Postgres-wire variant | TimescaleDB, Citus | Reuse adapters/postgres; compose, seed, catalog quirks, specific tests |
| New dialect | MySQL, SQLite, … | New adapters/<engine> implementing adapters.Adapter; driver selection in app/app.go |
Ask whether these match stock Postgres:
lib/pq vs another)RETURNING, upserts)If protocol and catalog SQL can stay on the postgres adapter with only seed/extension quirks → wire variant. If ports must emit different SQL or use another driver → new dialect. Do not greenwash a dialect as compose-only.
Write integration/<db>/DIFFERENCES.md before Make/CI targets that claim
support. Answer every item below (N/A with reason is fine).
/databases, /schemas, /tables, /columns vs stock Postgres (extra relation kinds, schemas, system catalogs)access_confine / allowlists implicationsTemplate shape: see integration/timescaledb/DIFFERENCES.md.
| Add / change | Path |
|---|---|
| Differences doc | integration/<db>/DIFFERENCES.md |
| Compose + seed | integration/<db>/docker-compose.yml, init/db-init.sh |
| Engine E2E | integration/<db>/... only |
| Make target | Makefile → test-integration-<db> |
| CI | .github/workflows/test-integration-<db>.yml (parallel with Postgres) |
Do not: new adapters/<engine>; fold into integration/postgres/docker-compose.yml.
| Add / change | Path |
|---|---|
| Ports (only if contract gaps) | adapters/*.go then make mockgen |
| Driven adapter | adapters/<engine>/ implementing adapters.Adapter (+ connector/pinger as needed) |
| Composition root | app/app.go New / EnsureAdapter (today hardcodes postgres.New) |
| Config | config/config.go (+ fail-closed for credentials; see config-resilience.mdc) |
| Unit tests | co-located under adapters/<engine>/ — TDD, ≥80% package coverage, no live DB (unit-tests-tdd.mdc, adapter-unit-tests.mdc) |
| Integration + CI | same layout as wire variant under integration/<db>/ |
Do not: import the engine from controllers/, middlewares/, or router/
(hexagonal: hexagonal-architecture.mdc).
integration/
helpers/ testutils/ suites/ # shared; suites stay on Postgres job
<db>/
docker-compose.yml
DIFFERENCES.md
... engine-specific tests ...Details: integration-layout.mdc.
integration/<db>/.suites/ run on Postgres compose; add a DB-specific compat job only if you intentionally gate that engine against the suite.prest-integration-tests / integration-tests.mdc.postgres.Load() or open live DBs outside integration/ and cmd/.When a feature is unique to one database engine (e.g., TimescaleDB's time_bucket):
Pattern:
Example — time_bucket (TimescaleDB-only):
Base postgres adapter:
func (adapter *postgres) TimeBucketClause(r *http.Request) (groupBySQL string, err error) {
return // Not supported in base postgres
}TimescaleDB adapter:
func (a *Adapter) TimeBucketClause(req *http.Request) (groupBySQL string, err error) {
// Full time_bucket implementation here
return
}Why: Base adapter must remain database-agnostic. Wire-compatible variants (Citus, Cockroach) inherit the base adapter unchanged; specialized variants override only what they need.
See rule: adapter-features.mdc.
integration/<db>/DIFFERENCES.md writtenintegration/<db>/docker-compose.yml + seed/initintegration/<db>/make test-integration-<db> (compose runs ./integration/<db>/... only).github/workflows/test-integration-<db>.ymlapp selection + mocks + unit tests (≥80%, TDD)examples.md — TimescaleDB skeleton + new-dialect file stub list.
© prest, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in .cursor/skills/sql-database-support of prest/prest.
Open the folder on GitHubat commit 76d114d
SQL Database Support for pREST next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| SQL Database Support for pREST this skillprest/prest | 4.6k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Vsql Install Serverhashgraph-online/awesome-codex-plugins | 1.2k | — | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| Squixeduardofuncao/squix | 273 | — | ~784 | Automated safety check: Pass | MIT | |
| Golang Databaseunxed/f4 | 240 | 2 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Database MarchatCod-e-Codes/marchat | 137 | — | ~985 | Automated safety check: Pass | MIT | |
| Databaseiii-hq/workers | 113 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 |
hashgraph-online/awesome-codex-plugins
Get a working VillageSQL server on this machine and prove it works — choose an install path (installer, Docker, or source), start the server, connect, load a bundled extension, and call one of its…
eduardofuncao/squix
Run SQL queries across databases (Postgres, MySQL, SQLite, etc.) via the squix CLI.
unxed/f4
Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context…
Cod-e-Codes/marchat
Changes marchat SQL schema and queries across SQLite, PostgreSQL, and MySQL using dialect helpers.
iii-hq/workers
Run SQL against PostgreSQL, MySQL, or SQLite from the iii engine — reads, writes, transactions, and prepared statements over managed connection pools.
matlab/matlab-agentic-toolkit
Reads from, writes to, and manages relational databases using MATLAB Database Toolbox.
prest/prest
Guides writing and reviewing pREST Docker-based integration tests so every HTTP request is explained by step comments or table-driven descriptions.
Categories
Guides classifying, gap-analyzing and scaffolding support for a new SQL database in pREST, from Postgres-compatible variants to entirely new dialects. The skill is a playbook for thinking through and starting support for a SQL engine in pREST, not for shipping a full product surface in one pass. Phase A classifies the database: a Postgres-wire variant such as TimescaleDB or Citus reuses the postgres adapter and adds compose, seed and catalog quirks, while a new dialect such as MySQL or SQLite needs its own adapter implementing the adapter interface plus driver selection in the app code.
SQL Database Support for pREST fits situations like: adding support for a Postgres-compatible database such as TimescaleDB or Citus; deciding whether a new database is a wire variant or a new dialect; writing the DIFFERENCES.md gap analysis for a database; planning docker-compose and GitHub workflow changes for a new engine's tests.
Run `npx skills add prest/prest --skill sql-database-support -a claude-code`. Or copy the skill folder (.cursor/skills/sql-database-support in prest/prest) into .claude/skills/sql-database-support in your project. Claude Code loads it when a task matches its description.
Run `npx skills add prest/prest --skill sql-database-support -a codex`. Or copy the skill folder (.cursor/skills/sql-database-support in prest/prest) into .agents/skills/sql-database-support in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add prest/prest --skill sql-database-support -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sql-database-support, .gemini/skills/sql-database-support, .github/skills/sql-database-support and .opencode/skills/sql-database-support in your project.
Going by SKILL.md and its folder, SQL Database Support for pREST needs the command-line tools its instructions call (make). Our summary lists: A pREST repository checkout.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
SQL Database Support for pREST is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.6k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with SQL Database Support for pREST: Vsql Install Server (hashgraph-online/awesome-codex-plugins, 1.2k stars), Squix (eduardofuncao/squix, 273 stars), Golang Database (unxed/f4, 240 stars) and Database Marchat (Cod-e-Codes/marchat, 137 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
prest (a GitHub organization) maintains it in prest/prest, which has 4,622 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: prest/prest on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
