01 / capability
Skill hosting and execution
Defined as an explicit contract so operators can review it before it runs.
Agents, MCP & capabilities · Concept
Ship the capability, not the glue.
Infrastructure for hosting, discovering, executing and governing reusable agent skills as network-accessible capabilities.
01
What it is
SkillServers is built for AI developers, enterprises, skill publishers, agent platform operators.
The problem
SkillServers replaces embedded agent scripts, manual skill sharing and ungoverned capability endpoints.
The approach
Infrastructure for hosting, discovering, executing and governing reusable agent skills as network-accessible capabilities.
The boundary
Work stays inside an explicit scope: named sources, defined permissions, bounded execution, retained evidence.
02
Capabilities
Five contracts the product is specified around. Each one is a boundary as much as a feature.
02 / capability
Manifest and dependency management
Available through the product surface and the machine interfaces, with permission attached.
03 / capability
Skill discovery and versioning
Exposed as a scoped capability with its own evidence trail, not a hidden setting.
04 / capability
Authorization, telemetry and testing
Available through the product surface and the machine interfaces, with permission attached.
05 / capability
MCP-compatible invocation and distribution
Available through the product surface and the machine interfaces, with permission attached.
03
How it works
The same three steps apply whether a person or an agent is driving.
01
Define the scope
Start from the boundary SkillServers is allowed to act inside: the workspace, the sources, the budget, the authority.
02
Connect the surfaces
Expose the same capability through the interface a human uses and the interface an agent calls, with one permission model.
03
Act with evidence
Every action leaves a record that can be inspected, replayed and challenged before the next one runs.
Read the specification before you believe the category.
SkillServers is documented as a concept: requirements, interfaces and evidence expectations. It is not presented as a live service.