dsh-postgres-expert

dsh-postgres-expert

PostgreSQL expertise for DeepSeek Harness. Eleven curated skills from
Tiger Data's pg-aiguide, registered as native skills, plus the public MCP
server for version-exact manual search — so the model stops writing 2015-era
schemas from memory.

Install

Anyone can install this. It needs a DeepSeek Harness profile, and nothing else —
no API key, no database and no account, because the only network call it makes is
an optional documentation search against a public endpoint.

From the GUI, paste this into Add plugin:

dsh-postgres-expert

Or from a terminal:

dsh plugin add dsh-postgres-expert

That is a plain npm install. It needs neither git nor a GitHub account.

No build step is involved. Every entry point ships as committed source, so
pnpm never has to run this package's scripts and you are never asked to
allowlist a build. Restart the profile afterwards and three rows appear.

Asking an agent instead

You can also just say "install the dsh-postgres-expert plugin in this
profile" and the agent will run the same install for you — it has a
plugin_manager install_bundle tool and writes the bundle for you. You do not
need this route, and it is not shorter; it is there because installing from an
agent is occasionally the only option available, such as over a remote host.

One thing to know if you use it: installing a package means its code runs on
your machine, so the agent will ask for approval first. That prompt is the
point, not an obstacle.

Installing by other routes

The GitHub route needs nothing but git access to this repository. The npm route
needs neither git nor an account, and is what the command above uses.

As a profile dependency, add it to package.json and to dsh.profile.bundles:

{
"dependencies": {
"dsh-postgres-expert": "1.0.0"
},
"dsh": {
"profile": {
"bundles": ["@deepseek-ai/dsh-base", "@deepseek-ai/dsh-web-app", "dsh-postgres-expert"]
}
}
}

dsh plugin add does both of those edits for you.

What it adds

The rows are independent. postgres-expert-mcp is the only one that touches
the network, so disabling it leaves the curated skills working entirely
offline:

- id: postgres-expert-mcp
disabled: true

Overriding that row replaces its whole config object, so re-declare every
field you still want. The fields are the
@deepseek-ai/dsh-mcp-client configuration:
transport, serverName, url, headers, toolCallTimeoutMs,
failOnStartupError, maxInstructionBytes and reconnect.

The skills

How they load themselves

You do not have to invoke a skill, and you do not have to remember a name. The
harness does the routing, and it happens before the model ever decides anything:

1. Every skill announces itself. At the first step of a session the harness
   injects an `` catalog carrying each skill's name and
   description — nothing else, no bodies. Each session gets this
   automatically.
2. The descriptions are the routing table. They are written for it: pg-aiguide
   packs each description with trigger phrases and a keyword line (PostgreSQL, Postgres, schema, table design, indexes, constraints, hypertable, semantic search, …). That is what makes the match, not anything this plugin does.
3. The model loads the one it needs. When the task is PostgreSQL, the model
   calls skill({ name }) by itself. That is the whole mechanism.

So "when it is about postgres" is already the behaviour: ask for a schema and
the model loads postgres or design-postgres-tables on its own. Ask about
React and nothing loads, because the catalog is the only thing in the prompt.

This plugin's own postgres-expert-prompt section reinforces it by naming the
skills and the MCP tool, so the model does not have to infer the tools exist.

The one thing this cannot do is override a deliberate restriction: a preset's
tools.restrict({ allow: [...] }), a subagent's toolFilter or a disabled
postgres-expert-skills row removes the skills from that scope, and the prompt
section withdraws itself with them rather than advertising tools it cannot
reach.

Bodies load on demand, so a session that never touches PostgreSQL pays nothing
for any of this.

The MCP connection

The harness connects to https://mcp.tigerdata.com/docs, negotiates the
protocol, discovers the tools and exposes each as an ordinary harness tool with
cancellation, permission checks and recorded results. It does not host or
supervise the server — Tiger Data runs it.

Upstream exposes exactly two tools:

source carries both corpus and version in one value — tiger,
postgres_14 … postgres_18, postgis_3.3 … postgis_3.6. There is no
separate version argument.

view_skill overlaps with the skills vendored here, which is why the skills are
registered natively rather than read back over MCP.

Discovery is asynchronous: after a restart, wait for the mcp__pg-aiguide__*
tools before sending the first prompt that needs them. If the endpoint is
unreachable the bundle still loads, failOnStartupError: false keeps it that
way, and the reconnect policy retries with backoff.

Staying current

The vendored skills under assets/skills/ are what the plugin serves, so a copy
that is not synced is a package serving stale advice.

assets/upstream.json is the provenance. It records the upstream commit, a
SHA-256 digest per file, and the licence the copy was taken under — so the exact
upstream state this package corresponds to is reviewable without fetching
anything.

npm run sync          # rewrite assets/skills/ and the pin from upstream
npm run sync:check    # fail if the vendored tree differs from what upstream gives
npm test              # behaviour tests over the catalogue and the sync helpers

A GitHub Actions workflow runs sync daily and opens a pull request when
upstream has moved. CI runs sync:check on Linux and Windows on every push
and pull request, so a package cannot be published against a stale mirror.

Releasing

Merging an upstream sync is not enough on its own: the registry serves a fixed
tarball, so a new upstream state needs a new npm version before anyone receives
it.

npm run prepublish      # every gate, without publishing
npm version patch       # 1.0.0 -> 1.0.1
npm publish
git push --follow-tags

npm publish runs scripts/prepublish.mjs first, and refuses if any of it
fails. A published name and version can never be reused, even after an
unpublish, so the gate checks that the version is free on the registry, that the
working tree is committed, and that the tag points at HEAD — otherwise the
registry and the repository would describe different code under the same
version.

How the sync reads upstream

One repository tarball, with the sha resolved by git ls-remote — so it needs no
GitHub token and cannot exhaust the API rate limit on a schedule. Two details of
the upstream tree are handled explicitly:

• Symlinks are materialised. pg-aiguide's postgres umbrella skill points
  its references/ at the sibling skills with relative symlinks. Those links do
  not survive every checkout or npm publish, so their contents are copied into
  place and the vendored tree is identical on every platform.
• Only markdown below skills/ is copied, so the output stays reviewable.

Licence and attribution

The vendored skills are redistributed unmodified under the Apache License
2.0 from timescale/pg-aiguide. See
LICENSE and NOTICE; the upstream copyright notice is
retained verbatim as that licence requires.

This plugin configures a connection to a public MCP server operated by Tiger
Data. It vendors no server code and sends no telemetry.

icon.svg is Pazalo's logo.

Layout

cordis.patch.yml            the bundle: three independent rows
icon.svg                    the plugin panel's row image
src/catalog.js              reads the vendored skills and their frontmatter
src/entry-skills.js         loader entry registering the skills
src/entry-prompt.js         loader entry publishing the guidance section
src/prompt.js               the guidance text and its visibility check
assets/skills/              the vendored pg-aiguide skills (synced, not edited)
assets/upstream.json        the upstream commit and a digest per file
scripts/sync-upstream.mjs   the vendoring tool
scripts/check-patch.mjs     CI gate: bundle patch, exports and icon
test/plugin.test.js         behaviour tests

Never edit anything under assets/skills/ by hand: the next sync overwrites it
and sync:check fails on the difference. Change upstream, or change this
plugin's own source.

Plugin © 2026 dsh-postgres-expert contributors
Skills © 2025 Timescale, Inc., d/b/a Tiger Data — Apache-2.0