memory-setup
Skill9 starsChanged 4 months agoMITView on GitHub
Use when user says 'Set up my memory' — runs 5-question interactive setup and saves to persistent memory.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- shreeve1/Claude-Coworktheir own version, first seen Nov 1, 2026
- IlyaGorsky/memory-toolkittheir own version, first seen Nov 1, 2026
- LupoGrigi0/claude-memorytheir own version, first seen Apr 15, 2026
- thoitiettxl-cyber/Claw-IItheir own version, first seen Apr 3, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- IlyaGorsky/memory-toolkit★ 13same name
- thoitiettxl-cyber/Claw-II★ 2same name
- LupoGrigi0/claude-memory★ 0same name
- shreeve1/Claude-Cowork★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 99
After all 5 answers collected, call memory tool with operations array:
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
Memory Setup Skill
Overview
This skill provides a guided first-time setup for new users. When triggered, it runs a 5-question interactive flow using the clarify tool and saves the answers to the user's persistent memory (~/.hermes/memories/memory.md).
Trigger Conditions
Load this skill when the user says:
- "Set up my memory"
Workflow
Step 1: Announce the Setup
I'll ask 5 quick questions to learn your preferences. This runs once and saves forever.Step 2: Run Questions Sequentially (using clarify tool)
Question 1 — Browser Automation:
clarify(
question="What browser automation do you prefer?",
choices=[
"Kimi WebBridge (uses your real Chrome with your logins)",
"Chrome CDP / Playwright (headless, no login persistence)",
"No preference — whatever works"
]
)Question 2 — Research Style:
clarify(
question="How do you like deep research done?",
choices=[
"Many tabs (10+) organized in named groups",
"One focused search at a time",
"Just give me the answer/summary"
]
)Question 3 — Repeat Command:
clarify(
question="What word do you use to mean 'do it again the same way'?",
choices=[
"retry",
"rerun",
"again",
"Other (I'll specify)"
]
)Question 4 — Privacy Concerns:
clarify(
question="Any privacy/data things I should avoid?",
choices=[
"No public pastes (dpaste, GitHub Gists)",
"Local-only tools, no cloud APIs",
"Delete temp files after",
"No strong preferences"
]
)Question 5 — UI Patterns:
clarify(
question="Any UI patterns you use repeatedly?",
choices=[
"Preview pane for docs/social/localhost",
"Terminal split for logs + editor",
"Dev server on fixed port (e.g., :3000)",
"No strong patterns"
]
)Step 3: Save to Memory
After all 5 answers collected, call memory tool with operations array:
memory(
target="memory",
operations=[
{"action": "add", "content": f"User prefers {browser_choice} for all browser automation — standing preference for all future sessions."},
{"action": "add", "content": f"User prefers {research_style} research workflows. Uses \"{repeat_word}\" as a command to re-do a task with the same approach."},
{"action": "add", "content": f"User is privacy-conscious: {privacy_choice}. Avoids public pastes/external uploads."},
{"action": "add", "content": f"Preview pane workflows: use open_preview(url, label) to embed web content, files, or screenshots. Patterns: {ui_patterns}."}
]
)Step 4: Confirm Completion
✅ Done! Saved to ~/.hermes/memories/memory.md. From now on I'll:
- Use [browser_choice] for all browser tasks
- Open 10+ tabs in named groups for research
- "[repeat_word]" = re-run same methodology
- Never use dpaste/public uploads
- Open preview pane for docs/localhost/social linksImplementation Notes
- Each
clarifycall renders as clickable buttons in Hermes — user just clicks or types - Questions run sequentially (one at a time) to avoid overwhelm
- Memory entries use the
§delimiter format for proper parsing - The
memorytool batch operation ensures atomic save
Testing
To test without saving, use a test profile or mock the memory tool.
Related Skills
None — this is a standalone onboarding skill.
References
- Questions Reference
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.

