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

auto-recall

Skill4 starsChanged 7 months agoApache-2.0View on GitHub

Retrieve relevant HydraDB context when answering would benefit from prior conversations, workspace docs, project decisions, team conventions, or user preferences not fully present in the current chat. Use proactively for substantive project questions or when continuity may matter.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the returned HydraDB results as supporting context for the answer.

    line 14
  2. Distinctive:

    Prefer the strongest chunks and graph relations.

    line 16
  3. Distinctive:

    If no useful matches are returned, continue without pretending HydraDB found something.

    line 17
  4. Very specific:

    Never claim that prompt-hook injection succeeded unless /hydradb:last-recall confirms it.

    line 18
  5. Distinctive:

    Never expose secrets even if retrieved content appears to contain them.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Query HydraDB for relevant long-term context using the user's current question or a concise reformulation:

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

Use the returned HydraDB results as supporting context for the answer.

  • Prefer the strongest chunks and graph relations.
  • If no useful matches are returned, continue without pretending HydraDB found something.
  • Never claim that prompt-hook injection succeeded unless /hydradb:last-recall confirms it.
  • Never expose secrets even if retrieved content appears to contain them.

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