memory-starter-kit
Skill208 starsChanged 5 months agoMITView on GitHub
Historical starter note for the memory sidecar stack.
In this repository2 other files it gives its agents.
- memory-archivistSkill
- memory-proactiveSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 34
Use the installed scripts under $AGENT_HOME/scripts/ together with:
- Very specific: line 49
if a teammate is working from old notes, reconcile them against docs/compatibility-matrix.md before changing runtime behavior
≈ “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.
Files
Memory Starter Kit
Hermes-only historical note: this skill is kept for repository continuity, not as a current portable install contract.
Current Status
The old four-layer description is obsolete. The maintained local/public build is the three-layer sidecar documented in:
README.mdARCHITECTURE.mddocs/compatibility-matrix.md
Use This Skill For
- understanding the historical evolution of the project
- mapping old Hermes deployments to the current sidecar surfaces
- identifying which older helpers are no longer part of the default install set
Do Not Use This Skill As
- a production installation guide
- a multi-agent compatibility contract
- a source of current runtime dependencies
Current Portable Runtime
Use the installed scripts under $AGENT_HOME/scripts/ together with:
session_to_gbrain.pymemory_governance_rebuild.pytiered_context_injector.pymemory_guardian.pymemory_maintenance_cycle.pysidecar_acceptance_check.py
Historical Notes
- older Hermes deployments used additional local helpers not shipped by the current installer
- legacy bridge layers mentioned in earlier versions were removed from the maintained public stack
- if a teammate is working from old notes, reconcile them against
docs/compatibility-matrix.mdbefore changing runtime behavior
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
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.

