glibc-prebuilt-bundle
Skill2 starsChanged 7 months agoMITView on GitHub
Standardize the flow bundle prebuilt glibc into OpenClaw-Module for all runtimes/tools (not just Python): artifact policy, install sequence, standard wrapper, smoke test, rollback.
In this repository47 other files it gives its agents.
- brainstormingSkill
- claude-code-termux-runbookSkill
- cli-patcherSkill
- code-review-workflowSkill
- commit-commandsSkill
- consulting-analysisSkill
- context7-cleanSkill
- data-analysisSkill
- deep-researchSkill
- edit-tool-compat-guardSkill
- env-managerSkill
- executing-plansSkill
- feature-devSkill
- firecrawlSkill
- frontend-designSkill
- gateway-device-pairingSkill
- githubSkill
- gogSkill
- image-generationSkill
- memory-setupSkill
- module-auditorSkill
- module-scaffoldSkill
- openclaw-config-guardianSkill
- openclaw-ollama-runtime-kbSkill
- plugin-cutover-guardianSkill
- plugin-runtime-guardianSkill
- python-env-managerSkill
- self-improving-agentSkill
- simplify-and-hardenSkill
- skill-benchSkill
- skill-creatorSkill
- skill-unificationSkill
- skill-vetterSkill
- socratic-groundingSkill
- subagent-orchestrationSkill
- systematic-debuggingSkill
- tailscale-oauth-bridgeSkill
- termux-packagerSkill
- termux-runnerSkill
- test-driven-developmentSkill
- vercel-deploy-claimableSkill
- verification-before-completionSkill
- video-generationSkill
- workspace-cleanupSkill
- writing-plansSkill
- yt-dlp-ingest-firstSkill
- zero-downtime-cutoverSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 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.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 37
If a skill/tool needs to install a prebuilt runtime running through the glibc loader (node/python/rust/go binary bundle...), the policy + …
- Very specific: line 45
Do not use ad hoc namespaces like .tmp-glibc-*, .tmp-python-*, or target-side .backup-* as the primary workflow contract.
- Very specific: line 46
Do not export LD_LIBRARY_PATH globally.
- Very specific: line 51
Artifact policy: only accept aarch64-unknown-linux-gnu (glibc), reject musl/bionic/false arch.
- Very specific: line 53
Backup-first: always backup target runtime to workspace/.ops/backups/<task-id>/ before replacing.
- Very specific: line 57
Smoke tests: run at least --version + basic functional test.
- Distinctive: line 61
No hardcoding tokens/secrets.
- Very specific: line 62
Do not edit /system, /vendor, /boot.
- Distinctive: line 68
If failed: state short reason + rollback command.
- Distinctive: line 85
If input/permissions are missing: report what is missing and clearly request additional information.
- Distinctive: line 86
If runtime/tool error: brief error return + possible cause + suggested fix.
- Distinctive: line 87
If there is a risk policy/safety: stop and escalate according to approval checkpoint.
≈ “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.
Files
glibc-prebuilt-bundle
This is the canonical skill for any task that embeds prebuilt using glibc-runner into the module.
Indexed Reference Map
- @[SKILL.md#L1-L84] Frontmatter + global standardized scope.
- @[SKILL.md#L10-L84] Rules apply to all tools/runtime.
- @[references/adoption-policy.md#L1-L37] Policy requires adopting this skill when installing prebuilt glibc.
- @[references/bundle-playbook.md#L1-L54] General playbook download/verify/extract/wrapper/smoke/rollback.
- @[references/python-build-standalone.md#L1-L45] Recipe profile cho Python (example profile).
- @[scripts/install_glibc_prebuilt.sh#L1-L101] General installer for prebuilt glibc bundles.
- @[scripts/install_python_glibc_prebuilt.sh#L1-L96] Installer profile Python (specialized wrapper).
- @[scripts/rollback_python_bundle.sh#L1-L37] Rollback nhanh cho Python profile.
KB Mode Notes
- Reading order:
references/INDEX.mdreferences/adoption-policy.mdreferences/bundle-playbook.mdreferences/python-build-standalone.md
- Coverage Matrix:
- adoption policy ->
adoption-policy.md - general install/extract/wrapper/rollback flow ->
bundle-playbook.md - Python-specific example profile ->
python-build-standalone.md
- adoption policy ->
- Portability note:
- This skill is the canonical policy layer for glibc prebuilt bundles; The specific recipe can be changed at runtime, but the safety sequence must remain the same.
Mandatory adoption rule
If a skill/tool needs to install a prebuilt runtime running through the glibc loader (node/python/rust/go binary bundle...), the policy + sequence of this skill must be used.
Hard Rules
- Workspace ops taxonomy is required:
workspace/.ops/staging/<task-id>/cho download/extract candidateworkspace/.ops/backups/<task-id>/cho rollback assetsworkspace/.ops/tmp/<task-id>/cho disposable temp artifactsworkspace/.ops/state/<task-id>/cho manifest/checkpoint
- Do not use ad hoc namespaces like
.tmp-glibc-*,.tmp-python-*, or target-side.backup-*as the primary workflow contract. - Do not export
LD_LIBRARY_PATHglobally. - On an Android module host, if the flow needs a lifecycle action after install, the local contract must be reconciled before restart/status.
SOP (global)
- Precheck: loader exists (
node/lib/glibc/ld-linux-aarch64.so.1). - Artifact policy: only accept
aarch64-unknown-linux-gnu(glibc), reject musl/bionic/false arch. - Integrity: HTTPS + checksum when available.
- Backup-first: always backup target runtime to
workspace/.ops/backups/<task-id>/before replacing. - Extract + normalize: download/extract into
workspace/.ops/staging/<task-id>/so the path runs stably. - Standard wrapper: wrapper calls glibc loader local; do not set
LD_LIBRARY_PATHglobal. - State capture: records manifest/checkpoint to
workspace/.ops/state/<task-id>/. - Smoke tests: run at least
--version+ basic functional test. - Rollback: fails at any verification step => rollback immediately from the recorded backup.
Guardrails
- No hardcoding tokens/secrets.
- Do not edit
/system,/vendor,/boot. - Do not export
LD_LIBRARY_PATHglobally. - Network fetch only when the user requests a prebuilt setup/update.
Output contract
- Report: artifact URL, target dir, wrapper name/path, version smoke-test, backup/staging/state paths, rollback status.
- If failed: state short reason + rollback command.
Trigger Rules
- Positive: Triggers when user request matches
glibc-prebuilt-bundleaccording to description: Standardize flow bundle prebuilt glibc into OpenClaw-Module for all runtime/tools (not just Python): artifact policy, install sequence, standard wrapper, smoke test, rollback. - 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
glibc-prebuilt-bundle; Specify the artifact/path/steps performed (if any). - Validation: reports
PASS/FAILstatus and main checks have been run. - Failure mode: when there is an error, the root cause + proposed fix must be stated.
Scope
- In-scope: tasks that match the skill description: Standardize flow bundle prebuilt glibc into OpenClaw-Module for all runtime/tools (not just Python): artifact policy, install sequence, standard wrapper, smoke test, rollback.
- 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: brief error return + possible cause + suggested fix.
- If there is a risk policy/safety: stop and escalate according to approval checkpoint.
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
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.