Build for Skulk™
A capability is an operation with a versioned descriptor: clients discover its input and output schemas, then negotiate a call against that exact contract. A plugin packages one or more capabilities with configuration, permissions, setup and lifecycle. An application can also declare a web surface that appears in Skulk™’s dashboard.
Start here
- Get the SDK: availability, supported environment and delivery.
- Build a managed echo child: define a descriptor, authenticate startup and answer a call.
- Choose a contract: unary, streaming or a durable operation.
- Try the examples: echo, duplex streams and job identity.
- Follow Video Studio: turn those building blocks into a complete application.
Build your application
| Question | Guide |
|---|---|
| How do peers know what I do? | Descriptors |
| How do I exchange audio or incremental results? | Managed streaming |
| How do I track work that takes minutes? | Durable jobs |
| How does my UI appear in the dashboard? | Application interfaces |
| How do I declare configuration and access? | Manifests and permissions |
| How do I distribute and verify a plugin? | Catalogs and qualification |
SDK and host roles
The capability SDK is the child authoring interface. Skulk™ and the managed host supply discovery, admission, process supervision and installation authority. Your application owns its behavior, external effects, resource cleanup and truthful readiness. The SDK does not supply a model engine or mount models automatically.
SDK module reference covers exact signatures and field contracts. Foxlight Docs owns installation, inference and HTTP endpoint reference.