agentleFS
Sign inStart free
thoitiettxl-cyberthoitiettxl-cyber/Claw-II/skills/env-manager/SKILL.md

env-manager

Skill2 starsChanged 7 months agoMITView on GitHub

Manage and look up Android Root environment parameters for OpenClaw-Module glibc-runner; standardize binary paths, wrapper discipline, service debug, and execution safety.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 5 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look up env/runtime facts (paths, wrappers, service, logs).

    line 22
  2. Very specific:

    Do not export LD_LIBRARY_PATH globally in the shell/service profile.

    line 30
  3. Very specific:

    Only set the linker path according to the process (wrapper calls ld-linux-aarch64.so.1 --library-path ...).

    line 31
  4. Very specific:

    Use openclaw.service to start/stop/restart/status/log.

    line 33
  5. Very specific:

    Check openclaw.log, runs.log, pidfile, and wrapper integrity before concluding.

    line 37
  6. Very specific:

    Verify wrapper targets (node, openclaw, python, pip).

    line 40
  7. Very specific:

    Verify loader exists: /data/adb/openclaw/node/lib/glibc/ld-linux-aarch64.so.1.

    line 41
  8. Very specific:

    Verify core runtime vars (PATH, NODE_PATH, HOME, TMPDIR).

    line 42
  9. Very specific:

    If prebuilt/newly installed runtime fails: apply rollback according to skill glibc-prebuilt-bundle.

    line 44
  10. Distinctive:

    Check the results, state validation and next steps.

    line 59
  11. Distinctive:

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

    line 62
  12. Distinctive:

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

    line 63
  13. Distinctive:

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

    line 64

≈ “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

Environment Manager

This skill is the environmental rulebook for the current glibc-runner runtime.

Indexed Reference Map

  • @[SKILL.md#L1-L64] Frontmatter + compatibility.
  • @[SKILL.md#L10-L64] Scope + usage guidelines.
  • @[references/environment.md#L1-L82] Environmental baseline, paths, wrappers, debug checklist.
  • @[../glibc-prebuilt-bundle/SKILL.md#L1-L63] Canonical policy for all prebuilt bundles using glibc-runner.

Scope

  • Look up env/runtime facts (paths, wrappers, service, logs).
  • Diagnose runtime errors due to path/linker/wrapper.
  • Standardize the way to run binaries in modules according to the glibc-runner principle.

Usage Guidelines (mandatory)

  1. Binary paths first
    • Priority wrapper at /data/adb/openclaw/node/bin/* (openclaw, node, python, pip).
  2. No global LD_LIBRARY_PATH
    • Do not export LD_LIBRARY_PATH globally in the shell/service profile.
    • Only set the linker path according to the process (wrapper calls ld-linux-aarch64.so.1 --library-path ...).
  3. Service control
    • Use openclaw.service to start/stop/restart/status/log.
  4. Prebuilt bundle policy
    • Any prebuilt runtime/tool ​​running through the glibc loader must follow the glibc-prebuilt-bundle skill.
  5. Log-first debugging
    • Check openclaw.log, runs.log, pidfile, and wrapper integrity before concluding.

Debugging Checklist

  1. Verify wrapper targets (node, openclaw, python, pip).
  2. Verify loader exists: /data/adb/openclaw/node/lib/glibc/ld-linux-aarch64.so.1.
  3. Verify core runtime vars (PATH, NODE_PATH, HOME, TMPDIR).
  4. View realtime service logs using openclaw.service log openclaw.
  5. If prebuilt/newly installed runtime fails: apply rollback according to skill glibc-prebuilt-bundle.

Trigger Rules

  • Positive: Triggers when user request matches env-manager according to description: Manage and look up Android Root environment parameters for OpenClaw-Module glibc-runner; standardize binary paths, wrapper discipline, service debug, and execution safety.
  • 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 env-manager; Specify the artifact/path/steps performed (if any).
  • Validation: reports PASS/FAIL status and main checks have been run.
  • Failure mode: when there is an error, the root cause + proposed fix must be stated.

SOP

  1. Determine whether the request is within the scope of the skill or not.
  2. Execute the skill's main workflow/instructions in a safe order.
  3. Check the results, state validation and next steps.

Error Handling

  • If input/permissions are missing: report what is missing and clearly request additional information.
  • If runtime/tool ​​error: brief error return + possible cause + suggested fix.
  • If there is a risk policy/safety: stop and escalate according to 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