managed-model-endpoints
Explain Wisp's current managed-model endpoint boundary and plan a safe integration. Use when the user asks to register, start, stop, tunnel, authenticate, or manage a persistent inference service.
npx skills add xuzhougeng/wisp-science --skill managed-model-endpoints --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Managed model endpoint boundary Wisp does not currently expose an endpoint registry or a service-lifecycle backend. The Agent cannot allocate ports, configure tunnels, read secrets, register health checks, or start and stop a persistent inference service through Python. Do not model service startup as a normal `run_in_context` command: a Run tracks one process lifecycle, while a managed endpoint also needs a durable endpoint identity, health, routing, authentication, restart policy, and ownership. ## Supported path If the user already operates an endpoint outside Wisp and the selected local, WSL, or SSH context can reach it using credentials already configured in that execution environment, load `using-model-endpoint` to run a bounded inference client. Never request or print secret values merely to make the call. Otherwise explain that endpoint registration and service management are not available in this Wisp build. A future implementation should add a typed service or execution-context backend with keyring-backed secret binding, health checks, start/stop/recovery semantics, and auditable invocation Runs.
- Supported path
What does the managed-model-endpoints skill do?
Explain Wisp's current managed-model endpoint boundary and plan a safe integration. Use when the user asks to register, start, stop, tunnel, authenticate, or manage a persistent inference service.
How do I install it?
Run `npx skills add xuzhougeng/wisp-science --skill managed-model-endpoints --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From xuzhougeng/wisp-science, a repository with 895 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.