/memory
Cross-project research memory. Deep-dive past projects' notes and record corrections across all Luxas research projects.
Claude Code
$ npx -y skills add Muuuun/luxas --skill memory --agent claude-code
Codex
$ npx skills add Muuuun/luxas --skill memory -a codex -y
Cursor
$ npx skills add Muuuun/luxas --skill memory -a cursor -y
Gemini CLI
$ npx skills add Muuuun/luxas --skill memory -a gemini-cli -y
GitHub Copilot
$ npx skills add Muuuun/luxas --skill memory -a github-copilot -y
OpenCode
$ npx skills add Muuuun/luxas --skill memory -a opencode -y
Windsurf
$ npx skills add Muuuun/luxas --skill memory -a windsurf -y
SKILL.md
memory.SKILL.mdname: memory
description: Cross-project research memory. Deep-dive past projects' notes and record corrections across all Luxas research projects.
compatibility: Always available. No external dependencies.
allowed-tools: read write edit
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). This skill is for what comes after discovery: deep-diving a relevant project's notes and recording corrections.
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/archive/<slug>/
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/archive/` is 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.
Read more
name: memory description: Cross-project research memory. Deep-dive past projects' notes and record corrections across all Luxas research projects. compatibility: Always available. No external dependencies. allowed-tools: read write edit
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). This skill is for what comes after discovery: deep-diving a relevant project's notes and recording corrections.
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/archive/<slug>/
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/archive/` is 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.
An autonomous research agent: from a one-line question to a compiled, reviewed LaTeX report. luxas.im · Gallery · Quick start · How it works · Architecture notes · Contributing Give Luxas a research question in RESEARCH.md.
Other skills on luxas.
More skills from other plugins.
prompt-lookup
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use…
ppt-master
AI-driven presentation workflow for generating editable PPTX decks and slides, reconstructing page visuals, creating reusable…
morph-ppt
Use this skill when the user wants a .pptx with smooth cross-slide animation — PowerPoint Morph transitions, Keynote-style…
frontend-slides
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to…
Questions about memory.
- Which coding agents can use memory?
- memory installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

