ClawHub

Vx Troubleshooting

v1.0.0

Troubleshooting guide for vx issues. Use when encountering installation failures, version conflicts, PATH issues, or other vx problems.

⭐ 0· 65·1 current·1 all-time
byHal@loonghao
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description ('vx troubleshooting') match the SKILL.md content. All commands and guidance are relevant to diagnosing and fixing vx installation, PATH, version, and runtime issues.
ℹ
Instruction Scope
The instructions are broadly in-scope for troubleshooting but include privileged and potentially destructive operations (sudo, chmod, rm -rf ~/.vx, reinstall, editing PATH) and recommend collecting/printing local files (vx.toml, vx doctor output). These actions are expected for repair guidance but require user caution because they modify local state and may expose local configuration when shared.
✓
Install Mechanism
No install spec and no code files — instruction-only skill; nothing will be written to disk by the skill itself. This is the lowest-risk install profile.
✓
Credentials
No required environment variables, credentials, or config paths declared. The SKILL.md references ~/.vx and vx.toml which are reasonable for a vx troubleshooting guide.
✓
Persistence & Privilege
always is false and the skill does not request elevated platform privileges or persistent presence. It is user-invocable and can be called autonomously (platform default) which is expected for a help/troubleshooting skill.
Assessment
This skill is coherent with its stated purpose, but review any suggested commands before running them. Pay special attention to commands that use sudo, change permissions, or remove files (e.g., rm -rf ~/.vx) — back up ~/.vx and vx.toml first. Diagnostic output (vx doctor, vx.toml, logs) can contain sensitive information, so sanitize before sharing. The skill's source/homepage is unknown and the 'Support Channels' section appears truncated; if you plan to follow links or report issues, confirm official project URLs first. Overall low risk as an instruction-only guide, but exercise standard caution when executing privileged or destructive commands and when sharing diagnostics.

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

latestvk973x0rq9hckj807bgkhdk3z4s848rwe

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments