# Skippy Server

> 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.

- Skill: `mesh-llm/skippy-server` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mesh-llm/skippy-server`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mesh-llm/skippy-server/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Web & Frontend
- Author: mesh-llm (https://skillmd.com/u/mesh-llm)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mesh-llm/skippy-server

---


# 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:

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

## Validation

Run cargo commands serially:

```bash
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:

```bash
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.