Agent skill

DB

GPL-3.0Auto-check: notesDatabases

Install DB

skills CLI

$ npx skills add plan4better/goat --skill db -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install plan4better/goat db --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/plan4better/goat.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/db .claude/skills/db && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "db" agent skill from https://github.com/plan4better/goat/tree/main/.claude/skills/db into .claude/skills/db/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "db", 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

$skill-installer install https://github.com/plan4better/goat/tree/main/.claude/skills/db

Type 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.

skills CLI

$ npx skills add plan4better/goat --skill db -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install plan4better/goat db --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/plan4better/goat.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/db .agents/skills/db && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "db" agent skill from https://github.com/plan4better/goat/tree/main/.claude/skills/db into .agents/skills/db/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "db", 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.

skills CLI

$ npx skills add plan4better/goat --skill db -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install plan4better/goat db --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/plan4better/goat.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/db .cursor/skills/db && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "db" agent skill from https://github.com/plan4better/goat/tree/main/.claude/skills/db into .cursor/skills/db/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "db", 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

$ gemini skills install https://github.com/plan4better/goat.git --path .claude/skills/db

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add plan4better/goat --skill db -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install plan4better/goat db --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/plan4better/goat.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/db .gemini/skills/db && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "db" agent skill from https://github.com/plan4better/goat/tree/main/.claude/skills/db into .gemini/skills/db/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "db", 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.

GitHub CLI

$ gh skill install plan4better/goat db

Installs 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).

skills CLI

$ npx skills add plan4better/goat --skill db -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/plan4better/goat.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/db .github/skills/db && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "db" agent skill from https://github.com/plan4better/goat/tree/main/.claude/skills/db into .github/skills/db/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "db", 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.

skills CLI

$ npx skills add plan4better/goat --skill db -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install plan4better/goat db --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/plan4better/goat.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/db .opencode/skills/db && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "db" agent skill from https://github.com/plan4better/goat/tree/main/.claude/skills/db into .opencode/skills/db/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "db", 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.

Facts

Skill name: db
GitHub stars: 167
Token cost: ~1.3k tokens
SKILL.md length: 398 words
Files: 1
Skills in repo: 2
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: GPL-3.0

At a glance

Understanding the GOAT PostgreSQL database — querying projects
SKILL.md covers Connection, Schemas, Key Tables & Relationships and Common Queries, plus 1 more section
Calls docker; needs POSTGRES_PASSWORD
Checking data state during local dev

What it does

DB is an agent skill from plan4better/goat. Use when inspecting, debugging, or understanding the GOAT PostgreSQL database — querying projects, layers, users, orgs, teams, roles, jobs, or checking data state during local dev.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases. It works with PostgreSQL. The repository describes itself as: WebGIS with Planning Intelligence. The licence is GPL-3.0.

When your agent uses it

Understanding the GOAT PostgreSQL database — querying projects
Checking data state during local dev

Example prompts

“/db”

Requirements

Docker

What it can do on your machine

Read from SKILL.md and the folder at commit a181bf4. It shows what the files ask for, not the result of running them.

Tool permissions
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.
Runs code
Shell commands in SKILL.md call:
- docker
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- POSTGRES_PASSWORD
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

DB loads about 1.3k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 398 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~46
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NoteMentions a .env fileSKILL.md:16
```
source /home/p4b/goat/.env
```
NoteMentions a .env fileSKILL.md:24
```
source /home/p4b/goat/.env
```

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.

SKILL.md

The full file from plan4better/goat at commit a181bf4, republished under its GPL-3.0 licence (© plan4better). 398 words, ~1,276 tokens.

