SKILLEMALL.ai
GitHub ↗ RU Sign in

DC openclaw-gateway-fd-fix

Fix OpenClaw Gateway "spawn EBADF" / "RPC probe failed" / "EMFILE too many open files" errors caused by file descriptor exhaustion from too many files in workspace. One-click detection and repair for the most common OpenClaw crash issue.

Not recommendedcritical or high security findings · low grade D
modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files · 1 script body ≈ 721 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Fix OpenClaw Gateway "spawn EBADF" / "RPC probe failed" / "EMFILE too many open files" errors caused by file descriptor exhaustion from too many files in…

As a process C 50/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
D
53/100
safety, quality, tests
Safety 60%
36
Quality 40%
78
Run on models
none yet
Process rating
C
50/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 5

  • high Dangerous commands cmd-persistence fix.sh:97
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl bootstrap gui/$(id -u) "$PLIST"
  • high Dangerous commands cmd-persistence SKILL.md:71
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl bootout gui/$(id -u) ~/Library/LaunchAgents/ai.openclaw.gateway.plist
  • high Dangerous commands cmd-persistence SKILL.md:72
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/ai.openclaw.gateway.plist
Medium and low: 2
  • medium Dangerous commands cmd-persistence fix.sh:17
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)
    PLIST="$HOME/Library/LaunchAgents/ai.openclaw.gateway.plist"
    code literal
  • medium Dangerous commands cmd-persistence SKILL.md:56
    Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition)
    Edit `~/Library/LaunchAgents/ai.openclaw.gateway.plist` and add inside the root `<dict>`:
    detector

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 50/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 2 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (python) that frontmatter does not declare
  • 100Steps. 21 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 721 tokens
  • 100Progress reporting. Reports progress

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 3 example trigger phrases
  • +3Description length 237: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 21 items
  • +4Has examples (5 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.