Best for
- Use when the user asks to register, start, stop, tunnel, authenticate, or manage a persistent inference service.
xuzhougeng/wisp-science/skills/managed-model-endpoints/SKILL.md
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.
Decision brief
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.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/xuzhougeng/wisp-science --skill "skills/managed-model-endpoints"Inspect the Agent Skill "managed-model-endpoints" from https://github.com/xuzhougeng/wisp-science/blob/95d2c13d1665d46a388b5bdc998dcce0d5ec2eee/skills/managed-model-endpoints/SKILL.md at commit 95d2c13d1665d46a388b5bdc998dcce0d5ec2eee. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
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 me…
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 57/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 560 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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.
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.