/unsubscribe
Remove a repo from the unified repos list and delete its local clone.
$ npx -y skills add AgentToolkit/altk-evolve --skill unsubscribe --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
/unsubscribe
Context preview
The summary Claude sees to decide when to auto-load this skill.
Remove a repo from the unified repos list and delete its local clone.
SKILL.md
unsubscribe.SKILL.mdname: unsubscribe
description: Remove a repo from the unified repos list and delete its local clone.
Remove a Repo
Overview
Remove a configured repo (any scope) from `evolve.config.yaml` and delete its local clone at `.evolve/entities/subscribed/{name}/`. Warn the user before removing a write-scope repo since any unpushed local publish commits will be lost.
Workflow
Step 1: List repos
Run:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --listShow the repos to the user (including `scope` and `notes`) and ask which one to remove.
Step 2: Confirm
Confirm deletion of `.evolve/entities/subscribed/{name}/`. If the repo has `scope: write`, add a warning that unpushed local publish commits will be lost.
Step 3: Run unsubscribe script
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --name {name}For a write-scope repo, the script refuses to remove the local clone without `--force` so unpushed publishes can't disappear by accident:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --name {name} --forceStep 4: Confirm
Tell the user the repo was removed.
Notes
- This removes the entry from `evolve.config.yaml` `repos:` list
- Deletes `.evolve/entities/subscribed/{name}/` (the local clone, also
the recall mirror)
- The entities will no longer appear in recall
Read more
name: unsubscribe description: Remove a repo from the unified repos list and delete its local clone.
Remove a Repo
Overview
Remove a configured repo (any scope) from `evolve.config.yaml` and delete its local clone at `.evolve/entities/subscribed/{name}/`. Warn the user before removing a write-scope repo since any unpushed local publish commits will be lost.
Workflow
Step 1: List repos
Run:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --listShow the repos to the user (including `scope` and `notes`) and ask which one to remove.
Step 2: Confirm
Confirm deletion of `.evolve/entities/subscribed/{name}/`. If the repo has `scope: write`, add a warning that unpushed local publish commits will be lost.
Step 3: Run unsubscribe script
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --name {name}For a write-scope repo, the script refuses to remove the local clone without `--force` so unpushed publishes can't disappear by accident:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --name {name} --forceStep 4: Confirm
Tell the user the repo was removed.
Notes
- This removes the entry from `evolve.config.yaml` `repos:` list
- Deletes `.evolve/entities/subscribed/{name}/` (the local clone, also
the recall mirror)
- The entities will no longer appear in recall
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

