OpenParable
Skip to content
← Back to skills

Skippy Server

DevOps & Security
skippy-server

Skippy Server is an Agent Skill for devops & security published in the Mesh-LLM/mesh-llm repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use this skill when running, configuring, debugging, or embedding skippy-server, binary stage transport, OpenAI frontend integration, activation wire dtype settings, stage configs, lifecycle status, or nonblocking telemetry.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Mesh-LLM/mesh-llm/blob/HEAD/.agents/skills/skippy-server/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/skippy-server, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

skippy-server

Use this skill for skippy serving, embedded runtime lifecycle, and binary stage-to-stage transport.

Current Repo Shape

The mesh integration embeds skippy-server through Rust APIs instead of launching it as mesh's public OpenAI surface. Public OpenAI compatibility belongs in openai-frontend; skippy-server should remain the backend stage runtime.

Important crates:

crates/skippy-server
crates/skippy-protocol
crates/skippy-runtime
crates/mesh-llm/src/inference/skippy

Validation

Run cargo commands serially:

cargo check -p mesh-llm
cargo test -p skippy-server --lib
cargo test -p skippy-protocol --lib
cargo test -p mesh-llm-host-runtime --lib inference::skippy

For lifecycle/status changes, also run:

cargo test -p mesh-llm-host-runtime --lib

Rules

Do not reintroduce standalone kv-server or ngram-pool dependencies into mesh. Keep structured outputs, tools, logprobs, and /v1/responses compatibility in openai-frontend.

Stage status exposed by mesh should be backend-neutral at the API boundary. Backend-specific details can remain in internal skippy structs.