agentleFS
Sign inStart free
mage0535mage0535/hermes-memory-installer/skills/memory-proactive/SKILL.md

memory-proactive

Skill208 starsChanged 5 months agoMITView on GitHub

Proactive layered recall and generic domain-aware routing.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    use generic domains, not user- or project-specific hardcoded labels

    line 60
  2. Distinctive:

    keep recall queries portable across agent runtimes

    line 61
  3. Distinctive:

    treat this skill as an optional helper layer, not a required production contract

    line 62

≈ “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

Memory Proactive

This skill describes the current proactive recall surfaces that remain useful in the local repository.

Layered Context Injection

Primary engine: tiered_context_injector.py

It combines multiple recall paths before the next interaction:

  • recent session recall from shared SQLite state
  • governance-backed object and hub recall
  • knowledge note recall
  • optional live Hindsight recall when the query profile needs it

Example:

python3 scripts/tiered_context_injector.py --query "user preferences"

Useful knobs:

  • --min-score 0.3
  • --max-results 10
  • --recall "project status" "system config"
  • --domains project,stock

Generic Domain Routing

Helper: domain_memory.py

This is a lightweight legacy helper for splitting local memory into generic domains so one topic does not crowd out everything else.

Example domains:

  • project
  • stock
  • system
  • marketing
  • relationship
  • general

Example:

python3 scripts/domain_memory.py check project "Milestone planning note"
python3 scripts/domain_memory.py status

Guidance

  • use generic domains, not user- or project-specific hardcoded labels
  • keep recall queries portable across agent runtimes
  • treat this skill as an optional helper layer, not a required production contract

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