/memory
Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects.
$ npx -y skills add Muuuun/luxas --skill memory --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/memory
Context preview
The summary Claude sees to decide when to auto-load this skill.
Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights across all Luxas research projects.
SKILL.md
memory.SKILL.mdname: memory
description: Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights 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) 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/<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/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.
Read more
name: memory description: Cross-project research memory. Deep-dive past projects' notes, record corrections, and save cross-project insights 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) 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/<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/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.
An autonomous research colleague — from a question to a compiled manuscript, while you sleep.
Repo: Muuuun/luxas
Other skills on luxas.
- /figure
Hybrid figure pipeline (Nano Banana raster + rembg background removal + TikZ vector assembly). Includes a TikZ template library covering quantum circuits (quantikz), Feynman diagrams (tikz-feynman), circuits (circuitikz), molecules (chemfig), 2D/3D plots (pgfplots), energy-level
Open skill - /matplotlib-figures
Publication-quality data plots via matplotlib with venue-specific styles. Use for generating your own figures (timelines, comparison charts, data summaries, heatmaps) that you add to the LaTeX report. Your brain prompt supplies the venue-specific style directory as
Open skill - /narrative
Narrative discipline for research reports — article-type templates (empirical / feasibility / comparison / policy-zh) and the feedback revision protocol that keeps outline, prose, and figures coherent across many feedback rounds.
Open skill - /paper-figures
Extract figures from downloaded papers and include them in survey/review reports. Use when the report covers other groups' work and benefits from their architecture diagrams, experimental plots, or system schematics. Your brain prompt supplies the absolute path to the
Open skill - /qec-construct
Verifier-in-the-loop CONSTRUCTION of quantum error-correcting codes with transversal non-Clifford gates (CCZ/T). Use when the task is to INVENT or improve a code/construction (not merely search a known family). Provides a sound, cheap algebraic verifier (qverify, "QEC's Lean")
Open skill - /review
Write domain-authentic review articles that synthesize rather than stack. Covers 10 scientific domains (physics, chemistry, biology, medicine, mathematics, computer_science, earth_environment, astronomy, economics, materials) with per-domain style guides mined from landmark
Open skill

