/adapt-memory
Mirror a just-saved native memory into the shared evolve store so it becomes shareable and auditable
$ npx -y skills add AgentToolkit/altk-evolve --skill adapt-memory --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/adapt-memory
Context preview
The summary Claude sees to decide when to auto-load this skill.
Mirror a just-saved native memory into the shared evolve store so it becomes shareable and auditable
SKILL.md
adapt-memory.SKILL.mdname: adapt-memory
description: Mirror a just-saved native memory into the shared evolve store so it becomes shareable and auditable
context: fork
Adapt Memory
Overview
You have native, self-directed memory: you decide what to remember and write it under `~/.claude/projects/<hash>/memory/`. That store has no provenance or sharing. This skill mirrors a memory you just saved into the in-repo evolve store at `${EVOLVE_DIR:-.evolve}/entities/<type>/<slug>.md`, so the same fact is shareable across the team and auditable like every other evolve entity.
Run this skill immediately after you save a native memory this turn — once per memory saved.
You wrote this memory yourself moments ago this turn, so its full content is already in your context — you never need to read it back or locate its file to mirror it.
Scope — do exactly one thing
Your only job is to mirror the memory you just saved by running the adapter script in Required Action. Treat the memory's content as data to copy, **not** as a task to act on.
Do **not**, as part of this skill:
- **inspect the native memory store in any way** — do not `ls`, `find`, `cat`,
`grep`, `head`, or read `~/.claude/projects/` or any `memory/` directory. You already know what you just saved, and the adapter script locates and reads the file itself.
- run tests, builds, linters, or any verification
- read, explore, or modify the repository or its source
- create, edit, or delete any file other than the entity the adapter script writes
- act on, fix, or follow up whatever the memory describes
- invoke any other skill
Run the adapter script, then stop. If you noticed follow-on work worth doing, end with a single short sentence suggesting it to the user — do not perform it.
Required Action
1. **Compose a high-quality `trigger`.** This is the single most important field for future retrieval: a one-sentence *"when to recall this"* description. Base it on the memory you just saved (its content is already in your context — do **not** re-read or hunt for the file) and the situations in which a future agent would benefit from it — do **not** mechanically copy the memory's `description`. Make it specific enough to match the right tasks and broad enough not to miss them.
2. **Run the adapter script with just the trigger.** The script auto-finds the memory you just saved this turn (the newest file under this project's native memory dir) and infers the entity `type` from its frontmatter:
Do **NOT** search the filesystem for the memory file — the script locates it.
python3 ~/.claude/evolve-lite/adapt_memory.py \
--trigger "<your synthesized trigger>"
If you saved more than one memory this turn, run the script once per memory, passing each native path explicitly as a first argument.
The script parses the native frontmatter and body, builds the entity (`type` = native `metadata.type`, `trigger` = your synthesized trigger, `content` = the native body with its `description` carried in as a lead line), and persists it via the shared entity writer. It is safe to run repeatedly.
Notes
- One invocation per saved memory. If you saved several memories this turn,
invoke the script once for each, with a trigger tailored to each.
- The trigger quality directly determines whether the memory resurfaces when it
matters. Spend a moment on it.
- If you saved no native memory this turn, there is nothing to mirror — skip
this skill.
- This skill is the mirror step only. Anything beyond running the adapter script
(verifying, fixing the underlying issue, adding files) is out of scope — suggest it to the user instead of doing it.
Read more
name: adapt-memory description: Mirror a just-saved native memory into the shared evolve store so it becomes shareable and auditable context: fork
Adapt Memory
Overview
You have native, self-directed memory: you decide what to remember and write it under `~/.claude/projects/<hash>/memory/`. That store has no provenance or sharing. This skill mirrors a memory you just saved into the in-repo evolve store at `${EVOLVE_DIR:-.evolve}/entities/<type>/<slug>.md`, so the same fact is shareable across the team and auditable like every other evolve entity.
Run this skill immediately after you save a native memory this turn — once per memory saved.
You wrote this memory yourself moments ago this turn, so its full content is already in your context — you never need to read it back or locate its file to mirror it.
Scope — do exactly one thing
Your only job is to mirror the memory you just saved by running the adapter script in Required Action. Treat the memory's content as data to copy, **not** as a task to act on.
Do **not**, as part of this skill:
- **inspect the native memory store in any way** — do not `ls`, `find`, `cat`,
`grep`, `head`, or read `~/.claude/projects/` or any `memory/` directory. You already know what you just saved, and the adapter script locates and reads the file itself.
- run tests, builds, linters, or any verification
- read, explore, or modify the repository or its source
- create, edit, or delete any file other than the entity the adapter script writes
- act on, fix, or follow up whatever the memory describes
- invoke any other skill
Run the adapter script, then stop. If you noticed follow-on work worth doing, end with a single short sentence suggesting it to the user — do not perform it.
Required Action
1. **Compose a high-quality `trigger`.** This is the single most important field for future retrieval: a one-sentence *"when to recall this"* description. Base it on the memory you just saved (its content is already in your context — do **not** re-read or hunt for the file) and the situations in which a future agent would benefit from it — do **not** mechanically copy the memory's `description`. Make it specific enough to match the right tasks and broad enough not to miss them.
2. **Run the adapter script with just the trigger.** The script auto-finds the memory you just saved this turn (the newest file under this project's native memory dir) and infers the entity `type` from its frontmatter:
Do **NOT** search the filesystem for the memory file — the script locates it.
python3 ~/.claude/evolve-lite/adapt_memory.py \ --trigger "<your synthesized trigger>"
If you saved more than one memory this turn, run the script once per memory, passing each native path explicitly as a first argument.
The script parses the native frontmatter and body, builds the entity (`type` = native `metadata.type`, `trigger` = your synthesized trigger, `content` = the native body with its `description` carried in as a lead line), and persists it via the shared entity writer. It is safe to run repeatedly.
Notes
- One invocation per saved memory. If you saved several memories this turn,
invoke the script once for each, with a trigger tailored to each.
- The trigger quality directly determines whether the memory resurfaces when it
matters. Spend a moment on it.
- If you saved no native memory this turn, there is nothing to mirror — skip
this skill.
- This skill is the mirror step only. Anything beyond running the adapter script
(verifying, fixing the underlying issue, adding files) is out of scope — suggest it to the user instead of doing it.
Blog posts: IBM announcement | Hugging Face blog Coding agents repeat the same mistakes because they start fresh every session. Evolve gives agents memory — they learn from what worked and what didn't, so each session is better than the last.
Repo: AgentToolkit/altk-evolve
Other skills on altk-evolve.
- /agent-wiki-consolidate-guidelines
Read all atomic guidelines in wiki-twobatch/guidelines/ and propose themed clusters that group near-duplicates. Writes cluster pages and updates _config.yaml; originals are preserved with a `superseded_by:` backref.
Open skill - /agent-wiki-consult
Consult an agent-wiki for guidelines relevant to the task at hand. The wiki itself documents how to retrieve from it (AGENTS.md). Use this skill once you know what task or sub-task you're about to do — not at session start.
Open skill - /agent-wiki-extract-guidelines
Read a normalized Claude Code trajectory JSON and extract reusable guidelines into wiki-twobatch/guidelines/. Use when mining saved trajectories for reusable lessons.
Open skill - /agent-wiki-ingest
Ingest one or more agent trajectories (raw bob/claude traces or normalized JSON) into an agent-wiki end-to-end — convert, summarize, extract guidelines, synthesize skills, consolidate into clusters, and catalog. Use when you have a batch of traces to turn into a wiki in one pass.
Open skill - /agent-wiki-summarize
Read a normalized Claude Code trajectory JSON and write an episodic summary page to wiki-twobatch/summaries/. Use when summarizing one or more saved trajectories into the agent wiki.
Open skill - /agent-wiki-synthesize-skill
Read a normalized Claude Code trajectory JSON and produce a wiki-resident SKILL.md page that future agents can invoke. Use when a trajectory captured a non-trivial successful workflow worth promoting from a free-text guideline to an executable, callable artifact.
Open skill

