agentleFS
Sign inStart free
thoitiettxl-cyberthoitiettxl-cyber/Claw-II/skills/cli-patcher/SKILL.md

cli-patcher

Skill2 starsChanged 7 months agoMITView on GitHub

Fix command execution error (command not found) when installing via npx or npm global on Android Root. Automatically create wrapper scripts with absolute paths to bypass symlink and path errors.

  • Installs packages

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use when a post-install command (for example, npx package or npm install -g) returns error sh: command not found or inaccessible or not …

    line 23
  2. Very specific:

    Create an executable file at /data/adb/openclaw/node/bin/<alias> with the content:

    line 31
  3. Very specific:

    Always use an absolute path starting with /data/adb/openclaw/node/bin/node to ensure the command runs in every shell session.

    line 43
  4. Distinctive:

    If input/permissions are missing: report what is missing and clearly request additional information.

    line 60
  5. Distinctive:

    If runtime/tool error: return a brief error + possible cause + suggested fix.

    line 61
  6. Distinctive:

    If there is a risk policy/safety issue: stop and escalate according to the approval checkpoint.

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CLI Patcher

This skill is used to fix common CLI command execution errors on OpenClaw's Android Root environment.

Indexed Reference Map

  • @[SKILL.md#L1-L62] Standard Frontmatter (name, description).
  • @[SKILL.md#L6-L62] CLI Patcher.
  • @[SKILL.md#L10-L62] When to use?.
  • @[SKILL.md#L13-L62] Processing procedure (Manual/Auto).
  • @[SKILL.md#L27-L62] Real-life example.
  • @[SKILL.md#L30-L62] Note.

Supporting files

  • @[scripts/create_wrapper.sh#L1-L19] Execution/automation script for skill.

When should I use it?

Use when a post-install command (for example, npx package or npm install -g) returns error sh: command not found or inaccessible or not found.

SOP

  1. Find the original executable file: Locate the package's .js file in node_modules. For example: /data/adb/openclaw/node/lib/node_modules/<package>/bin/<file>.js
  2. Create Wrapper: Create an executable file at /data/adb/openclaw/node/bin/<alias> with the content:
    #!/data/adb/openclaw/node/bin/node
require('/path/to/file.js');
  3. Grant permission: chmod +x /data/adb/openclaw/node/bin/<alias>

Real-life example

The claw command has been patched to point directly at clawhub/bin/clawdhub.js.

Note

Always use an absolute path starting with /data/adb/openclaw/node/bin/node to ensure the command runs in every shell session.

Trigger Rules

  • Positive: Triggers when the user request matches cli-patcher according to the description: Fix command execution error (command not found) when installing via npx or npm global on Android Root. Automatically create wrapper scripts with absolute paths to bypass symlink and path errors.
  • Negative: Not enabled for requests outside scope or without the workflow/expertise of this skill.
  • Escalation: If there is an external action/network write or sensitive operation, an approval checkpoint must be added before executing.

Output Contract

  • Deliverable: target tracking result of cli-patcher; specify the artifact/path/steps performed (if any).
  • Validation: report PASS/FAIL status and the main checks that were run.
  • Failure mode: when there is an error, the root cause + proposed fix must be stated.

Scope

  • In-scope: tasks match the skill description: Fix command execution error (command not found) when installing via npx or npm global on Android Root. Automatically create wrapper scripts with absolute paths to bypass symlink and path errors.
  • Out-of-scope: request outside the domain or against system policy.

Error Handling

  • If input/permissions are missing: report what is missing and clearly request additional information.
  • If runtime/tool error: return a brief error + possible cause + suggested fix.
  • If there is a risk policy/safety issue: stop and escalate according to the approval checkpoint.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free