aim-memory-wiki
MANDATE: You are the active agent in a session, and the user has activated the aim-memory-wiki skill. Your objective is to process the recent session context, extract key discoveries, code decisions, and milestones, and incrementally update the persistent knowledge base located in memory-wiki/.
1. THE CORE PHILOSOPHY
The wiki is a persistent, compounding artifact — a structured, interlinked collection of markdown files. It sits between the user and raw data. You do not just index data for retrieval; you read it, extract key information, and integrate it into the existing wiki (updating entity pages, revising topic summaries, noting where new data contradicts old claims).
The wiki keeps getting richer with every source you add and every session you summarize.
2. BOOTSTRAPPING (IF EMPTY)
If memory-wiki/ does not exist or is completely empty (no index.md or log.md), you must scaffold it:
- Create
memory-wiki/index.md with a # Project Wiki Index header and basic placeholder sections (e.g., ## Core Concepts, ## Architecture).
- Create
memory-wiki/log.md with a # Memory Log header to track chronological ingestion events.
- Create the
memory-wiki/pages/ directory to house individual detailed markdown files.
3. THE THREE LAYERS
- Raw Sources: External files, chat history, or code that you read but do not modify.
- The Wiki: A directory of LLM-generated markdown files (
memory-wiki/). You own this layer entirely. You create pages, update them, maintain cross-references, and keep everything consistent.
- The Schema: Rules and configurations (like
AGENTS.md) that guide how you act.
4. GITOPS WORKFLOW (MANDATORY)
Because you are updating the persistent architecture of the repository, you MUST follow strict GitOps procedures. Do not commit wiki updates directly to the main branch.
- Open an Issue: Track the wiki documentation updates via a formal issue ticket (e.g., using
gh issue create or aim bug).
- Branch Out: Spawn a GitOps sandbox (e.g.,
aim fix <issue_id> or standard git checkout -b fix/...) to perform your edits safely.
- Update the Wiki: Perform all the ingestion, writing, and linting within this isolated branch.
- Clean up & Promote: Once the wiki is updated and verified, commit the changes, close the issue, and cleanly merge/promote the branch back to main (e.g.,
aim promote).
5. YOUR OPERATIONS WHEN TRIGGERED
When the user invokes this skill, you must perform an Ingest operation synchronously:
- Synthesize Context: Review what was accomplished, decided, or learned in the recent session. Do NOT copy raw transcripts. Extract the tactical takeaways, architectural changes, or deep insights.
- Update the Index (
memory-wiki/index.md): This is the content-oriented catalog. If you create a new page or identify a new core concept, add a link and a one-line summary to index.md. Organize it by category (entities, concepts, etc.).
- Update the Log (
memory-wiki/log.md): This is a chronological, append-only record of operations. You MUST append an entry detailing what you ingested.
- Format:
## [YYYY-MM-DD] ingest | <Title of the update>
- Include a brief bulleted summary of what pages were touched.
- Update/Create Content Pages:
- Open existing relevant pages (e.g.,
memory-wiki/pages/architecture.md) and integrate the new facts.
- If a topic is new and complex, create a new file (e.g.,
memory-wiki/pages/new_concept.md) and interlink it with existing pages using standard Markdown links ([Concept](concept.md)).
- Resolve any contradictory stale claims from older versions.
6. LINTING AND CROSS-REFERENCING
Always ensure:
- No orphaned pages exist. If you make a new page, link to it from
index.md or another relevant page.
- Links are valid relative markdown links.
- Your summaries are precise and dense with signal, free of conversational filler.
7. EXECUTION
Proceed by explicitly generating your proposed memory updates for the user to review, or immediately begin writing to the memory-wiki/ directory depending on the user's prompt.
Vessel file tools (dual — do not strip either host)
Use the file tools of the host CLI you are running in. Both columns remain valid; never replace one host's tools with the other when editing this skill.
| Vessel |
Read |
Create / overwrite |
Edit in place |
| Grok CLI |
read_file |
write |
search_replace |
| AGY / Antigravity |
host read tools |
write_to_file |
replace_file_content, multi_replace_file_content |
Methodically apply wiki updates with the tools for your vessel. Prefer small, surgical edits over whole-file rewrites when updating existing pages.
1---2name: aim-memory-wiki3description: Interactive active-memory ingestion skill for maintaining a persistent, compounding LLM knowledge base (the Memory Wiki).4---56# `aim-memory-wiki`78> **MANDATE:** You are the active agent in a session, and the user has activated the `aim-memory-wiki` skill. Your objective is to process the recent session context, extract key discoveries, code decisions, and milestones, and incrementally update the persistent knowledge base located in `memory-wiki/`.910## 1. THE CORE PHILOSOPHY11The wiki is a **persistent, compounding artifact** — a structured, interlinked collection of markdown files. It sits between the user and raw data. You do not just index data for retrieval; you read it, extract key information, and *integrate it into the existing wiki* (updating entity pages, revising topic summaries, noting where new data contradicts old claims). 12**The wiki keeps getting richer with every source you add and every session you summarize.**1314## 2. BOOTSTRAPPING (IF EMPTY)15If `memory-wiki/` does not exist or is completely empty (no `index.md` or `log.md`), you must scaffold it:161. Create `memory-wiki/index.md` with a `# Project Wiki Index` header and basic placeholder sections (e.g., `## Core Concepts`, `## Architecture`).172. Create `memory-wiki/log.md` with a `# Memory Log` header to track chronological ingestion events.183. Create the `memory-wiki/pages/` directory to house individual detailed markdown files.1920## 3. THE THREE LAYERS211. **Raw Sources:** External files, chat history, or code that you read but do not modify.222. **The Wiki:** A directory of LLM-generated markdown files (`memory-wiki/`). You own this layer entirely. You create pages, update them, maintain cross-references, and keep everything consistent.233. **The Schema:** Rules and configurations (like `AGENTS.md`) that guide how you act. 2425## 4. GITOPS WORKFLOW (MANDATORY)26Because you are updating the persistent architecture of the repository, you MUST follow strict GitOps procedures. Do not commit wiki updates directly to the `main` branch.271. **Open an Issue:** Track the wiki documentation updates via a formal issue ticket (e.g., using `gh issue create` or `aim bug`).282. **Branch Out:** Spawn a GitOps sandbox (e.g., `aim fix <issue_id>` or standard `git checkout -b fix/...`) to perform your edits safely.293. **Update the Wiki:** Perform all the ingestion, writing, and linting within this isolated branch.304. **Clean up & Promote:** Once the wiki is updated and verified, commit the changes, close the issue, and cleanly merge/promote the branch back to main (e.g., `aim promote`).3132## 5. YOUR OPERATIONS WHEN TRIGGERED33When the user invokes this skill, you must perform an **Ingest** operation synchronously:34351. **Synthesize Context:** Review what was accomplished, decided, or learned in the recent session. Do NOT copy raw transcripts. Extract the tactical takeaways, architectural changes, or deep insights.362. **Update the Index (`memory-wiki/index.md`):** This is the content-oriented catalog. If you create a new page or identify a new core concept, add a link and a one-line summary to `index.md`. Organize it by category (entities, concepts, etc.).373. **Update the Log (`memory-wiki/log.md`):** This is a chronological, append-only record of operations. You MUST append an entry detailing what you ingested.38 - Format: `## [YYYY-MM-DD] ingest | <Title of the update>`39 - Include a brief bulleted summary of what pages were touched.404. **Update/Create Content Pages:** 41 - Open existing relevant pages (e.g., `memory-wiki/pages/architecture.md`) and integrate the new facts. 42 - If a topic is new and complex, create a new file (e.g., `memory-wiki/pages/new_concept.md`) and interlink it with existing pages using standard Markdown links (`[Concept](concept.md)`).43 - Resolve any contradictory stale claims from older versions.4445## 6. LINTING AND CROSS-REFERENCING46Always ensure:47- No orphaned pages exist. If you make a new page, link to it from `index.md` or another relevant page.48- Links are valid relative markdown links.49- Your summaries are precise and dense with signal, free of conversational filler. 5051## 7. EXECUTION52Proceed by explicitly generating your proposed memory updates for the user to review, or immediately begin writing to the `memory-wiki/` directory depending on the user's prompt.5354### Vessel file tools (dual — do not strip either host)5556Use the file tools of the **host CLI you are running in**. Both columns remain valid; never replace one host's tools with the other when editing this skill.5758| Vessel | Read | Create / overwrite | Edit in place |59|--------|------|--------------------|---------------|60| **Grok CLI** | `read_file` | `write` | `search_replace` |61| **AGY / Antigravity** | host read tools | `write_to_file` | `replace_file_content`, `multi_replace_file_content` |6263Methodically apply wiki updates with the tools for your vessel. Prefer small, surgical edits over whole-file rewrites when updating existing pages.
BrianV1981