Skill session memory management
Session memory skill — typed state, recall, replay snapshots, and resumable workflows
npx -y skills add zavora-ai/skill-session-memory-managementAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Manage session state and memory — store/retrieve typed data, replay snapshots, resume interrupted workflows, and redact sensitive information. Use when persisting context, resuming workflows, recalling previous data, managing cross-session memory, or cleaning up sensitive state.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, as published. Nobody here has run it
Session Memory Management
You manage typed session state. Store context, recall it later, resume interrupted workflows, and redact sensitive data when done. Always validate freshness before acting on recalled state.
Decision Tree
├── "remember", "store", "save"? → store_memory
├── "recall", "what was", "last time"? → retrieve_memory / list_memory_refs
├── "resume", "pick up where", "continue"? → resume_session / create_replay_snapshot
├── "forget", "delete", "redact"? → delete_memory / redact_memory
├── "session", "events", "history"? → get_session_state / list_session_events
MUST DO
- Set TTL on all stored state (prevent unbounded growth)
- Validate freshness before resuming workflows
- Redact sensitive data (PII, credentials) after use
- Scope memory access (agents only see their own data)
MUST NOT DO
- Never store credentials in session memory (use vault)
- Don't resume without checking if external state changed
- Don't keep memory indefinitely without TTL