Download SKILL.mdSave it as .claude/skills/db/SKILL.md (or your agent's skills folder).

name: db
description: Use when inspecting, debugging, or understanding the GOAT PostgreSQL database — querying projects, layers, users, orgs, teams, roles, jobs, or checking data state during local dev.

Database Query

Query the GOAT PostgreSQL database to inspect data, debug issues, and understand state.

Connection

There is no host psql; go through the running Postgres container. The container name changes across setups (goat-db, goat-db18, …), so discover it rather than hardcoding:

bash

source /home/p4b/goat/.env
DBC=$(docker ps --format '{{.Names}}' | grep -E '^goat-db' | head -1)
docker exec -e PGPASSWORD=$POSTGRES_PASSWORD "$DBC" psql -h 127.0.0.1 -U $POSTGRES_USER -d $POSTGRES_DB

One-off query:

bash

source /home/p4b/goat/.env
DBC=$(docker ps --format '{{.Names}}' | grep -E '^goat-db' | head -1)
docker exec -e PGPASSWORD=$POSTGRES_PASSWORD "$DBC" psql -h 127.0.0.1 -U $POSTGRES_USER -d $POSTGRES_DB -c "YOUR SQL HERE"

Schemas

Schema	Purpose
`customer`	Everything: users, orgs, teams, roles/permissions, projects, layers, jobs, workflows
`ducklake`	DuckLake catalog (managed by geoapi, don't modify directly)

Key Tables & Relationships

The SQLModel definitions in apps/core are the source of truth — introspect when unsure:

sql

SELECT table_name FROM information_schema.tables WHERE table_schema='customer' ORDER BY 1;
\d customer.layer

Identity & sharing (all in `customer`)

user (id uuid) — Keycloak-synced. firstname, lastname, avatar
organization (id uuid) — name, avatar; organization_domain, organization_analytics
team (id uuid) — belongs to org. name, avatar
role (id uuid) — permission roles; RBAC via permission, role_permission, user_role, resource, resource_grant, resource_permission
user_team — M2M user ↔ team; invitation — pending org/team invites
layer_organization / layer_team / layer_user — layer sharing with role
project_organization / project_team / project_user — project sharing with role

Projects & layers (`customer`)

project (id uuid) — user_id, folder_id, layer_order[], basemap, tags[]
layer (id uuid) — user_id, folder_id. Key fields: name, type, data_type, tool_type, job_id, feature_layer_type, feature_layer_geometry_type, extent (geometry), properties (jsonb), other_properties (jsonb — holds catalog_item / catalog_materialize for promoted catalog layers), field_config (jsonb, per-column metadata), url, size, in_catalog, tags[], catalog_external_uid, catalog_version
layer_project (id int) — M2M layer ↔ project. name, properties (jsonb style config), other_properties, query (jsonb filters), charts, order, layer_project_group_id
layer_project_group (id int) — layer groups. project_id, parent_id (self-ref nesting), order
folder (id uuid) — user_id, name
job (id uuid) — user_id. type, status, payload (jsonb)
workflow (id uuid) — project_id, name, config (jsonb), is_default
report / report_layout (id uuid) — project_id, name, config (jsonb), is_default
project_public — public sharing config: password, config (jsonb snapshot)
user_project — user ↔ project with initial_view_state (jsonb)
system_setting — per-user: client_theme, preferred_language, unit
uploaded_asset — user uploads: s3_key, file_name, mime_type, file_size, asset_type, content_hash
cost / credit_usage — credit metering

Show full SKILL.md (117 more words)Show less

Common Queries

sql

-- Projects with layer counts
SELECT p.id, p.name, p.created_at, COUNT(lp.id) AS layer_count
FROM customer.project p
LEFT JOIN customer.layer_project lp ON lp.project_id = p.id
GROUP BY p.id ORDER BY p.created_at DESC;

-- Layers in a project with styles
SELECT lp.id, lp.name, lp.order, l.type, l.feature_layer_type, l.feature_layer_geometry_type
FROM customer.layer_project lp
JOIN customer.layer l ON l.id = lp.layer_id
WHERE lp.project_id = 'PROJECT_UUID'
ORDER BY lp.order;

-- Job status
SELECT id, type, status, created_at, payload->>'tool_type' AS tool
FROM customer.job ORDER BY created_at DESC LIMIT 10;

Important Notes

Layer metadata lives in PostgreSQL (customer.layer), layer data lives in DuckLake (managed by geoapi)
layer_project.properties = style/rendering config (jsonb); layer_project.query = active filters (jsonb)
Scenarios are gone (2026-08-27): the feature, the three tables and project.active_scenario_id were all removed. scenario_feature was the last table using generic columns (integer_attr1..25); nothing in GOAT uses that scheme any more
A catalog layer has no owner: layer.user_id and layer.folder_id are NULL for promoted catalog layers. Joins from layer to user must be LEFT joins or those rows vanish
A public dashboard reads the project_public.config snapshot, not the live project — re-publish to reflect changes
Always use READ-ONLY queries. Never INSERT/UPDATE/DELETE unless explicitly asked
Use ST_AsText() or ST_AsGeoJSON() to read geometry columns

Files

Just SKILL.md in .claude/skills/db of plan4better/goat.

Open the folder on GitHubat commit a181bf4

Compare with similar skills

DB 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.

DB compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
DB this skillplan4better/goat	167	—	~1.3k	Automated safety check: Notes	GPL-3.0	yesterday
Find Postgres Bugdigoal/blog	8.6k	—	~4k	Automated safety check: Pass	GPL-2.0	10 days ago
Diesel Guardayarotsky/diesel-guard	121	—	~3.1k	Automated safety check: Pass	MIT	10 days ago
Releaserogerpadilla/uql	125	—	~842	Automated safety check: Pass	MIT	today
Srtd Devt1mmen/srtd	105	—	~2.3k	Automated safety check: Pass	MIT	1 mo ago
SQLx Offline Cache Updaterwindmill-labs/windmill	18k	—	~1.7k	Automated safety check: Pass	Custom licence	today

Similar skills

Find Postgres Bug
digoal/blog
Find latent bugs in a local PostgreSQL source tree (RELxxSTABLE branch or HEAD) the way a core hacker does: build a heavily-poisoned debug instance (cassert + cache-discard + -O0/-ggdb3 + core…
8.6k GitHub stars~4k tokensUpdated 10 days ago
DatabasesAuto-check passed
Diesel Guard
ayarotsky/diesel-guard
Lints Diesel and SQLx Postgres migrations for unsafe schema changes that lock tables or cause downtime, and authors custom Rhai checks.
121 GitHub stars~3.1k tokensUpdated 10 days ago
DatabasesAuto-check passed
Release
rogerpadilla/uql
Cut and publish a uql release - review the change, changelog entry, commit, version bump and tag, GitHub Release, npm publish, docs site.
125 GitHub stars~842 tokensUpdated today
DatabasesAuto-check passed
Srtd Dev
t1mmen/srtd
Expert knowledge for developing the SRTD codebase itself. An agent skill from t1mmen/srtd.
105 GitHub stars~2.3k tokensUpdated 1 mo ago
DatabasesAuto-check passed
SQLx Offline Cache Updater
windmill-labs/windmill
Safely regenerates Windmill's SQLx offline query cache after a SQL query changes in Rust, with a mandatory backup step and worktree-specific database checks.
18k GitHub stars~1.7k tokensUpdated today
DatabasesAuto-check passed
DB AI GitHub Paper Weekly News
digoal/blog
抓取并汇总"数据库、AI、GitHub、AI 论文"近 1 周新闻，输出图文并茂（含 mermaid 图）的 markdown 周报到当前项目的 markdown/ 目录。覆盖 10 个数据源：postgresweekly.com/issues（自动解析最新 issue…
8.6k GitHub stars~1.2k tokensUpdated 10 days ago
DatabasesAuto-check passed

Questions about DB

What does DB do?

A skill your agent uses when inspecting, debugging, or understanding the GOAT PostgreSQL database — querying projects, layers, users, orgs, teams, roles, jobs, or checking data state during local dev. DB is an agent skill from plan4better/goat. Use when inspecting, debugging, or understanding the GOAT PostgreSQL database — querying projects, layers, users, orgs, teams, roles, jobs, or checking data state during local dev.

When should I use DB?

DB fits situations like: understanding the GOAT PostgreSQL database — querying projects; checking data state during local dev.

How do I install DB in Claude Code?

Run `npx skills add plan4better/goat --skill db -a claude-code`. Or copy the skill folder (.claude/skills/db in plan4better/goat) into .claude/skills/db in your project. Claude Code loads it when a task matches its description.

How do I install DB in Codex?

Run `npx skills add plan4better/goat --skill db -a codex`. Or copy the skill folder (.claude/skills/db in plan4better/goat) into .agents/skills/db in your project. Codex loads it when a task matches its description.

Can I use DB in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add plan4better/goat --skill db -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/db, .gemini/skills/db, .github/skills/db and .opencode/skills/db in your project.

What does DB need to run?

Going by SKILL.md and its folder, DB needs the command-line tools its instructions call (docker) and credentials named POSTGRES_PASSWORD. Our summary lists: Docker.

Does DB access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is DB safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does DB use?

DB is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does DB use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to DB?

Skills that share tags, products or a category with DB: Find Postgres Bug (digoal/blog, 8.6k stars), Diesel Guard (ayarotsky/diesel-guard, 121 stars), Release (rogerpadilla/uql, 125 stars) and Srtd Dev (t1mmen/srtd, 105 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains DB?

plan4better (a GitHub organization) maintains it in plan4better/goat, which has 167 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

Source: plan4better/goat on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install DB

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Database Query

Connection

Schemas

Key Tables & Relationships

Identity & sharing (all in customer)

Projects & layers (customer)

Common Queries

Important Notes

Files

Compare with similar skills

Similar skills

Find Postgres Bug

Diesel Guard

Release

Srtd Dev

SQLx Offline Cache Updater

DB AI GitHub Paper Weekly News

More from plan4better/goat

Windmill

Related

Questions about DB

Identity & sharing (all in `customer`)

Projects & layers (`customer`)