ClawHub

Resource Leak

v1.0.0

Files, sockets, subscriptions, or other finite resources are acquired without a guaranteed release path.

⭐ 0· 41·0 current·0 all-time
by@mvogt99

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mvogt99/resource-leak.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Resource Leak" (mvogt99/resource-leak) from ClawHub.
Skill page: https://clawhub.ai/mvogt99/resource-leak
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install resource-leak

ClawHub CLI

Package manager switcher

npx clawhub@latest install resource-leak
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name and description match the SKILL.md content. The skill is purely educational/diagnostic guidance about resource leaks and does not request unrelated binaries, environment variables, or config paths.
✓
Instruction Scope
SKILL.md contains static guidance (symptoms and remediation) and does not instruct the agent to read files, run commands, call external endpoints, or access credentials. It stays within the scope of explaining how to find and fix leaks.
✓
Install Mechanism
No install spec or code files are present; this is instruction-only, so nothing is written to disk or fetched at install time.
✓
Credentials
The skill requires no environment variables, credentials, or config paths — appropriate for a documentation-style guidance skill.
✓
Persistence & Privilege
The skill is not marked always:true and does not request system or cross-skill configuration changes. It poses no elevated persistence or privilege demands.
Assessment
This skill is safe and coherent: it is a text-only guide on identifying and fixing resource leaks and asks for nothing sensitive. If you plan to use an agent to automatically scan your codebase for leaks, make sure the agent runtime is granted file access only to code you want analyzed (and that no credentials or external uploads are unintentionally enabled), because the skill itself does not perform scanning or request access.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

OSmacOS · Linux · Windows
latestvk972bcxbz78z6tjwc65c3812z585kzjb
41downloads
0stars
1versions
Updated 1d ago
v1.0.0
MIT-0
macOS, Linux, Windows
@mvogt99
latest
Download

resource-leak

A resource is opened but not closed. Under low load the process recycles or the OS cleans up on exit, so the bug stays hidden. Under real load, file-descriptor exhaustion, memory bloat, or orphaned connections appear and cascade.

Symptoms

  • open(...) without a matching close() or with block.
  • Database connections or HTTP clients instantiated per-request without pooling or teardown.
  • Event listeners / observers / subscriptions registered but never removed.
  • Background tasks or timers spawned without cancellation paths.
  • Gradual memory growth that correlates with request count.

What to do

  • Pair every acquire with a release. Use language constructs that guarantee teardown: with (Python), using / try-with-resources (C#/Java), defer (Go), try/finally (JS/TS).
  • For resources that outlive a single function, document ownership: who closes it, when, on which code path — including error paths.
  • Prefer pooled clients (HTTP, database) over creating a new one per call.
  • When registering event listeners, return the unregister function in the same scope so the caller can clean up.
  • Test the teardown path. Kill a process or trigger an error mid-operation and confirm resources are released.

Comments

Loading comments...