agentleFS
Sign inStart free
hydra-dbhydra-db/hydradb-claude-code/skills/doctor/SKILL.md

doctor

Skill4 starsChanged 7 months agoApache-2.0View on GitHub

Inspect HydraDB plugin configuration, active settings, and sync state for the current workspace. Use when the user asks if HydraDB is working or why sync or recall is not happening.

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use uninstall, cancel and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    uninstall

    Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.

    Also in 6 projects that use this

  • woosikkimSkill

    cancel

    Clear any stale OMC-Slim state

    Also in 3 projects that use this

  • ibahgatSkill

    mode

    Inspect or switch omi operating mode/profile for speed, depth, autonomy, or strict quality gates.

    Also in 3 projects that use this

  • BlockSkill

    open

    Open markdown documents in Penpal for collaborative review. Use when you want a human to review a document, plan, or research artifact.

    Also in 3 projects that use this

  • QinghongLinSkill

    editor

    Read analyst.json and detective.json, make all editorial decisions — what the blog argues, which findings matter, narrative arc and section structure. No visual design. Outputs editor.md (prose) and editor.json (structure with edt_xx IDs).

    Also in 3 projects that use this

  • MicrosoftSkill

    init

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 61 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check HydraDB plugin health for the current workspace:

    line 8
  2. Very specific:

    If configuration is missing or broken, point the user to /hydradb:setup.

    line 27
  3. Very specific:

    If the user is specifically debugging prompt-time recall, point them to /hydradb:last-recall.

    line 29
  4. Very specific:

    Do not infer that UserPromptSubmit hooks failed or that no HydraDB context was injected based on this output alone.

    line 31

“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Check HydraDB plugin health for the current workspace:

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

Summarize:

  • whether the plugin is configured
  • which config layers or files were resolved
  • which API base URL is active
  • the active collection (sub-tenant)
  • whether auto-recall and auto-ingest are enabled
  • the active captureMode, searchMode, and ingestionMode
  • the active max prompt context budget
  • the active HydraDB read and write timeouts
  • how many files and sessions are currently tracked
  • any config validation errors

If configuration is missing or broken, point the user to /hydradb:setup. If captureMode is off, mention that manual session saving is available via /hydradb:ingest.

If the user is specifically debugging prompt-time recall, point them to /hydradb:last-recall.

Do not infer that UserPromptSubmit hooks failed or that no HydraDB context was injected based on this output alone. It only reports configuration and tracked state; use /hydradb:last-recall for prompt-time recall evidence.

This is the canonical command; /hydradb:status is a deprecated alias that still works.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free