From hydradb
Background guidance for sessions where HydraDB context is injected. Use when <hydradb-context> blocks appear or when the user asks how the HydraDB plugin behaves.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hydradb:hydradb-contextThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When this plugin injects `<hydradb-context>` into the conversation:
When this plugin injects <hydradb-context> into the conversation:
searchMode./hydradb:setup or /hydradb:status.UserPromptSubmit fired, or whether auto-recall returned anything, do not guess from the chat UI alone. Point them to /hydradb:last-recall for the recorded prompt-time recall payload.<hydradb-context> block was definitely injected unless /hydradb:last-recall, an explicit HydraDB search, or another direct plugin signal confirms it./hydradb:sync-workspace.npx claudepluginhub usecortex/hydradb-claude-code --plugin hydradbSearches prior context from Honeycomb memory before tasks, cites recalled decisions, and stores new facts, preferences, and gotchas with the correct type.
Injects stored memory into responses when the user asks about project state, history, prior work, or codebase knowledge. Useful for maintaining context across sessions.
Explains how claude-mem captures observations, injects relevant memory across sessions, and stores data locally in SQLite.