Update VX provider.toml files to RFC 0018 and RFC 0019 standards.
npx skills add https://github.com/loonghao/vx --skill vx-provider-updater
Please help me install this Agent Skill. Skill: vx-provider-updater Source: https://github.com/loonghao/vx/tree/main/.codebuddy/skills/vx-provider-updater Command: npx skills add https://github.com/loonghao/vx --skill vx-provider-updater
This Skill streamlines the process of updating VX provider configurations to the latest standards, ensuring compatibility and improving the reliability of tool installations.
provider.toml files to include layout configurations for binary and archive downloads, and integrates system package manager fallbacks.license field.provider.toml files to support new download layouts and add package manager fallbacks for tools that lack portable binaries on certain platforms.Use the vx-provider-updater skill to update the provider.toml file for the 'imagemagick' tool.
High-intent search queries and answers about installing and using this skill.
To update provider.toml files for RFC 0018 and RFC 0019, this skill standardizes provider manifests by adding layout definitions for binary and archive downloads, enforcing mandatory license fields, and enabling system package manager fallbacks.
A license field is required in VX provider configurations to conform to RFC 0018 and RFC 0019 standards, which standardize provider manifests for enhanced tool management and mandatory compliance.
You can add system package manager fallbacks to VX provider configurations by updating your provider.toml files to incorporate the layout definitions and fallback mechanisms specified in RFC 0018 and RFC 0019.
The best way to support new download layouts in VX providers is updating provider.toml configurations to include binary and archive download definitions, ensuring full RFC 0018 and 0019 compliance and reliable tool installations.
You need to define binary and archive download layouts in provider.toml when updating VX providers to conform to RFC 0018 and RFC 0019 standards, especially when adding system package manager fallbacks for tools lacking portable binaries.
Yes, vx-provider-updater addresses tools lacking portable binaries on certain platforms by enabling system package manager fallbacks within the provider.toml configuration, ensuring reliable installations across different environments.
phillippelevidadGenerate and update AGENTS.md constraint files for project-specific AI agent rules.
loonghaoGenerate runtime provider code templates and configuration files for vx tools.
aaronbassettAutomate reading, validating, cloning, merging, and generating Sandbox.toml configurations.
fefogarciaAudit JavaScript/TypeScript dependencies for vulnerabilities, outdated packages, and license compliance.