← Back to Skills Marketplace
76
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install memguard
Description
Memory leak & resource management scanner -- detects unclosed handles, event listener leaks, circular references, unbounded caches, missing cleanup, dangling...
Usage Guidance
This skill appears to do what it says: a local, regex-based memory/resource leak scanner implemented in bash with optional paid features gated by a MEMGUARD_LICENSE_KEY. Before installing:
- Confirm the MEMGUARD_LICENSE_KEY placement you intend to use (env var or ~/.openclaw/openclaw.json). The registry metadata omitted required env/config entries that the scripts actually read; verify the key is stored where you expect.
- Installing hooks will modify your repository's lefthook.yml and call lefthook install; review the hook snippet (it sources the skill scripts from $HOME/.openclaw/skills/memguard by default) — ensure that directory contains the genuine memguard scripts and is from a trusted source, since the pre-commit hook will source and run them on every commit.
- The installer uses brew to install lefthook, which is standard; no remote code downloads are embedded in the skill files themselves.
- If you require absolute confidence in no external communication, inspect the skill scripts for any network-related commands (none were found) and validate that your environment tooling (bash, git, python/node/jq if present) behaves as expected.
Overall: coherent and matching its stated purpose, with minor metadata mismatches and the usual cautions around installing project hooks and storing license keys.
Capability Analysis
Type: OpenClaw Skill
Name: memguard
Version: 1.0.0
MemGuard is a legitimate resource management and memory leak scanner that operates entirely locally. The skill uses regex-based pattern matching (defined in scripts/patterns.sh) to identify potential leaks in various languages and provides integration with git hooks via lefthook (scripts/memguard.sh). The license validation logic in scripts/license.sh is performed offline using JWT decoding, and there is no evidence of data exfiltration, malicious execution, or unauthorized persistence mechanisms.
Capability Assessment
Purpose & Capability
Name/description match the provided scripts: bash-based pattern scanner, pre-commit hook integration via lefthook, report/CI/watch modes. Required binaries (git, bash) and the lefthook brew install are appropriate for the stated functionality.
Instruction Scope
Runtime instructions and scripts operate locally (discover files, run grep-based patterns, generate markdown). Hooks source the skill's scripts from a local skill directory (default $HOME/.openclaw/skills/memguard) and install lefthook into the repo; this modifies repo config (expected for hook installation). The analyzer reads ~/.openclaw/openclaw.json for optional config/license values — that config path is used at runtime but was not listed in the registry's 'required config paths' field (incoherence in metadata). No network calls or telemetry are present in the scripts.
Install Mechanism
Install spec is a single brew formula (lefthook) to provide git-hook functionality — a low-risk, well-known package source. The skill itself is provided as included bash scripts (no remote download during install), and there are no downloads from untrusted URLs recorded.
Credentials
The skill declares MEMGUARD_LICENSE_KEY as the primary credential (used only for pro/team features) which is appropriate. However, registry metadata listed 'Required env vars: none' while SKILL.md and scripts reference MEMGUARD_LICENSE_KEY and also read ~/.openclaw/openclaw.json (which may contain apiKey). This mismatch between declared required env/config and actual script behavior is an inconsistency to be aware of.
Persistence & Privilege
always:false and model invocation allowed (default). Hook installation alters project lefthook.yml and runs lefthook install in the repo (expected for a pre-commit scanner). The skill does not request system-wide persistent privileges beyond installing/using lefthook and writing to the repo config when hooks are installed.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install memguard - After installation, invoke the skill by name or use
/memguard - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of memguard – a memory leak and resource management scanner for all languages.
- Scans codebases for 90+ memory/resource leak patterns (file handles, event listeners, circular refs, unbounded caches, missing cleanup, dangling timers, etc.)
- Supports JS/TS, Python, Java, Go, Rust, and C#
- Provides CLI commands for scanning, git hook integration, and markdown reporting
- Free tier supports scanning up to 5 files, with advanced watch, CI, and team modes for Pro/Team tiers
- Local-only scanning with zero telemetry
- Integrates with git pre-commit via lefthook (darwin, linux, win32)
Metadata
Frequently Asked Questions
What is memguard?
Memory leak & resource management scanner -- detects unclosed handles, event listener leaks, circular references, unbounded caches, missing cleanup, dangling... It is an AI Agent Skill for Claude Code / OpenClaw, with 76 downloads so far.
How do I install memguard?
Run "/install memguard" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is memguard free?
Yes, memguard is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does memguard support?
memguard is cross-platform and runs anywhere OpenClaw / Claude Code is available (darwin, linux, win32).
Who created memguard?
It is built and maintained by suhteevah (@suhteevah); the current version is v1.0.0.
More Skills