mcpbeat Sign in

Managed Model Endpoints Agent Skill

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.

350 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
859
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/xuzhougeng/wisp-science --skill managed-model-endpoints

The instruction itself

2 sections, as written by the author

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.

Other skills for the same job

different authors, same section of the catalogue
Skill Creator
by anthropics
vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

56k tokens scripts
Geo Database
by christophacham
×4

Access NCBI GEO for gene expression/genomics data. Search/download microarray and RNA-seq datasets (GSE, GSM, GPL), retrieve SOFT/Matrix files, for transcriptomics and expression analysis.

12k tokens
Pymc Bayesian Modeling
by christophacham
×4

Bayesian modeling with PyMC. Build hierarchical models, MCMC (NUTS), variational inference, LOO/WAIC comparison, posterior checks, for probabilistic programming and inference.

24k tokens scripts
Pymoo
by christophacham
×4

Multi-objective optimization framework. NSGA-II, NSGA-III, MOEA/D, Pareto fronts, constraint handling, benchmarks (ZDT, DTLZ), for engineering design and optimization problems.

19k tokens scripts
Statsmodels
by ComeOnOliver
×4

Statistical modeling toolkit. OLS, GLM, logistic, ARIMA, time series, hypothesis tests, diagnostics, AIC/BIC, for rigorous statistical inference and econometric analysis.

41k tokens
Add Uint Support
by pytorch
vendor ×3

Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.

2k tokens
At Dispatch V2
by pytorch
vendor ×3

Convert PyTorch AT_DISPATCH macros to AT_DISPATCH_V2 format in ATen C++ code. Use when porting AT_DISPATCH_ALL_TYPES_AND*, AT_DISPATCH_FLOATING_TYPES*, or other dispatch macros to the new v2 API. For ATen kernel files, CUDA kernels, and native operator implementations.

2k tokens
Docstring
by pytorch
vendor ×3

Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.

3k tokens

How to use it

Copy the folder

Take xuzhougeng/managed-model-endpoints from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.