Source profileQuality 57/100

xuzhougeng/wisp-science/skills/managed-model-endpoints/SKILL.md

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.

Source repository stars
560
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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.

Best for

  • Use when the user asks to register, start, stop, tunnel, authenticate, or manage a persistent inference service.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/xuzhougeng/wisp-science --skill "skills/managed-model-endpoints"
Safe inspection promptEditorial

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

What the source asks the agent to do

  1. 01

    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 me…

    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 bound…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 bindin…

Permission review

Static risk signals and limitations

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

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score57/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars560SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
xuzhougeng/wisp-science
Skill path
skills/managed-model-endpoints/SKILL.md
Commit
95d2c13d1665d46a388b5bdc998dcce0d5ec2eee
License
AGPL-3.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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.