Skills Guide

Database Query – jishono-backend

VerifiedCaution

Use this skill to run SQL queries against the jishono PostgreSQL database. Supports local dev and production databases.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/23/2026
Claude Code
#sql#postgresql#database#docker#psql

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerDevOps engineer

Automated summary

Runs SQL queries against the jishono PostgreSQL database, either locally through Docker or against production through a psql tunnel.

Strengths

  • Covers both environments (Docker dev on 5432, prod on 5433) with the exact commands to run
  • Sets a clear safety rule: default to dev and always confirm before writes on prod
  • Gives practical tips for wide results (\x), CSV export, and LIMIT on exploratory queries
  • Lists the key tables (oppslag, definisjon, boyning, brukere, forslag) to guide queries

Limitations

  • The .env.prod path is hardcoded to one user's machine and must be adapted
  • No column-level schema description beyond the table names
  • Assumes psql and Docker Compose are already set up locally
When to use it

When you need to inspect, count, or modify jishono data during development or debugging.

When not to use it

For schema migrations, code changes, or querying any database other than jishono.

Security analysis

Caution
Quality score80/100

No obfuscated payloads, destructive shell commands, or network exfiltration; all actions are transparent psql/docker invocations for a legitimate purpose. The risk is capability-based: it pulls production admin credentials into the environment and allows writes to prod with only textual confirmation, which warrants caution rather than 'safe'.

Findings
  • •Sources a production `.env.prod` file containing admin DB credentials (`DB_PASS_ADMIN_NODE`) into the shell environment before running `psql` against the prod database — those exported secrets persist for subsequent commands in the same session.
  • •Grants the agent admin-level access to a production database and permits write operations (INSERT/UPDATE/DELETE) there, guarded only by an honor-system instruction to 'always confirm'.
  • •Hardcoded absolute path `/Users/pg/kode/jisho/jishono-backend/.env.prod` leaks a local username/directory layout and is non-portable.
  • •Broad trigger wording ('check the data', 'look up rows') could route unrelated tasks into live DB access.
How this analysis is made

Examples

Count dictionary entries
Query the local database and count how many rows are in the oppslag table.
Inspect a user
Look up the rows in the brukere table and show me the 5 most recent users.
Read-only prod check
On the prod database, run a SELECT to show the 10 latest rows in fors lag with a LIMIT.

name: db-query description: Use this skill to run SQL queries against the jishono database. Trigger for requests like "query the database", "run a SQL query", "check the data", "look up rows", "count entries", or any task that requires reading from or writing to the PostgreSQL database. Supports both the local dev database (via Docker) and the prod database (on localhost:5433).

Database Query — jishono-backend

Run SQL queries against the jishono PostgreSQL database.

Connection details

Local dev database (default)

Accessed via the Docker postgres service. The local dev DB is exposed on localhost:5432.

docker compose exec -T postgres psql -U postgres -d jishono -c "<SQL>"

For multi-line or complex queries, use a heredoc:

docker compose exec -T postgres psql -U postgres -d jishono <<'SQL'
SELECT ...
FROM ...
WHERE ...;
SQL

Production database

The prod database is tunneled/available on localhost:5433. Use psql directly (not via Docker): Source the .env.prod file first:

source /Users/pg/kode/jisho/jishono-backend/.env.prod && PGPASSWORD="$DB_PASS_ADMIN_NODE" psql -h localhost -p 5433 -U "$DB_USER_ADMIN_NODE" -d jishono -c "<SQL>"

Which database to use

  • Default to local dev unless the user explicitly says "prod", "production", or "live".
  • Always confirm before running write operations (INSERT, UPDATE, DELETE) on prod.
  • SELECT queries on prod are safe to run without confirmation.

Useful tips

  • Use \x or --expanded for wide result sets.
  • Use LIMIT on exploratory queries to avoid dumping huge tables.
  • For CSV output: psql ... -A -F',' -c "SELECT ..."
  • The -T flag on docker compose exec is important to avoid TTY issues.

Key tables

  • oppslag — dictionary entries (lemma_id, oppslag, boy_tabell, etc.)
  • definisjon — definitions linked to oppslag via lemma_id
  • boyning tables — subst_boy, verb_boy, adj_boy, adv_boy, det_boy, pron_boy
  • brukere — users
  • forslag — definition suggestions
  • oppslag_forslag — new entry suggestions
  • veggen_innlegg — community wall posts
  • page_traffic — page visit tracking

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/database-query-jishono-backend-mrx3xwfs/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/database-query-jishono-backend-mrx3xwfs' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/database-query-jishono-backend-mrx3xwfs/download' --output '.skill-downloads/database-query-jishono-backend-mrx3xwfs/SKILL.md.part' && mv '.skill-downloads/database-query-jishono-backend-mrx3xwfs/SKILL.md.part' '.skill-downloads/database-query-jishono-backend-mrx3xwfs/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/database-query-jishono-backend-mrx3xwfs/SKILL.md' && test -s '.skill-downloads/database-query-jishono-backend-mrx3xwfs/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/db-query' && cp -R '.skill-downloads/database-query-jishono-backend-mrx3xwfs' '.claude/skills/db-query'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/database-query-jishono-backend-mrx3xwfs'

openskills read 'database-query-jishono-backend-mrx3xwfs'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/database-query-jishono-backend-mrx3xwfs/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot