← Back to Skills Marketplace
Vultr
by
happytreees
· GitHub ↗
· v1.3.0
· MIT-0
366
Downloads
1
Stars
0
Active Installs
6
Versions
Install in OpenClaw
/install vultr
Description
Manage Vultr cloud infrastructure including VPS instances, bare metal, Kubernetes clusters, databases, DNS, firewalls, VPCs, object storage, and more. Use wh...
Usage Guidance
This skill is a full Vultr API client and mostly coherent, but the manifest omits the fact that it needs your Vultr API key stored at ~/.config/vultr/api_key. Before installing: (1) verify the script contents yourself (scripts/vultr.py) to confirm it only talks to api.vultr.com; (2) create an API key with the minimum permissions required and store it with tight file permissions (chmod 600); (3) consider using a dedicated, limited-scope API key rather than a broad account key; (4) if you need stronger assurance, run the skill in an isolated environment or container. The metadata omission is likely an oversight but you should confirm the credential storage and usage before trusting the skill with sensitive keys.
Capability Analysis
Type: OpenClaw Skill
Name: vultr
Version: 1.3.0
The vultr skill bundle is a comprehensive and well-structured CLI client for the Vultr API v2, designed to manage cloud infrastructure. The Python script (scripts/vultr.py) uses standard libraries to interact with the official Vultr API and follows secure practices by reading the API key from a local configuration file (~/.config/vultr/api_key) with recommended restricted permissions. No evidence of data exfiltration, malicious execution, or prompt injection was found; the tool's broad capabilities are consistent with its stated purpose of infrastructure management.
Capability Assessment
Purpose & Capability
The name, description, SKILL.md, reference doc, and scripts/vultr.py are consistent: this is a comprehensive Vultr API client covering instances, kubernetes, DNS, firewalls, object storage, etc. However, the registry metadata lists no required credentials or primary credential while the SKILL.md and script explicitly require an API key stored at ~/.config/vultr/api_key. That metadata omission is an inconsistency (likely an oversight) but not proof of malicious intent.
Instruction Scope
The runtime instructions are narrowly scoped to interacting with the Vultr API and to storing/reading the API key from the user's home config path. The SKILL.md does not instruct the agent to read unrelated files, call external endpoints other than api.vultr.com, or exfiltrate data. The script constructs HTTP requests to the Vultr API and handles responses.
Install Mechanism
There is no install spec (instruction-only skill with included script). No downloads from arbitrary URLs, no package installs, and nothing is written to disk by an installer. The included script will be executed by the agent when invoked, which is expected for a code-backed skill.
Credentials
The skill requires an API key (SKILL.md and scripts/vultr.py instruct storing it at ~/.config/vultr/api_key), but the registry metadata declares no required env vars or primary credential. Requiring an API key is reasonable for a cloud-management skill, but the manifest should explicitly declare that credential. Also note the script reads a file in the user's home directory — ensure you understand which key is stored there and limit its permissions and scope.
Persistence & Privilege
The skill does not request always: true and does not attempt to modify other skills or system-wide agent settings. Its recommended configuration is to store an API key in a dedicated config file (~/.config/vultr/api_key), which is scoped to the skill.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install vultr - After installation, invoke the skill by name or use
/vultr - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.0
Removed env var metadata - skill only uses file-based auth (~/.config/vultr/api_key). Matches DigitalOcean pattern exactly.
v1.2.1
Added credential metadata declaration (requires.env: VULTR_API_KEY) to fix security scan warning about undeclared credentials.
v1.2.0
Security hardening: Removed all env var and CLI arg auth methods. API key MUST be stored in ~/.config/vultr/api_key (matches DigitalOcean pattern).
v1.1.0
Security: API key now stored in config file (~/.config/vultr/api_key) instead of env var. Falls back to VULTR_API_KEY env var or --api-key flag.
v1.0.1
Initial release
v1.0.0
Initial release - Vultr cloud infrastructure management skill
Metadata
Frequently Asked Questions
What is Vultr?
Manage Vultr cloud infrastructure including VPS instances, bare metal, Kubernetes clusters, databases, DNS, firewalls, VPCs, object storage, and more. Use wh... It is an AI Agent Skill for Claude Code / OpenClaw, with 366 downloads so far.
How do I install Vultr?
Run "/install vultr" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Vultr free?
Yes, Vultr is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Vultr support?
Vultr is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Vultr?
It is built and maintained by happytreees (@happytreees); the current version is v1.3.0.
More Skills