iwe-restore
Skill0 starsChanged 26 days agoMITView on GitHub
Restores agent memory from an exocortex Backup when moving to a new device.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- TserenTserenov/FMT-exocortex-templateedited, first seen Nov 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- TserenTserenov/FMT-exocortex-template★ 6421% same
Wrote their own version · 0
None found.
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 repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-faultSkill
- apply-capturesSkill
- archgateSkill
- artifactorSkill
- audit-docsSkill
- audit-installationSkill
- author-modeSkill
- bottleneck-pickSkill
- check-secretSkill
- consentSkill
- day-closeSkill
- day-openSkill
- decomposeSkill
- diagnoseSkill
- discovery-sessionSkill
- extendSkill
- fpfSkill
- integration-gateSkill
- iwe-bug-reportSkill
- iwe-platform-redteamSkill
- iwe-rules-reviewSkill
- iwe-updateSkill
- keSkill
- kimi-peer-writerSkill
- local-llmSkill
- month-closeSkill
- org-devSkill
- pack-creatorSkill
- pack-newSkill
- peer-conversationSkill
- personal-guide-renderSkill
- personal-guide-startSkill
- platform-bottleneckSkill
- repo-newSkill
- restore-exocortexSkill
- run-protocolSkill
- setup-wakatimeSkill
- skill-creatorSkill
- strategy-sessionSkill
- skill-idSkill
- thinkSkill
- transcribeSkill
- vdvSkill
- verify-hypothesesSkill
- verifySkill
- week-close-pilotSkill
- week-closeSkill
- wp-newSkill
- w-reflectionSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Very specific: line 63
If exocortex/ is not found → say:
- Distinctive: line 110
Ask a single question:
- Very specific: line 147
If the user chose "skip existing" — add the --ignore-existing flag.
- Very specific: line 187
Run /audit-installation for a final integrity check of the installation.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
IWE Restore — Agent Memory Restoration
When to use: you moved to a new laptop, recreated a workspace, or lost
memory/. Ifmemory/is already populated and you only want to verify it — use/audit-installation.
Arguments: $ARGUMENTS
When to use
Restores agent memory from an exocortex Backup when moving to a new device. Locates DS-strategy/exocortex/, shows what will be restored, asks for confirmation, copies memory/ + CLAUDE.md + AGENTS.md, finalizes with /audit-installation.
Promise
In 5 minutes and one confirmation — restore agent memory from a GitHub Backup. The agent will not overwrite anything silently: it shows what was found first, then waits for "yes".
Algorithm
Step 1. Find the Backup
Determine the path to the governance repo. Priority order:
- Skill argument
$ARGUMENTS(if provided) - Environment variable
$DS_STRATEGYor$GOVERNANCE_REPO - Default path
${IWE_WORKSPACE:-$HOME/IWE}/${IWE_GOVERNANCE_REPO:-DS-strategy}/ - Search:
find ${IWE_WORKSPACE:-$HOME/IWE} -maxdepth 2 -name "exocortex" -type d 2>/dev/null
GOVERNANCE="${1:-${DS_STRATEGY:-$HOME/IWE/${IWE_GOVERNANCE_REPO:-DS-strategy}}}"
EXOCORTEX="$GOVERNANCE/exocortex"If exocortex/ is not found → say:
"Backup not found. The
exocortex/folder is missing from$GOVERNANCE. Make sure the governance repo is cloned:git clone <url> ${IWE_WORKSPACE:-$HOME/IWE}/${IWE_GOVERNANCE_REPO:-DS-strategy}. If the repo is at a different path — call/iwe-restore path/to/DS-strategy."
Stop.
Step 2. Show What Was Found
Collect information about the Backup:
# List files in the backup
find "$EXOCORTEX" -maxdepth 1 -type f \( -name "*.md" -o -name "*.yaml" -o -name "*.yml" \) | sort
# Modification date of the most recent file
find "$EXOCORTEX" -maxdepth 1 -type f | xargs ls -lt 2>/dev/null | head -1Determine the path to memory/ on the current device:
HOME_SLUG=$(echo "$HOME" | sed 's|/|-|g')
MEMORY_DST="$HOME/.claude/projects/${HOME_SLUG}-IWE/memory"Show the user:
Backup found:
Source: ${IWE_WORKSPACE:-$HOME/IWE}/${IWE_GOVERNANCE_REPO:-DS-strategy}/exocortex/ (N files, last backup: DATE)
Destination: ~/.claude/projects/.../memory/
What will be restored:
memory/: [list of .md and .yaml files]
CLAUDE.md → ${IWE_WORKSPACE:-$HOME/IWE}/CLAUDE.md
AGENTS.md → ${IWE_WORKSPACE:-$HOME/IWE}/AGENTS.md (if present)
Current state of memory/:
[empty / N files already present]Step 3. Ask for Confirmation
Ask a single question:
"Restore? (yes / no / show diff)"
- no → stop, change nothing.
- show diff → go to Step 3a.
- yes → go to Step 4.
Step 3a. Diff (if requested)
For each file from the Backup that already exists in memory/:
diff "$EXOCORTEX/<file>" "$MEMORY_DST/<file>"Show differences briefly. Then ask again: "Restore with overwrite? (yes / skip existing / no)"
Step 4. Restore
4a. Create the memory/ folder if it does not exist
mkdir -p "$MEMORY_DST"4b. Copy memory files
rsync -av --exclude='CLAUDE.md' --exclude='AGENTS.md' \
--include='*.md' --include='*.yaml' --include='*.yml' \
--exclude='*' \
"$EXOCORTEX/" "$MEMORY_DST/"If the user chose "skip existing" — add the --ignore-existing flag.
4c. Copy CLAUDE.md
issue #217: substituting
{{HOME_DIR}}→$HOMEmakes restoration OS-agnostic (the Backup is written with a placeholder inday-close.sh, symmetrically withsetup.sh).$HOMEappears in the replacement part ofsed s///— escape&/\, otherwise$HOMEcontaining&is treated as "the entire matched text" and corrupts the path (cold-review finding).
WORKSPACE_DIR="${IWE_WORKSPACE:-$HOME/IWE}"
HOME_SED_SAFE=$(printf '%s' "$HOME" | sed 's/[&\]/\\&/g')
if [ -f "$EXOCORTEX/CLAUDE.md" ]; then
# If CLAUDE.md already exists — show: "CLAUDE.md already exists. Overwrite?"
# On confirmation:
sed "s|{{HOME_DIR}}|$HOME_SED_SAFE|g" "$EXOCORTEX/CLAUDE.md" > "$WORKSPACE_DIR/CLAUDE.md"
fi4d. Copy AGENTS.md
if [ -f "$EXOCORTEX/AGENTS.md" ]; then
sed "s|{{HOME_DIR}}|$HOME_SED_SAFE|g" "$EXOCORTEX/AGENTS.md" > "$WORKSPACE_DIR/AGENTS.md"
fi4e. Report
Restored:
memory/: N files copied, M skipped
CLAUDE.md: ✅ / ⏭ skipped
AGENTS.md: ✅ / — not present in backupStep 5. Verification
Run /audit-installation for a final integrity check of the installation.
Tell the user:
"Memory restored. Restart Claude Code — the agent will pick up the files from
memory/in the next Session."
Edge Cases
| Situation | Behavior |
memory/ is empty | Copy everything without prompting (only the final confirmation question) |
memory/ is already populated | Show the diff option, do not overwrite silently |
exocortex/ contains a very old backup (>30 days) | Warn: "Backup is from DATE — N days ago. Continue?" |
CLAUDE.md in workspace is newer than the backup | Warn: "The file in the workspace is N days newer than the backup. Overwriting will discard your edits." |
No write permission to memory/ | Show the error and the command to fix permissions manually |
<!-- USER-SPACE --><!-- /USER-SPACE -->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.

