CtrlK
BlogDocsLog inGet started
Tessl Logo

managed-model-endpoints

Register or audit Feynman-managed model endpoints. Use when a research workflow needs a local or remote model service, endpoint health checks, credential refs, startup scripts, or inference routing.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Managed Model Endpoints

Use this skill to make a model endpoint usable from Feynman.

Workflow:

  1. Define the endpoint purpose, model family, input/output schema, auth method, hardware need, and expected latency.
  2. Record whether the endpoint is local, remote HTTP, Modal-backed, SSH-backed, or a custom connector.
  3. Add only non-secret endpoint metadata to settings. Store secret references as environment variable names or credential refs.
  4. Implement start/stop/health/inference checks when Feynman owns the endpoint lifecycle.
  5. Run a tiny inference smoke and save request/response shape without leaking secrets.

Expose endpoints as research infrastructure, not as permanent claims that a model is installed when health has not passed.

Repository
companion-inc/feynman
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.