unsubscribe
Remove a repo from the unified repos list and delete its local clone.
git clone --depth 1 https://github.com/AgentToolkit/altk-evolve /tmp/unsubscribe && cp -r /tmp/unsubscribe/platform-integrations/codex/plugins/evolve-lite/skills/evolve-lite/unsubscribe ~/.claude/skills/unsubscribeSKILL.md
# 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:
```bash
python3 "$(git rev-parse --show-toplevel 2>/dev/null || pwd)/plugins/evolve-lite/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py" --list
```
Show 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
```bash
python3 "$(git rev-parse --show-toplevel 2>/dev/null || pwd)/plugins/evolve-lite/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py" --name {name}
```
### Step 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 recallRead 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.
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.
Read a normalized Claude Code trajectory JSON and extract reusable guidelines into wiki-twobatch/guidelines/. Use when mining saved trajectories for reusable lessons.
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.
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.
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.
Discover task families across summaries and write per-family comparison pages with findings narrative. Updates wiki-twobatch/_config.yaml task definitions and writes tasks/<slug>__task.md.
Must be used near the end of any non-trivial turn that produced potentially reusable tools, guidance, errors, workarounds, or workflows, so those lessons are saved for future turns.