Latest release: v1.0.0Download zip
Capabilities
Compatibility
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The hook's name/description match the included files and handler.ts implementation. All required metadata (events, required config workspace.dir) are present and used as expected. There are no extra credentials, binaries, or unrelated capabilities requested.
Instruction Scope
The runtime instructions and handler only read/write files under the workspace (memory/*.md and workspace/MEMORY.md) and mutate the bootstrapFiles array. There are no network calls, no access to unrelated system paths, and no instructions to collect or transmit data outside the workspace. It explicitly states it does not store secrets.
Install Mechanism
No install spec is embedded in the registry entry (instruction-only). README/INSTALL recommend installing the plugin archive via OpenClaw; that is a normal distribution method for hooks. No downloads from arbitrary URLs or extract operations are present in the package metadata. The repository includes the hook source (handler.ts), which will be installed as part of the plugin—this is expected.
Credentials
The skill requests no environment variables, no credentials, and its HOOK.md/openclaw.plugin.json declare only a workspace.dir config requirement, which the handler uses. There are no secret-like env names or unrelated credential requests.
Persistence & Privilege
always is false and the hook only registers for the agent:bootstrap event. It does not modify other skills or global agent configuration. Its persistent effect is limited to adding MEMORY.md into bootstrapFiles for sessions in the workspace.
Assessment
This hook appears to do what it says: it will create/ensure memory/*.md files and write a workspace-level MEMORY.md, then add that file to the agent bootstrap context. Before installing, confirm that (1) the workspace.dir referenced is the intended workspace, (2) the memory files do not contain any secrets you don't want visible to the agent (anything added to MEMORY.md becomes part of bootstrap context), and (3) you trust the plugin source. If you want extra assurance, inspect handler.ts locally (it is short and readable) before enabling the hook. Otherwise it is low-risk and scoped to the workspace files only.Verification
Tags
Solana Deploy Memory Hook Pack
This OpenClaw hook pack rebuilds a workspace MEMORY.md file from the Solana deployment memory files and injects it during agent bootstrap.
What it does
- Watches the
agent:bootstraplifecycle event - Ensures deployment memory files exist under
memory/ - Generates a root-level
MEMORY.mdsummary from those files - Pushes
MEMORY.mdinto bootstrap context so the agent sees prior deployment lessons at the start of the session
Expected workspace files
This hook is designed to work with the companion skill package:
memory/deploy-history.mdmemory/error-catalog.mdmemory/version-decisions.mdmemory/project-notes.md
Install
openclaw plugins install ./solana-deploy-memory-hook.zip
openclaw hooks list
openclaw hooks enable solana-deploy-memory-bootstrap
# restart the gateway after enabling
OpenClaw discovers hook folders that contain HOOK.md and handler.ts, and workspace hooks must be enabled before they load. The agent:bootstrap hook can modify the bootstrap file list, and MEMORY.md is one of the recognized bootstrap basenames.
Notes
- This is operational memory, not semantic memory.
- It does not store secrets.
- It is safe to pair with the
solana_deploy_engineerskill.