Memory logo

Memory

CommunityPopular
Muuuun
memory

Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects.

Overview

PublisherMuuuun
Repositoryluxas
Skill namememory
Stars
1.2K
Forks
18
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Muuuun on GitHub. Read the source before you install it.

Installation

Install the Memory AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Muuuun/luxas/tree/main/skills/memory
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Muuuun/luxas.git /tmp/luxas
mkdir -p .claude/skills
cp -r /tmp/luxas/skills/memory .claude/skills/memory
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Memory in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Memory on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Memory is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Memory Skill

Access persistent memory that spans across research projects.

You do not need this skill to discover past projects — your system prompt already carries a <past_research> digest (every past project's name, date, notes path, and research question) and <global_memory> (cross-project lessons). This skill is for what comes after discovery: deep-diving a relevant project's notes, recording corrections, and saving insights.

Trust rule

Everything read from a past project is a dated, UNVERIFIED lead — not established fact. Values must re-enter the current project's own evidence chain (reader-distilled literature, this project's experiments) before they appear in report.tex. Honor ## CORRECTIONS sections wherever you find them.

Files

Past project notes (primary source)

The <past_research> digest lists each project's live notes path:

<path>/notes/experiments.md   ← findings, alternatives, limitations, red-team
<path>/notes/literature.md    ← reader-distilled per-paper entries
<path>/notes/memory.md        ← decisions, dead ends, TODOs
<path>/data/papers/           ← downloaded PDFs (check before re-downloading)

~/.sisyphus/projects.json

Project registry (path, name, dates, auto-generated summary, cost). The digest is built from this; read it directly only for projects that fell into the digest's overflow index.

~/.sisyphus/memory.md

Cross-project lessons, injected into every run as <global_memory>. You can read and write it. Keep it SMALL; every entry starts with a provenance tag [project, YYYY-MM]. Tool/method lessons, recurring pitfalls, and cross-domain connections belong here — domain findings and numbers do NOT (they live in the source project's notes and must be re-verified wherever used).

~/.sisyphus/archive//

Auto-archived copies of each project's notes + report.tex, written when a run completes. Fallback when the live project dir is gone.

CORRECTIONS convention

When you find that a past project's notes contain a claim that is wrong, append a ## CORRECTIONS section to that file (live notes and archive copy) stating the false claim, why it is wrong, and the evidence — do not edit the original text. History stays intact; future readers see the refutation next to the claim.

Write mechanics

  • ~/.sisyphus/memory.md and ~/.sisyphus/archive/ are whitelisted for your write/edit tools (read before edit, as usual).
  • Another project's LIVE notes are outside your write/edit scope — append corrections there via bash: cat >> <path>/notes/experiments.md << 'EOF' .... Append-only; never rewrite or delete in another project's tree.

Frequently asked questions

What does the Memory AI skill do?

Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects.

Why use Memory on TypingMind?

Because you install it once and use it with any model. Memory is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Memory in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Muuuun/luxas/tree/main/skills/memory. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Memory?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Memory?

As many as you like. As long as a model supports skills, you can use Memory with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Memory AI skill free?

Yes. It is published on GitHub by Muuuun under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