vastkitlisted
Install: claude install-skill RazinAleksandr/vastkit
# Vastkit
Use the Vastkit runtime bundled with this plugin as the execution layer. Apply
the workflow and guardrails below; do not install a separate Vastkit package or
recreate Vast.ai API requests in ad hoc scripts.
## Resolve the CLI
Resolve `<skill-dir>` to the directory containing this `SKILL.md`. In Claude
Code, `${CLAUDE_SKILL_DIR}` is that directory. In other agents, use the skill
path shown by the host.
```bash
VK="<skill-dir>/scripts/vastkit-cli"
"$VK" --version
```
The launcher resolves the Python package from the installed plugin. If the
version check reports that the runtime is missing, stop and ask the user to
update or reinstall the plugin through their agent. Do not use `pip` as a
fallback.
Require Python 3.9+, internet access, `ssh`, and `tar`. Prefer `rsync` when
available; Vastkit falls back to tar transfers when the remote image lacks it.
## Protect Credentials
- Use `VAST_API_KEY` or `~/.vast_api_key`. Never put an API key in a command,
pass `--api-key`, print it, commit it, or ask the user to paste it into chat.
- Let Vastkit auto-detect an SSH key, or use `VASTKIT_SSH_KEY`. Never print or
transfer private keys.
- Do not upload `.env` files or credential directories. Vastkit excludes common
environment files by default; add explicit exclusions for any project-specific
secret paths.
- Pass remote secrets only by referencing an already-exported local variable,
for example `--env HF_TOKEN="$HF_TOKEN"`. Never place a literal token in the