db
Connect to any database — Cloud SQL, PostgreSQL, Snowflake, Databricks, Athena, Presto, or Oracle.
Install / Use
npx skills add rajitsaha/100xprismInstalls into whichever agent you are using.
Cursor Rules
Cursor IDE rules (v2)
Quality Score
Category
Data & AnalyticsSupported Platforms
Our assessment of db
db scores 76/100 on our quality scale, 549th of 605 Data & Analytics skills we index.
Its Cursor Rules is 7.3 KB long, well organised into 22 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- The repository was last updated today, so db is actively maintained.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 80/100, with 2 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
db compared with similar skills
All 4 of these similar skills score higher than db; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| db (this skill)by rajitsaha | 76 | 0 | today | Cursor Rules |
| claude-memby thedotmack | 100 | 100.3k | today | CLAUDE.md |
| ccs-alignby thedotmack | 100 | 97.1k | 6d ago | SKILL.md |
| site-architectureby coreyhaines31 | 100 | 51.4k | 38d ago | SKILL.md |
| diagram-designby cathrynlavery | 100 | 42.3k | 23d ago | SKILL.md |
Frequently asked questions
- How do I install db?
- Run
npx skills add rajitsaha/100xprism. The install tabs above show the steps for each supported agent. - Which AI agents does db work with?
- It is written for Cursor, as a Cursor Rules file. Other agents that read the same format can often use it too.
- Is db safe to use?
- It declares no license and scores 80/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is db still maintained?
- The repository was last updated today, so db is actively maintained.
Skill content
View source on GitHubdescription: Connect to any database — Cloud SQL, PostgreSQL, Snowflake, Databricks, Athena, Presto, or Oracle. globs: alwaysApply: false
<!-- generated by 100xprism from modules/db/SKILL.md -->DB — Universal Database Access
Reads connection config from the project instruction file (CLAUDE.md, AGENTS.md, .cursorrules, or equivalent) or ~/.claude/db-connections.json (global registry).
Scope:
/dbexecutes specific SQL or migrations against named connections. For analytics in plain English, use/query.
Supported engines
cloud-sql | postgres | snowflake | databricks | athena | presto | oracle
Usage
/db— default audit query for current project DB/db "SELECT count(*) FROM users"— arbitrary SQL on current project DB/db migrate— run pending migrations/db prod-snowflake— named connection from global registry/db prod-snowflake "SELECT ..."— named connection + custom SQL
Step 0 — Parse arguments
# If first arg looks like a connection name (no spaces, no SQL keywords), treat as named connection
ARGS="${1:-}"
if echo "$ARGS" | grep -qE '^[a-zA-Z0-9_-]+$' && ! echo "$ARGS" | grep -qiE '^(SELECT|INSERT|UPDATE|DELETE|CREATE|DROP|ALTER|SHOW|DESCRIBE|migrate)'; then
NAMED_CONNECTION=$(echo "$ARGS" | awk '{print $1}')
SQL=$(echo "$ARGS" | cut -s -d' ' -f2-)
else
NAMED_CONNECTION=""
SQL="$ARGS"
fi
Step 1 — Load connection config
# Detect project instruction file
INSTRUCTION_FILE=$(ROOT=$(git rev-parse --show-toplevel 2>/dev/null); for f in CLAUDE.md AGENTS.md .cursorrules; do [ -f "$ROOT/$f" ] && echo "$ROOT/$f" && break; done)
DB_CONNECTIONS="$HOME/.claude/db-connections.json"
if [ -n "$NAMED_CONNECTION" ]; then
ENGINE=$(python3 -c "import json; d=json.load(open('$DB_CONNECTIONS')); c=d.get('$NAMED_CONNECTION',{}); print(c.get('engine',''))" 2>/dev/null)
CONFIG_SOURCE="registry:$NAMED_CONNECTION"
elif [ -n "$INSTRUCTION_FILE" ] && grep -q "^engine:" "$INSTRUCTION_FILE" 2>/dev/null; then
ENGINE=$(grep "^engine:" "$INSTRUCTION_FILE" | head -1 | cut -d: -f2 | tr -d ' ')
CONNECTION_NAME=$(grep "^connection:" "$INSTRUCTION_FILE" | head -1 | cut -d: -f2 | tr -d ' ')
CONFIG_SOURCE="instruction-file"
elif [ -f "$DB_CONNECTIONS" ]; then
echo "No DB config found in project instruction file. Available connections:"
python3 -c "
import json
d = json.load(open('$DB_CONNECTIONS'))
for i, (name, cfg) in enumerate(d.items(), 1):
print(f' {i}) {name} ({cfg.get(\"engine\",\"unknown\")})')
"
read -rp "Select connection (number or name): " SELECTION
NAMED_CONNECTION=$(python3 -c "
import json, sys
d = json.load(open('$DB_CONNECTIONS'))
keys = list(d.keys())
sel = '$SELECTION'
if sel.isdigit() and 1 <= int(sel) <= len(keys):
print(keys[int(sel)-1])
elif sel in d:
print(sel)
else:
print('', end='')
" 2>/dev/null)
ENGINE=$(python3 -c "import json; d=json.load(open('$DB_CONNECTIONS')); print(d.get('$NAMED_CONNECTION',{}).get('engine',''))" 2>/dev/null)
CONFIG_SOURCE="registry:$NAMED_CONNECTION"
else
echo "ERROR: No database config found."
echo " Option 1: Add a '## Database' section to your project instruction file"
echo " Option 2: Create ~/.claude/db-connections.json with named connections"
exit 1
fi
if [ -z "$ENGINE" ]; then
echo "ERROR: Could not determine database engine from config."
exit 1
fi
echo "Engine: $ENGINE | Config: $CONFIG_SOURCE"
Step 2 — Load connection details from registry (if using named connection)
if [ -n "$NAMED_CONNECTION" ]; then
# Extract all fields from the named connection into shell variables
eval "$(python3 -c "
import json, shlex
d = json.load(open('$HOME/.claude/db-connections.json'))
cfg = d.get('$NAMED_CONNECTION', {})
for k, v in cfg.items():
if k != 'engine':
print(f'CONN_{k.upper()}={shlex.quote(str(v))}')
" 2>/dev/null)"
fi
Step 3 — Resolve credentials
AUTH="${CONN_AUTH:-$(grep '^auth:' "$INSTRUCTION_FILE" 2>/dev/null | head -1 | cut -d: -f2- | tr -d ' ')}"
case "$AUTH" in
gcp-secret:*)
SECRET_NAME="${AUTH#gcp-secret:}"
DB_CRED=$(gcloud secrets versions access latest --secret="$SECRET_NAME" --project="${CONN_GCP_PROJECT:-$(grep '^gcp_project:' "$INSTRUCTION_FILE" | cut -d: -f2 | tr -d ' ')}")
echo "Credential resolved from GCP Secret Manager ✓"
;;
env:*)
VAR_NAME="${AUTH#env:}"
DB_CRED="${!VAR_NAME}"
# Fall back to .env file
if [ -z "$DB_CRED" ] && [ -f "$(git rev-parse --show-toplevel 2>/dev/null)/.env" ]; then
DB_CRED=$(grep "^${VAR_NAME}=" "$(git rev-parse --show-toplevel)/.env" | cut -d= -f2-)
fi
[ -z "$DB_CRED" ] && { echo "ERROR: Env var $VAR_NAME not set and not in .env"; exit 1; }
echo "Credential resolved from env var $VAR_NAME ✓"
;;
sso)
DB_CRED=""
echo "Using SSO auth — browser window will open ✓"
;;
keychain:*)
KEY_NAME="${AUTH#keychain:}"
DB_CRED=$(security find-generic-password -a "$KEY_NAME" -w 2>/dev/null)
[ -z "$DB_CRED" ] && { echo "ERROR: Keychain key '$KEY_NAME' not found"; exit 1; }
echo "Credential resolved from macOS keychain ✓"
;;
databricks-token)
DB_CRED="${DATABRICKS_TOKEN:-$(grep -A5 '\[DEFAULT\]' "$HOME/.databrickscfg" 2>/dev/null | grep '^token' | cut -d= -f2 | tr -d ' ')}"
[ -z "$DB_CRED" ] && { echo "ERROR: No Databricks token found"; exit 1; }
echo "Credential resolved from Databricks config ✓"
;;
*)
DB_CRED=""
echo "WARNING: No auth method specified — proceeding without credentials"
;;
esac
Step 4 — Set default SQL if not provided
if [ -z "$SQL" ]; then
SQL="SELECT 'connected' AS status, current_timestamp AS at"
echo "No SQL provided — running default connectivity check"
fi
Step 5 — Delegate to engine file
ENGINE_FILE="$HOME/.claude/commands/db-engines/${ENGINE}.md"
if [ ! -f "$ENGINE_FILE" ]; then
echo "ERROR: No engine file found at $ENGINE_FILE"
echo "Supported engines: cloud-sql, postgres, snowflake, databricks, athena, presto, oracle"
exit 1
fi
echo "Delegating to db-engines/${ENGINE}.md..."
echo "---"
# Pass all resolved variables to the engine skill
# The engine file will use these pre-resolved values:
# - For cloud-sql: INSTANCE=$CONN_INSTANCE, GCP_PROJECT=$CONN_GCP_PROJECT, DB_NAME=$CONN_DB_NAME, DB_USER=$CONN_DB_USER, DB_PASS=$DB_CRED
# - For postgres: DB_HOST=$CONN_HOST, DB_PORT=$CONN_PORT, DB_NAME=$CONN_DATABASE, DB_USER=$CONN_USER, DB_PASS=$DB_CRED
# - For snowflake: SF_ACCOUNT=$CONN_ACCOUNT, SF_WAREHOUSE=$CONN_WAREHOUSE, SF_DATABASE=$CONN_DATABASE, SF_ROLE=$CONN_ROLE, SF_USER=$CONN_USER, SF_TOKEN=$DB_CRED, SF_AUTH=$AUTH
# - For databricks: DBX_HOST=$CONN_HOST, DBX_HTTP_PATH=$CONN_HTTP_PATH, DBX_TOKEN=$DB_CRED, DBX_CATALOG=$CONN_CATALOG, DBX_SCHEMA=$CONN_SCHEMA
# - For athena: ATHENA_REGION=$CONN_REGION, ATHENA_DATABASE=$CONN_DATABASE, ATHENA_WORKGROUP=$CONN_WORKGROUP, ATHENA_S3_OUTPUT=$CONN_S3_OUTPUT
# - For presto: PRESTO_HOST=$CONN_HOST, PRESTO_PORT=$CONN_PORT, PRESTO_USER=$CONN_USER, PRESTO_CATALOG=$CONN_CATALOG, PRESTO_SCHEMA=$CONN_SCHEMA, PRESTO_TOKEN=$DB_CRED, PRESTO_ENGINE=$CONN_ENGINE
# - For oracle: ORA_HOST=$CONN_HOST, ORA_PORT=$CONN_PORT, ORA_SERVICE=$CONN_SERVICE, ORA_USER=$CONN_USER, ORA_PASS=$DB_CRED
# SQL=$SQL is passed to all engines
# Follow the instructions in db-engines/${ENGINE}.md using the variable mappings above
Related Skills
claude-mem
100.3kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
ccs-align
97.1kRun the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → get_observations, land them in a seat-owned middle cache via atomic grab → append → filter exclude-marks → replace, manage exclude marks, and walk hous…
site-architecture
51.4kWhen the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.
diagram-design
42.3kCreate branded architecture, IT current-state, flowchart, sequence, state machine, ER/data model, timeline, swimlane, quadrant, radar/spider, polar chart (polar/radial lollipop), loop/flywheel, nested, tree, org chart, layer stack, Venn, pyramid/funnel, treemap, heatmap, bar, waterfall, line, Gantt…
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
