Setup

Skill hydra-db/hydradb-claude-code/skills/setup

Configure the HydraDB Claude Code plugin for the current workspace. Use when the user wants to enable HydraDB memory, fix configuration, or create a workspace config file.From its SKILL.md

Install

npx -y skills add hydra-db/hydradb-claude-code --skill setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.1 KB, as published. Nobody here has run it

Configure the HydraDB plugin for the current workspace.

Check current status first:

node "${CLAUDE_PLUGIN_ROOT}/scripts/plugin.mjs" doctor --json

If HydraDB is already configured, explain which config layers are active and whether anything still needs to change.
If configuration is missing, prefer one of these paths:
- .hydradb-plugin.local.json for machine-local overrides
- .hydradb-plugin.json for shareable workspace defaults
- ${CLAUDE_PLUGIN_DATA}/config.json for persistent user-level plugin defaults
- ./.hydradb-plugin-data/config.json only when CLAUDE_PLUGIN_DATA is not available in the current environment
Use ${CLAUDE_PLUGIN_ROOT}/.hydradb-plugin.json.example for workspace config or ${CLAUDE_PLUGIN_ROOT}/config.example.json for the full shape. For a minimal safe setup, this is enough:

{
  "apiBaseUrl": "https://api.hydradb.com",
  "apiKey": "${HYDRADB_API_KEY}",
  "tenantId": "${HYDRADB_TENANT_ID}",
  "subTenantId": "",
  "autoRecall": true,
  "autoIngest": true,
  "captureMode": "off",
  "searchMode": "memory",
  "ingestionMode": "memory",
  "recallMode": "thinking",
  "graphContext": true,
  "maxContextChars": 7000,
  "requestTimeoutMs": 15000,
  "writeTimeoutMs": 15000,
  "ignoreMarker": "hydra-ignore"
}

Never invent secrets. Prefer environment variables for secret values:
- HYDRADB_API_KEY
- HYDRADB_TENANT_ID
- HYDRADB_SUB_TENANT_ID (set it explicitly; "" is valid if you want HydraDB's default sub-tenant)
- optional HYDRADB_BASE_URL
- optional HYDRADB_USER_NAME
JSON config values can reference environment variables like "${HYDRADB_API_KEY}". Prefer that over putting literal secrets into repo files.
Only put a literal API key in a file if the user explicitly asks for it. Otherwise keep secrets out of committed config.
After any config edit, recommend running:

node "${CLAUDE_PLUGIN_ROOT}/scripts/plugin.mjs" doctor

If the user wants manual-only memory, set captureMode to off and point them to /hydradb:remember or /hydradb:save-session.
If the user wants whole-session upsert behavior, set captureMode to session-upsert. If they want both isolated turns and rolling session memories, set it to both.
The default workspace sync target should usually be ingestionMode: "memory", with markdown-first includeGlobs. Only recommend knowledge or both recall if the user understands the tradeoff.
If HydraDB feels slow or the user wants tighter hook budgets, suggest lowering requestTimeoutMs and writeTimeoutMs, or setting HYDRADB_REQUEST_TIMEOUT_MS and HYDRADB_WRITE_TIMEOUT_MS.
If the plugin is configured but the user is unsure whether prompt-time recall actually ran, suggest /hydradb:last-recall. Do not claim that no context was injected unless that command or explicit recall output confirms it.

One thing to look at

SKILL.md

Keep looking