Install
Two skills. auto-context
turns a folder of documents — or a datastore you already run — into governed,
searchable context served over HTTP by skardi-server: hybrid search (vector +
FTS + RRF), defaulting to a local SQLite file the skill creates and owns, or
pointed at Postgres + pgvector, MongoDB, or Lance.
retrieval
teaches the agent to answer questions from a skardi-server you already run.
Both run on every Agent Skills host below. They differ only in where the skill directory goes.
Claude Code installs from the marketplace:
/plugin marketplace add SkardiLabs/skardi-skills
/plugin install auto-context@skardi-skills
/plugin install retrieval@skardi-skills
Every other host installs from a checkout:
git clone https://github.com/SkardiLabs/skardi-skills.git && cd skardi-skills
Codex, Cursor, Pi, dsh and OpenCode all read the cross-tool
~/.agents/skills/ convention, so one copy covers all five:
mkdir -p ~/.agents/skills
cp -r auto-context/skills/auto-context ~/.agents/skills/auto-context
cp -r retrieval/skills/retrieval ~/.agents/skills/retrieval
OpenClaw installs through its own CLI
instead of copying, and Hermes
reads ~/.hermes/skills/:
openclaw skills install ./auto-context/skills/auto-context # add --global for every workspace
mkdir -p ~/.hermes/skills && cp -r auto-context/skills/auto-context ~/.hermes/skills/auto-context
Per-host native directories, project-scoped installs and the Hermes
external_dirs option are covered in the
skardi-skills README.
CLI — pre-built for x86_64/aarch64 Linux and Apple Silicon (Intel Macs:
build from source — the one-liner below has no published artifact there):
curl -fSL "https://github.com/SkardiLabs/skardi/releases/latest/download/skardi-$(uname -m | sed 's/arm64/aarch64/')-$(uname -s | sed 's/Linux/unknown-linux-gnu/' | sed 's/Darwin/apple-darwin/').tar.gz" | tar xz
sudo mv skardi /usr/local/bin/
Server — a Docker image, or a source build (no pre-built binary yet):
git clone https://github.com/SkardiLabs/skardi.git && cd skardi
cargo build --release -p skardi-server --features candle,chunking # local embeddings + chunk(); pure Rust
cargo install --locked --path crates/cli # the CLI, from the same checkout
That gives the retrieval skills what they need — chunk() plus a local
embedding UDF — and builds with cargo alone. (chunking is already a default
server feature; naming it keeps the line correct against older tags.)
--features rag widens that to all four embedding backends, and one of them
— gguf — compiles llama.cpp through cmake, so that build needs cmake and a
C++ toolchain on the machine. Reach for rag when you want gguf, onnx or
remote_embed; otherwise the line above is the cheaper build. Or skip building
altogether and run a published server image that ships the embedding backends
(see Docker & cloud under More).