Vx Best Practices

Best practices for using vx effectively. Use when following recommended patterns for tool management, project setup, and team workflows with vx.

This skill is a documentation-only guide for vx and appears internally consistent. Before acting on any suggested commands: (1) review and understand commands like 'vx install', 'git commit', and 'vx setup' — don't run them blindly; (2) verify the third-party GitHub Action example (loonghao/vx@main) and prefer pinning to a specific release or commit to reduce supply-chain risk; (3) never paste real secrets into example files shown here — follow your usual secrets management practices; and (4) if you don't use vx in your projects, this skill is not needed. If you want a deeper check, provide the source of the referenced vx tooling or your repository so I can flag any risky commands or unpinned external dependencies.

Type: OpenClaw Skill Name: vx-best-practices Version: 1.0.1 The skill bundle consists of documentation and best practices for the 'vx' tool management system. The SKILL.md file provides comprehensive guidance on project setup, security practices (such as checksum verification and auditing), and AI agent integration without any evidence of malicious intent, data exfiltration, or harmful instructions.