⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

v1.2.7

mindkeeper

seekcontext@seekcontext⭐ 6 stars· last commit 8mo ago· 1 open issues

Time Machine for Your AI's Brain — version control for agent context files. Use when the user asks about changes in SOUL.md, AGENTS.md, MEMORY.md, or other agent context files; when they want to undo, rollback, or compare versions; or when they need a checkpoint before risky edits.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐ 6 on GitHubGitHub ↗

New / niche

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Mindkeeper Skill

Time Machine for Your AI's Brain — install this skill if you want your AI to inspect history, show diffs, create checkpoints, and guide rollback in natural language.

This skill teaches the AI how to bootstrap and use the mindkeeper-openclaw plugin. It is the easiest way to get the OpenClaw Plugin experience without manually setting everything up first.

Why Use It

  • Guided setup — the AI checks whether the plugin is available and walks through first-use install
  • Safe permissions model — plugin install and Gateway restart always require explicit confirmation
  • Natural-language usage — ask about changes, diffs, rollback, and checkpoints conversationally
  • Rollback guardrails — preview first, confirm second

Install

clawhub install mindkeeper

On first use, the AI checks whether mindkeeper-openclaw is available. If the tools are not ready yet, it should first consider whether Gateway still needs to finish loading or restart before assuming the plugin is missing.

What It Enables

  • Browse history — See what changed in SOUL.md, AGENTS.md, or any tracked file
  • Compare versions — Full unified diff between any two commits
  • Rollback — Restore any file to a previous version with preview + confirmation
  • Named snapshots — Create checkpoints before risky changes
  • LLM commit messages — Available in OpenClaw Plugin mode using your existing OpenClaw model and auth settings

Requirements

  • Node.js >= 22
  • OpenClaw with Gateway running

The mindkeeper-openclaw plugin provides the actual mind_* tools and background watcher. This skill provides the guidance and first-use bootstrap behavior.

In OpenClaw Plugin mode, the AI should prefer the mind_* tools for history, diff, snapshot, and rollback tasks. CLI commands are mainly for setup, troubleshooting, or manual terminal workflows.

If you prefer to install the plugin yourself first:

openclaw plugins install mindkeeper-openclaw
# Then restart your Gateway

Permissions & Why They Are Needed

ActionPurpose
openclaw plugins install mindkeeper-openclawFetches the official plugin and makes the mind_* tools available
Gateway restartLoads the newly installed plugin into the running Gateway

User consent is required before either action runs.

How to Use

  1. Install the skill: clawhub install mindkeeper
  2. Ask your AI in natural language:
    • "What changed in SOUL.md recently?"
    • "Compare my current AGENTS.md to last week's version"
    • "Roll back SOUL.md to yesterday"
    • "Save a checkpoint called 'perfect-personality' before I experiment"

Examples

User saysAI action
"What changed in SOUL.md?"mind_history with a file filter
"Show me the diff from last week"mind_history → find commit → mind_diff
"Undo that change"mind_rollback preview first, then execute after confirmation
"Save a checkpoint before I experiment"mind_snapshot with a descriptive name
"Edit SOUL.md to change my tone"Edit the file directly; mindkeeper should track the change automatically

Troubleshooting

  • History is empty — Call mind_status to check whether mindkeeper is initialized. Make a small edit to a tracked file to trigger the first snapshot.
  • Tools not found — Ensure the mindkeeper-openclaw plugin is installed and Gateway has been restarted. A brand-new /new session can briefly miss the tool context while startup is still finishing.
  • Rollback not applying — After rollback, run /new to reload the session with the restored file.

Links

// HOW IT'S BUILT

// FILES

4 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • packages/openclaw/skills/mindkeeper/SKILL.md8.4 KB141fd1607e88upstream ↗
    ---
    name: mindkeeper
    description: Time Machine for Your AI's Brain — version control for agent context files. Use when the user asks about changes in SOUL.md, AGENTS.md, MEMORY.md, or other agent context files; when they want to undo, rollback, or compare versions; or when they need a checkpoint before risky edits.
    version: 1.2.7
    homepage: https://github.com/seekcontext/mindkeeper
    repository: https://github.com/seekcontext/mindkeeper
    ---
    
    # Mindkeeper — Time Machine for Your AI's Brain
    
    Use mindkeeper tools when the user asks about changes, history, or versions of their agent context files (`AGENTS.md`, `SOUL.md`, `USER.md`, `IDENTITY.md`, `TOOLS.md`, `HEARTBEAT.md`, `MEMORY.md`, `memory/`, `skills/`).
    
    ## Bootstrap (One-time setup)
    
    **When the user enables mindkeeper or asks for mindkeeper capability**, first try `mind_status`. If it fails, do **not** assume the plugin is missing yet. It can also fail when Gateway has not finished loading the plugin, when tools are not exposed to the current session yet, or when the workspace copy of this skill is unavailable.
    
    1. **Diagnose conservatively** — Tell the user: "I can't access the mindkeeper tools yet. The plugin may be missing, Gateway may still need a restart, or the current session may not have loaded the skill/tool context yet." Only say the plugin is definitely missing if the runtime explicitly shows that `mindkeeper-openclaw` is not installed.
    
    2. **If the runtime confirms the plugin is missing and the user confirms**, run this flow:
       - **Install the plugin** — Run via bash:
         ```bash
         openclaw plugins install mindkeeper-openclaw
         ```
       - **Restart Gateway if the runtime supports it** — Use the available runtime mechanism to restart Gateway. If restart is unavailable or fails, tell the user: "Plugin installed. Restart your Gateway manually to apply."
       - **Confirm** — If restart succeeded, tell the user: "Mindkeeper is ready. Restart complete — you can now ask about history, diffs, rollbacks, or snapshots." If restart did not happen, tell the user that the plugin is installed but Gateway must be restarted before the tools will appear.
    
    3. **If the plugin appears installed already** — Tell the user to retry after Gateway finishes loading or after a manual restart. If a workspace copy of the skill appears to be missing, mention that the session may not have loaded the built-in mindkeeper skill correctly yet.
    
    4. **Alternative** — If the user prefers to install manually, tell them: "Run `openclaw plugins install mindkeeper-openclaw` in your terminal, then restart your Gateway. After that, mindkeeper will be ready."
    
    If `mind_status` succeeds, the plugin is already installed; skip the bootstrap and proceed with the user's request.
    
    ## Tool Preference
    
    In OpenClaw Plugin mode, prefer the `mind_*` tools over CLI commands for normal mindkeeper operations.
    
    - Use `mind_status`, `mind_history`, `mind_diff`, `mind_snapshot`, and `mind_rollback` whenever they are available.
    - Do not use `openclaw mind ...` or `mindkeeper ...` for routine history, diff, snapshot, or rollback requests if the plugin tools are available.
    - CLI commands are for one-time setup, troubleshooting, manual user workflows, or when the user explicitly asks for terminal commands.
    
    ## Available Tools
    
    | Tool | Purpose |
    |------|---------|
    | `mind_status` | Show what files are tracked and whether there are unsaved changes |
    | `mind_history` | Browse the change log for one file or all files |
    | `mind_diff` | Compare any two versions of a file side-by-side |
    | `mind_rollback` | Restore a file to a previous version (always preview first) |
    | `mind_snapshot` | Save a named checkpoint before making significant changes |
    
    ## Tracking Scope
    
    Mindkeeper tracks these files by default:
    
    - `AGENTS.md`, `SOUL.md`, `USER.md`, `IDENTITY.md`
    - `TOOLS.md`, `HEARTBEAT.md`, `MEMORY.md`
    - `memory/**/*.md`
    - `skills/**/*.md`
    
    Excluded by default: `BOOTSTRAP.md`, `canvas/**`, `.git/`, `.mindkeeper/`.
    
    ## When to Use
    
    | User says… | Action |
    |-----------|--------|
    | "What changed in SOUL.md?" | `mind_history` with `file: "SOUL.md"` |
    | "Show me the diff from last week" | `mind_history` to find the commit, then `mind_diff` |
    | "Undo that change" / "Roll back AGENTS.md" | Full rollback procedure (see below) |
    | "Save a checkpoint before I experiment" | `mind_snapshot` with a descriptive name |
    | "Is mindkeeper tracking my files?" | `mind_status` |
    | "What does my history look like?" | `mind_history` without a file filter |
    
    ## Direct Edit Requests
    
    If the user asks to directly edit a tracked file such as `SOUL.md`, `AGENTS.md`, or `MEMORY.md`, make the edit directly.
    
    - Do not block on CLI availability.
    - Do not mention unavailable CLI commands unless the user explicitly asked for a CLI-based workflow.
    - Mindkeeper's background watcher should capture the change automatically after the edit.
    - If relevant, you may mention that the change should now be tracked by mindkeeper.
    
    ## Tool Usage Guide
    
    ### mind_status
    Call this first when the user asks about history, tracking state, snapshots, or rollback, or if you're unsure whether mindkeeper is initialized.
    ```
    mind_status → { initialized, workDir, pendingChanges, snapshots }
    ```
    
    You do not need to call `mind_status` before a simple direct edit request unless the user specifically asks about tracking or history.
    
    ### mind_history
    Returns a list of commits with short hash, date, and message.
    - `file` (optional): filter to a specific file path, e.g. `"SOUL.md"`
    - `limit` (optional): number of entries to return (default 10, increase for longer searches)
    
    ```
    mind_history({ file: "SOUL.md", limit: 20 })
    → { count, entries: [{ oid, date, message }] }
    ```
    
    ### mind_diff
    Compares two versions of a file. `from` and `to` are short or full commit hashes from `mind_history`.
    - Omit `to` to compare `from` against the current version (HEAD).
    - **To see what changed in the latest commit**: use `from: entries[1].oid` (the parent) and `to: entries[0].oid` or omit `to` for HEAD. Do NOT use `from: entries[0].oid` with `to: HEAD` — that compares the same commit to itself and yields an empty diff.
    
    ```
    mind_diff({ file: "SOUL.md", from: "a1b2c3d4" })
    → { file, from, to, additions, deletions, unified }
    ```
    
    ### mind_snapshot
    Creates a named checkpoint of the current state of all tracked files. Use before risky changes.
    - `name`: short identifier, e.g. `"stable-v2"` or `"before-experiment"`
    - `message` (optional): longer description
    
    ```
    mind_snapshot({ name: "stable-v2", message: "Personality tuned, rules finalized" })
    → { success, snapshot, commit: { oid, message } }
    ```
    
    ### mind_rollback
    **Always use the two-step procedure.** Never skip the preview.
    
    **Step 1 — Preview:**
    ```
    mind_rollback({ file: "SOUL.md", to: "a1b2c3d4", preview: true })
    → { preview: true, diff: { unified, additions, deletions }, instruction }
    ```
    Show the diff to the user and ask for confirmation.
    
    **Step 2 — Execute (only after user confirms):**
    ```
    mind_rollback({ file: "SOUL.md", to: "a1b2c3d4", preview: false })
    → { preview: false, success: true, commit: { oid, message } }
    ```
    After success, tell the user: **"Run `/new` to apply the changes to your current session."**
    
    ## Important Notes
    
    - **This skill is the guide, the plugin is the engine** — the `mindkeeper-openclaw` plugin provides the actual `mind_*` tools and watcher; this skill teaches the AI how to bootstrap and use them safely
    - **Use plugin tools first** — in OpenClaw Plugin mode, prefer `mind_*` tools over CLI commands for normal operations
    - **Rollback is per-file** — it only restores the specified file, not all files at once
    - **Rollbacks are non-destructive** — every rollback creates a new commit, so it can itself be undone
    - **Auto-snapshots run in the background** — the user doesn't need to manually save; mindkeeper captures every change automatically
    - **LLM commit messages are plugin-only for now** — currently supported only through the OpenClaw plugin; standalone CLI mode falls back to template messages
    - **Named snapshots are the safety net** — encourage users to snapshot before major personality or rule changes
    - **If history is empty** — mindkeeper may not have initialized yet, or no changes have been made since install. Call `mind_status` to check.
    - **Commit hashes** — always use the `oid` field from `mind_history` results. Short 8-character hashes are fine.
    - **Keep user-facing messages focused** — if a task can be completed with file edits or `mind_*` tools, do not distract the user with unavailable CLI details
    
  • packages/openclaw/skills/mindkeeper/README.md3.8 KB91fbabf6bdbfupstream ↗
    # Mindkeeper Skill
    
    **Time Machine for Your AI's Brain** — install this skill if you want your AI to inspect history, show diffs, create checkpoints, and guide rollback in natural language.
    
    This skill teaches the AI how to bootstrap and use the `mindkeeper-openclaw` plugin. It is the easiest way to get the OpenClaw Plugin experience without manually setting everything up first.
    
    ## Why Use It
    
    - **Guided setup** — the AI checks whether the plugin is available and walks through first-use install
    - **Safe permissions model** — plugin install and Gateway restart always require explicit confirmation
    - **Natural-language usage** — ask about changes, diffs, rollback, and checkpoints conversationally
    - **Rollback guardrails** — preview first, confirm second
    
    ## Install
    
    ```bash
    clawhub install mindkeeper
    ```
    
    On first use, the AI checks whether `mindkeeper-openclaw` is available. If the tools are not ready yet, it should first consider whether Gateway still needs to finish loading or restart before assuming the plugin is missing.
    
    ## What It Enables
    
    - **Browse history** — See what changed in `SOUL.md`, `AGENTS.md`, or any tracked file
    - **Compare versions** — Full unified diff between any two commits
    - **Rollback** — Restore any file to a previous version with preview + confirmation
    - **Named snapshots** — Create checkpoints before risky changes
    - **LLM commit messages** — Available in OpenClaw Plugin mode using your existing OpenClaw model and auth settings
    
    ## Requirements
    
    - Node.js >= 22
    - OpenClaw with Gateway running
    
    The `mindkeeper-openclaw` plugin provides the actual `mind_*` tools and background watcher. This skill provides the guidance and first-use bootstrap behavior.
    
    In OpenClaw Plugin mode, the AI should prefer the `mind_*` tools for history, diff, snapshot, and rollback tasks. CLI commands are mainly for setup, troubleshooting, or manual terminal workflows.
    
    If you prefer to install the plugin yourself first:
    
    ```bash
    openclaw plugins install mindkeeper-openclaw
    # Then restart your Gateway
    ```
    
    ## Permissions & Why They Are Needed
    
    | Action | Purpose |
    |--------|---------|
    | `openclaw plugins install mindkeeper-openclaw` | Fetches the official plugin and makes the `mind_*` tools available |
    | Gateway restart | Loads the newly installed plugin into the running Gateway |
    
    **User consent is required** before either action runs.
    
    ## How to Use
    
    1. Install the skill: `clawhub install mindkeeper`
    2. Ask your AI in natural language:
       - "What changed in SOUL.md recently?"
       - "Compare my current AGENTS.md to last week's version"
       - "Roll back SOUL.md to yesterday"
       - "Save a checkpoint called 'perfect-personality' before I experiment"
    
    ## Examples
    
    | User says | AI action |
    |-----------|-----------|
    | "What changed in SOUL.md?" | `mind_history` with a file filter |
    | "Show me the diff from last week" | `mind_history` → find commit → `mind_diff` |
    | "Undo that change" | `mind_rollback` preview first, then execute after confirmation |
    | "Save a checkpoint before I experiment" | `mind_snapshot` with a descriptive name |
    | "Edit SOUL.md to change my tone" | Edit the file directly; mindkeeper should track the change automatically |
    
    ## Troubleshooting
    
    - **History is empty** — Call `mind_status` to check whether mindkeeper is initialized. Make a small edit to a tracked file to trigger the first snapshot.
    - **Tools not found** — Ensure the `mindkeeper-openclaw` plugin is installed and Gateway has been restarted. A brand-new `/new` session can briefly miss the tool context while startup is still finishing.
    - **Rollback not applying** — After rollback, run `/new` to reload the session with the restored file.
    
    ## Links
    
    - [mindkeeper on GitHub](https://github.com/seekcontext/mindkeeper)
    - [mindkeeper-openclaw on npm](https://www.npmjs.com/package/mindkeeper-openclaw)
    
  • packages/openclaw/skills/mindkeeper/clawhub.json1.2 KBf711c27adf8aupstream ↗
    {
      "name": "Mindkeeper",
      "tagline": "Time Machine for Your AI's Brain",
      "description": "Time Machine for Your AI's Brain — install this skill if you want your AI to inspect history, show diffs, create checkpoints, and guide rollback in natural language across agent context files.\n\nSetup: add this skill alone. On first use, the AI checks whether the mindkeeper-openclaw plugin is available. If it is not, the AI asks for explicit confirmation before installing the plugin and before restarting Gateway. User consent is required for plugin install and Gateway restart.\n\nUse this skill when the user asks about changes, history, or versions of their agent context files. The skill teaches the AI how to bootstrap and use the mind_status, mind_history, mind_diff, mind_rollback, and mind_snapshot tools safely.",
      "category": "productivity",
      "tags": ["version-control", "agent", "history", "rollback", "snapshot", "diff", "openclaw"],
      "version": "1.2.6",
      "license": "MIT",
      "pricing": "free",
      "homepage": "https://github.com/seekcontext/mindkeeper",
      "repository": "https://github.com/seekcontext/mindkeeper",
      "support_url": "https://github.com/seekcontext/mindkeeper/issues"
    }
    
  • packages/openclaw/skills/mindkeeper/SCREENSHOT_GUIDELINE.md5.0 KB3edfa12fc695upstream ↗
    # Screenshot Preparation Guideline for ClawHub
    
    This guide walks you through preparing the environment and demo data before taking screenshots for the mindkeeper skill listing on ClawHub.
    
    See [CLAWHUB_PUBLISH.md](../../../../CLAWHUB_PUBLISH.md) for the full publishing workflow.
    
    ## Prerequisites
    
    - **Node.js** ≥ 22
    - **OpenClaw** installed and configured
    - **Gateway** running (e.g. `openclaw start` or desktop app)
    - A **workspace** with agent context files (SOUL.md, AGENTS.md, etc.)
    
    ---
    
    ## Phase 1: Environment Setup
    
    ### 1.1 Install mindkeeper plugin
    
    ```bash
    openclaw plugins install mindkeeper-openclaw
    ```
    
    Restart the Gateway so the plugin loads and the mind_* tools become available.
    
    ### 1.2 Identify your workspace
    
    mindkeeper tracks files in your OpenClaw workspace. Typical locations:
    
    - `~/.openclaw/workspace/` (default)
    - Or the workspace configured in `~/.openclaw/openclaw.json`
    
    Ensure the workspace contains at least:
    
    - `SOUL.md`
    - `AGENTS.md` (optional but helpful)
    
    If these files don't exist, create minimal placeholder content:
    
    ```bash
    # Example: create SOUL.md
    echo "# Agent Personality" > ~/.openclaw/workspace/SOUL.md
    echo "You are a helpful assistant." >> ~/.openclaw/workspace/SOUL.md
    ```
    
    ### 1.3 Verify mindkeeper is running
    
    ```bash
    openclaw mind status
    ```
    
    You should see workspace path, pending changes count, and named snapshots. The plugin uses your configured OpenClaw workspace automatically.
    
    ---
    
    ## Phase 2: Build Demo History
    
    mindkeeper auto-snapshots after changes with a **30-second debounce**. Plan edits with gaps or wait ~30s between edits.
    
    ### 2.1 Create initial history (Day 1 simulation)
    
    **Edit 1** — Add content to SOUL.md:
    
    ```markdown
    # Agent Personality
    
    You are a helpful assistant. You prefer concise answers.
    ```
    
    Save and wait **≥30 seconds** for the auto-snapshot to run (mindkeeper debounces changes).
    
    **Edit 2** — Change SOUL.md:
    
    ```markdown
    # Agent Personality
    
    You are a helpful assistant. You prefer concise answers and use markdown when useful.
    ```
    
    Save and wait **≥30 seconds**.
    
    **Edit 3** — Add more:
    
    ```markdown
    # Agent Personality
    
    You are a helpful assistant. You prefer concise answers and use markdown when useful.
    You avoid being overly verbose.
    ```
    
    Save and wait **≥30 seconds**.
    
    ### 2.2 Create a named snapshot (for Screenshot 3)
    
    ```bash
    openclaw mind snapshot before-experiment
    ```
    
    Or ask the AI: "Save a checkpoint called 'before-experiment' before I make changes."
    
    ### 2.3 Verify history exists
    
    ```bash
    openclaw mind history SOUL.md
    ```
    
    You should see at least 3–4 commits with short hashes (e.g. `a1b2c3d4`). Note one or two hashes for the diff example.
    
    ---
    
    ## Phase 3: Screenshot Checklist
    
    Before taking screenshots, confirm:
    
    - [ ] Gateway is running
    - [ ] mindkeeper plugin is installed and loaded
    - [ ] `openclaw mind status` shows workspace and tracked info
    - [ ] `openclaw mind history SOUL.md` shows at least 3 commits
    - [ ] You have a named snapshot (e.g. `before-experiment`)
    - [ ] Screen resolution is 1920×1080 or 1280×720
    - [ ] UI is clean (close unnecessary panels, hide clutter)
    
    ---
    
    ## Phase 4: Screenshot Order
    
    Take screenshots in this order so the conversation state stays consistent:
    
    | # | Screenshot | User prompt | What to capture |
    |---|------------|-------------|-----------------|
    | 1 | Hero | "What changed in SOUL.md recently?" | User question + AI response with history list |
    | 2 | Diff | "Compare my current SOUL.md to the previous version" or "Show me the diff between SOUL.md now and [paste a hash from history]" | AI response with diff output |
    | 3 | Snapshot | "Save a checkpoint called 'demo-checkpoint'" | AI success message confirming snapshot |
    | 4 | Rollback | "Roll back SOUL.md to the previous version" | AI preview diff + confirmation prompt |
    | 5 | Status | "Is mindkeeper tracking my files?" | AI response with `mind_status` output |
    
    ---
    
    ## Phase 5: Save & Name
    
    Save screenshots as PNG in:
    
    ```
    packages/openclaw/skills/mindkeeper/screenshots/
    ```
    
    Suggested filenames:
    
    - `01-hero-history.png`
    - `02-diff.png`
    - `03-snapshot.png`
    - `04-rollback-preview.png`
    - `05-status.png`
    
    ---
    
    ## Troubleshooting
    
    | Issue | Fix |
    |-------|-----|
    | `mind_status` / tools not found | Restart Gateway after plugin install |
    | History is empty | Make edits, wait 30s between each, or run `openclaw mind snapshot <name>` |
    | "No commits" in diff | Ensure you have at least 2 commits; use `mind_history` to get valid hashes |
    | Diff shows nothing | Use `from` and `to` hashes from `mind_history`; omit `to` to compare to current |
    | Rollback fails | Ensure the target commit exists; use `mind_history` to verify hashes |
    
    ---
    
    ## Quick Reference
    
    ```bash
    # Check status
    openclaw mind status
    
    # View history (get commit hashes for diff/rollback)
    openclaw mind history SOUL.md
    
    # Create named snapshot
    openclaw mind snapshot <name>
    ```
    
    Note: `openclaw mind` only exposes status, history, and snapshot. For diff and rollback, use the AI (mind_diff, mind_rollback tools) or the standalone `mindkeeper` CLI if installed.
    

Plain-text copy, no login: /skill-bundles/seekcontext-mindkeeper-packages-openclaw-skills-mindkeeper.md

// REPO STATS

6 stars
1 open issues
Last commit: 8mo ago