# Aim Memory Wiki

> Interactive active-memory ingestion skill for maintaining a persistent, compounding LLM knowledge base (the Memory Wiki).

- Skill: `brianv1981/aim-memory-wiki` (Agent Skill)
- Install (CLI): `npx skillmds@latest add brianv1981/aim-memory-wiki`
- Raw SKILL.md: https://api.skillmd.com/api/skills/brianv1981/aim-memory-wiki/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: BrianV1981 (https://skillmd.com/u/brianv1981)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/brianv1981/aim-memory-wiki

---


# `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:
1. Create `memory-wiki/index.md` with a `# Project Wiki Index` header and basic placeholder sections (e.g., `## Core Concepts`, `## Architecture`).
2. Create `memory-wiki/log.md` with a `# Memory Log` header to track chronological ingestion events.
3. Create the `memory-wiki/pages/` directory to house individual detailed markdown files.

## 3. THE THREE LAYERS
1. **Raw Sources:** External files, chat history, or code that you read but do not modify.
2. **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.
3. **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.
1. **Open an Issue:** Track the wiki documentation updates via a formal issue ticket (e.g., using `gh issue create` or `aim bug`).
2. **Branch Out:** Spawn a GitOps sandbox (e.g., `aim fix <issue_id>` or standard `git checkout -b fix/...`) to perform your edits safely.
3. **Update the Wiki:** Perform all the ingestion, writing, and linting within this isolated branch.
4. **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:

1. **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.
2. **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.).
3. **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.
4. **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.