← Back to Skills Marketplace
sdsds222

Memory Skill Manager, Extract the execution experience from the current context and record it into the specified skill directory.

by sdsds222 · GitHub ↗ · v1.0.3 · MIT-0
cross-platform ⚠ suspicious
97
Downloads
0
Stars
0
Active Installs
4
Versions
Install in OpenClaw
/install memory-skill-manager
Description
Responsible for maintaining SKILLMEMORY.md in the target skill directory, recording the three most recent execution pipeline JSONs, and modifying the descrip...
Usage Guidance
What to consider before installing or running this skill: - Review and understand the skills root: the script's sandbox allows it to roam between skill directories under the skills root. Confirm where the skill bundle will be installed so you know which directories are in scope. - Backup targets: before running, back up SKILL.md files for any skills that might be targeted — the script will append text to other skills' SKILL.md and write SKILLMEMORY.md files. - Enforce the approval gate: SKILL.md instructs the agent to ask the user before writing, but the script itself does not enforce an interactive authorization step. Ensure your agent actually prompts and requires explicit 'Yes' before invoking the script, or modify the script to require interactive confirmation. - Verify runtime and provenance: the bundle includes manage_memory.js which requires Node. Confirm Node is available and audit the JS file yourself (it is included). Consider running in an isolated sandbox first. - Evaluate sanitization adequacy: the script's redaction uses heuristics that can miss secret formats. If you will feed any sensitive environment or command output into this skill, prefer additional manual review/sanitization or avoid passing secrets via the command line. - Least privilege: if you intend to use this, restrict the target path to a single explicit skill directory rather than allowing broad roaming. Prefer modifications that scope writes to the skill that owns the memory rather than arbitrary other skill directories. If you want a safer posture, ask the author to: (1) declare Node as a required binary, (2) implement an enforceable interactive confirmation inside manage_memory.js, and (3) narrow the sandbox so the script can only write to a single explicitly authorized skill directory. If you cannot obtain those changes, treat the skill as potentially risky and test in an isolated environment.
Capability Assessment
Purpose & Capability
The code and instructions match the declared purpose (record three most recent execution JSONs and append an 'awakening' note to a target SKILL.md). However, the manifest claims 'instruction-only' with no required binaries, while runtime requires node to run manage_memory.js. Also the skill is designed to operate across other skill directories (it intentionally 'roams' skill directories), which is a powerful capability that should be justified to the user.
Instruction Scope
SKILL.md instructs the agent to extract session context and target skill folder and mandates asking the user for approval before writing. That user-approval gate is a procedural control (not enforced by the script) — if an agent ignores the instruction or is run autonomously, the script will still perform writes. The instructions also require collecting environment fingerprints; although they forbid absolute paths/usernames/env var contents, they still require reading environment/tool info which could leak contextual details if sanitization fails.
Install Mechanism
No install spec (instruction-only) is the lowest install risk, but a code file (manage_memory.js) is included and intended to be executed with node. The skill manifest does not list Node or any runtime requirement, which is an incoherence (the agent will need 'node' on PATH to run the provided script). There is no download/install step; code will be executed from the skill bundle.
Credentials
The skill requests no environment variables or credentials in the manifest, and the script includes multiple sanitization attempts (redacting sk-* keys, Bearer tokens, key=value patterns). This is proportionate to recording execution traces. However, the regex sanitization is heuristic (may miss many secret formats) and the SKILL.md relies on the agent to scrub secrets before passing arguments. That split of responsibility increases risk of accidental secret capture/exfiltration.
Persistence & Privilege
The script writes SKILLMEMORY.md and appends a fixed 'AWAKEN' block to the target SKILL.md. This modifies other skills' instruction files and therefore can change how other skills behave. The skill does not require 'always: true', but it still has the ability to persistently modify other skills, which is a high-impact capability and should be strictly controlled (explicit user consent, narrow target path validation, audit logs).
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install memory-skill-manager
  3. After installation, invoke the skill by name or use /memory-skill-manager
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
No changes detected in this version. - No file changes were made from the previous version. - Functionality and documentation remain the same as the previous release.
v1.0.2
Version 1.0.2 of memory-skill-manager - No file changes detected in this release. - No updates to documentation or code. - Behavior remains consistent with previous version.
v1.0.1
Small but important security and UX improvements: - Added mandatory data sanitization to remove sensitive info (API keys, passwords, tokens) from execution records. - Introduced security restrictions: do not record absolute file paths, real usernames, environment variable content, or detailed permission configurations. - Implemented a required user authorization step: users must explicitly approve before any memory is written or updated. - Clarified process and strengthened safety prompts in the documentation.
v1.0.0
The first upload.
Metadata
Slug memory-skill-manager
Version 1.0.3
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 4
Frequently Asked Questions

What is Memory Skill Manager, Extract the execution experience from the current context and record it into the specified skill directory.?

Responsible for maintaining SKILLMEMORY.md in the target skill directory, recording the three most recent execution pipeline JSONs, and modifying the descrip... It is an AI Agent Skill for Claude Code / OpenClaw, with 97 downloads so far.

How do I install Memory Skill Manager, Extract the execution experience from the current context and record it into the specified skill directory.?

Run "/install memory-skill-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Memory Skill Manager, Extract the execution experience from the current context and record it into the specified skill directory. free?

Yes, Memory Skill Manager, Extract the execution experience from the current context and record it into the specified skill directory. is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Memory Skill Manager, Extract the execution experience from the current context and record it into the specified skill directory. support?

Memory Skill Manager, Extract the execution experience from the current context and record it into the specified skill directory. is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Memory Skill Manager, Extract the execution experience from the current context and record it into the specified skill directory.?

It is built and maintained by sdsds222 (@sdsds222); the current version is v1.0.3.

💬 Comments