session-memory

Featured

Save, recall, compare or cross-reference Design System Ops findings across runs in .ds-ops/sessions/. Triggers: save these findings, what did we find last time, compare with last run, what changed since. Not for producing a new audit (run that skill) or a full sweep (full-diagnostic).

Web & Frontend 196 stars 7 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
76
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Session Memory A skill for persisting findings across skill runs so that future skills can compare, correlate, and build on what was previously discovered. **Output type:** Memory file creation and recall. This skill writes structured session files and retrieves previous session data. It does not produce analysis — it provides the memory layer that other skills draw from. --- ## Before you begin: verify references Before doing anything else, confirm that every file listed in this skill's frontmatter `references:` field exists at its relative path from this SKILL.md. If any are missing, stop — the install is incomplete. This usually means a third-party installer (for example `npx skills install`) flattened the skill into a standalone folder and dropped the repo-root `knowledge-notes/` directory this skill depends on. Tell the user to reinstall using a supported method from `1-INSTALL.md` (git clone, or the `.plugin` bundle in Cowork) and to run `verify-install.sh` from the install root to confirm the fix. Only proceed without the references if the user explicitly says to — and if they do, state clearly in your output that it was produced in degraded mode without the pack's reference material. ## Why this exists Every skill in Design System Ops produces findings. But those findings are ephemeral — they exist in the conversation, get summarised, and then vanish. The next time someone runs token-audit, it starts from zero. It cannot tell you whether things got better or ...

Details

Author
murphytrueman
Repository
murphytrueman/design-system-ops
Created
6 months ago
Last Updated
2 days ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

session-audit

End-of-session audit that scans the conversation for corrections, preferences, decisions, and new context that were never saved, then proposes where each belongs in the user's memory files (CLAUDE.md, MEMORY.md, or a memory/ folder). Use whenever the user says "audit this session", "session audit", "what did we miss", "end of session check", or asks to capture what was learned before closing a session. Adapts to whatever memory structure the workspace already has, and proposes a simple one if none exists.

0 Updated 2 months ago
meggiepham06-smile
AI & Automation Solid

save-session

MUST use when user says 'save', 'save session', or explicitly wants to preserve session state. {USER_NAME} does NOT use slash commands; also trigger proactively when significant work has been completed and session context should be persisted. For session endings (bye/done/goodbye), use the session-end skill instead which combines save-session + save-diary.

71 Updated today
faizkhairi
AI & Automation Listed

memo-session-skill

Persistent AI agent memory for coding sessions — cross-session knowledge that survives context window resets. Consolidates session noise into durable facts and routes them via memory routing into MEMORY.md, memory/ HOT/WARM/COLD layers, project wiki, AGENTS.md, skills, and optional portfolio memory — git-tracked, with conflict gate and temperature limits. Stateful handoff when volatile chat context is lost; complements vector RAG or managed memory platforms, does not replace them. Use when the user says "wrap up the session", "save what we learned", "handoff", "open loops", "update memory", "agent memory", "persistent memory", "cross-session persistence", "how to give my agent memory", or when another skill requests a memory checkpoint. Also for portfolio/global memory, bootstrap project memory, session changelog, `/inbox`, process inbox, or ingest files from memory/inbox. When memo-session-mcp is connected, use search_all for portfolio/project lookup and reindex_changed after writes. Prefer after non-trivial

2 Updated 2 weeks ago
shenwell