agentleFS
the-void-iathe-void-ia/void-box/.claude/skills/test-vm/SKILL.md

test-vm

Skill88 starsChanged 3 months agoApache-2.0View on GitHub

Run a minimal VoidBox VM smoke test locally. Verifies the VM boots and the LLM responds correctly.

  • Pipes a download into a shell
  • Reads credentials
  • Installs packages

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 5 are distinctive, and 10 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    no argument — defaults to ollama phi4-mini

    line 15
  2. Very specific:

    Check for an existing kernel file.

    line 25
  3. Very specific:

    If missing, download it (the script caches the result in target/):

    line 34
  4. Distinctive:

    After downloading, run the check again to confirm and record the path — it is needed in Step 4.

    line 40
  5. Very specific:

    If missing, build it (auto-detects the claude binary on PATH or ~/.local/bin/claude):

    line 48
  6. Very specific:

    Run the check again to confirm.

    line 54
  7. Very specific:

    If not installed: macOS → brew install ollama.

    line 82
  8. Distinctive:

    If not running, start it in the background:

    line 90
  9. Very specific:

    If it was already running: warn the user that Ollama must be listening on 0.0.0.0:11434 (not 127.0.0.1) so the guest VM can reach it …

    line 98
  10. Distinctive:

    If not set, stop and ask the user to export it.

    line 118
  11. Distinctive:

    Check authentication status using the CLI (exits 0 if logged in, 1 if not):

    line 122
  12. Very specific:

    If not authenticated, stop and tell the user to run claude auth login first, then retry.

    line 128
  13. Very specific:

    No manual credential staging is needed — the claude-personal LLM provider discovers OAuth credentials automatically (macOS Keychain / Linux …

    line 130
  14. Distinctive:

    Use the kernel path found in Step 1 and the URL from Step 3 in the commands below.

    line 138
  15. Very specific:

    If success: false or output is missing vm-ok, report the full output for diagnosis.

    line 173

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Runs examples/smoke/smoke.yaml — the agent replies with "vm-ok 2+2=4". No tool use required; any model that generates text will pass. Success is success: true with output containing vm-ok.

All commands run from the repository root.

Usage: /test-vm [ollama [model] | claude | claude-personal]

  • ollama [model] — local Ollama (default model: phi4-mini)
  • claude — Anthropic API key (ANTHROPIC_API_KEY must be set)
  • claude-personal — personal Claude account (macOS: extracted from Keychain; Linux: staged from ~/.claude/)
  • no argument — defaults to ollama phi4-mini

Recommended Ollama models (2–4 GB RAM, reliable with claude-code): phi4-mini, gemma3:4b, llama3.2:3b. Avoid *-coder variants — they don't follow the agentic protocol well.


Step 1 — Prerequisites

Kernel

Check for an existing kernel file. macOS needs an uncompressed kernel (vmlinux-*); Linux can use the host kernel (vmlinuz-*):

ls target/vmlinux-arm64 2>/dev/null \
  || ls target/vmlinux-amd64 2>/dev/null \
  || ls /boot/vmlinuz-$(uname -r) 2>/dev/null \
  || echo "MISSING"

If missing, download it (the script caches the result in target/):

scripts/download_kernel.sh

After downloading, run the check again to confirm and record the path — it is needed in Step 4.

Rootfs

ls target/void-box-rootfs.cpio.gz 2>/dev/null || echo "MISSING"

If missing, build it (auto-detects the claude binary on PATH or ~/.local/bin/claude):

scripts/build_claude_rootfs.sh

Run the check again to confirm. If it still fails, tell the user to set CLAUDE_BIN=/path/to/claude and retry.


Step 2 — Build and sign

cargo build --release --bin voidbox

macOS only — Apple Virtualization.framework requires the entitlement:

codesign --force --sign - --entitlements voidbox.entitlements target/release/voidbox

Step 3 — Provider setup

Ollama

Check Ollama is installed:

which ollama || echo "NOT INSTALLED"

If not installed: macOS → brew install ollama; Linux → curl -fsSL https://ollama.com/install.sh | sh. Stop until installed.

Check Ollama is running and bound to 0.0.0.0 (required so the guest VM can reach it):

curl -sf http://localhost:11434/api/tags > /dev/null && echo "running" || echo "not running"

If not running, start it in the background:

OLLAMA_HOST=0.0.0.0:11434 ollama serve > /tmp/ollama-serve.log 2>&1 &
for i in $(seq 1 10); do curl -sf http://localhost:11434/api/tags > /dev/null && break || sleep 1; done
curl -sf http://localhost:11434/api/tags > /dev/null || { echo "Ollama failed to start:"; cat /tmp/ollama-serve.log; }

If it was already running: warn the user that Ollama must be listening on 0.0.0.0:11434 (not 127.0.0.1) so the guest VM can reach it through the NAT gateway. If unsure, stop Ollama and restart it with OLLAMA_HOST=0.0.0.0:11434 ollama serve.

Check the model is pulled; pull it if not:

ollama list | grep -F "MODEL_NAME" || ollama pull MODEL_NAME

(substitute MODEL_NAME with the actual model, e.g. phi4-mini)

Set the Ollama base URL for use in Step 4:

  • macOS: http://192.168.64.1:11434 (VZ NAT gateway)
  • Linux: http://10.0.2.2:11434 (SLIRP gateway)

Claude (API key)

[ -n "$ANTHROPIC_API_KEY" ] && echo "key set" || echo "MISSING — export ANTHROPIC_API_KEY=sk-ant-..."

If not set, stop and ask the user to export it.

Claude (personal account)

Check authentication status using the CLI (exits 0 if logged in, 1 if not):

claude auth status

If not authenticated, stop and tell the user to run claude auth login first, then retry.

No manual credential staging is needed — the claude-personal LLM provider discovers OAuth credentials automatically (macOS Keychain / Linux ~/.claude/.credentials.json), stages them to a secure temp directory, and mounts them into the guest VM.


Step 4 — Run

Use the kernel path found in Step 1 and the URL from Step 3 in the commands below.

Ollama:

VOIDBOX_LLM_PROVIDER=ollama \
VOIDBOX_LLM_MODEL=<model> \
VOIDBOX_LLM_BASE_URL=<ollama-url> \
VOID_BOX_KERNEL=<kernel-path> \
VOID_BOX_INITRAMFS=target/void-box-rootfs.cpio.gz \
./target/release/voidbox run --file examples/smoke/smoke.yaml

Claude (API key):

VOID_BOX_KERNEL=<kernel-path> \
VOID_BOX_INITRAMFS=target/void-box-rootfs.cpio.gz \
./target/release/voidbox run --file examples/smoke/smoke.yaml

Claude (personal account):

VOIDBOX_LLM_PROVIDER=claude-personal \
VOID_BOX_KERNEL=<kernel-path> \
VOID_BOX_INITRAMFS=target/void-box-rootfs.cpio.gz \
./target/release/voidbox run --file examples/smoke/smoke.yaml

Step 5 — Verify

The run output includes a success: field and an output: section. Check:

  • success: true — the VM ran the agent without error
  • output contains vm-ok — the LLM responded correctly

If success: false or output is missing vm-ok, report the full output for diagnosis.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.