ov-layers/skills/llama-cpp/SKILL.md
llama.cpp prebuilt binaries and GGUF conversion tools. Use when working with llama.cpp, GGUF model conversion, or llama-quantize/llama-cli.
npx skillsauth add overthinkos/overthink-plugins llama-cppInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
| Property | Value |
|----------|-------|
| Dependencies | None |
| Ports | — |
| Service | — |
| Install files | layer.yml, tasks: |
Downloads the latest llama.cpp release from GitHub into ~/llama.cpp:
Binaries: llama-quantize, llama-cli, shared libraries (lib*.so*)
Python tools: convert_hf_to_gguf.py, gguf-py package (from source tarball)
| Variable | Value | Purpose |
|----------|-------|---------|
| LLAMA_CPP_PATH | ~/llama.cpp | Location of llama.cpp binaries |
| PATH (appended) | ~/llama.cpp | Makes llama-quantize/llama-cli available |
This layer has no pixi.toml and no depends. It downloads prebuilt binaries and sets environment variables. It is designed to be composed into environment-owning layers (Tier 2) via the layers: field.
The user-phase tasks run after the pixi environment is established by the parent layer. The gguf Python package (for programmatic GGUF access) is declared in the parent layer's pixi.toml, not here.
/ov-layers:python-ml — via layers: [llama-cpp]/ov-layers:jupyter-ml — via layers: [llama-cpp, unsloth]/ov-layers:unsloth-studio — via layers: [llama-cpp, unsloth]/ov-layers:unsloth — Fine-tuning (depends on llama.cpp for GGUF conversion)/ov-images:python-ml (via python-ml metalayer)/ov-images:immich-ml (via python-ml metalayer)/ov-images:jupyter-ml (via jupyter-ml metalayer)/ov-images:jupyter-ml-notebook (via jupyter-ml metalayer)/ov-images:unsloth-studio (via unsloth-studio metalayer)Use when the user asks about:
LLAMA_CPP_PATH environment variable/ov:layer — layer authoring reference (layer.yml schema, task verbs, service declarations)/ov:test — declarative testing (tests: block, ov image test, ov test)development
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.