Skill Capsule
Bind SOP to action
SKILL.md explains the capability. Action code, schemas, preflights, and examples make it inspectable, testable, and packageable.
Executable Agent Skills runtime
Make executable Agent Skills inspectable, runnable, and evidenced.
SkillRun packages SKILL.md / SOP, action code, schemas, preflights, Manifests, and run evidence into Skill Capsules that can be exposed through an MCP Router when needed.
Team distribution for MCP tools and Agent Skills is the adoption route. SkillRun's core value is the runtime, contract, and evidence layer for executable skills.
manifest, package, route
$ skillrun manifest --cwd refund
$ skillrun validate --cwd refund
$ skillrun pack --cwd refund
$ skillrun import <package.skr> --id refund --json
No Manifest contract, no execution.
.skr is a distribution artifact; runtime and MCP exposure stay under local SkillRun Core / Router control.
SkillRun model
SkillRun is not just a wrapper around Skills and MCP.
Manifest contract
Freeze the contract first
Manifest stores source hashes, permissions, adapter, schemas, and MCP exposure. Missing, stale, or mismatched contracts fail closed.
Run evidence
Keep evidence after execution
Every run has a structured envelope, artifacts, hashes, timing, and a run record. stdout and stderr are logs, not business results.
Adoption route
Team distribution is how SkillRun lands, not the whole definition.
Share Skill Capsules
Teammates receive inspectable .skr artifacts instead of copied prompts or hand-written MCP configuration.
Check and enable locally
Consumers use import, check, doctor, and switchboard to decide what becomes locally enabled.
Mount the Router when needed
Claude Desktop, Codex, and other MCP clients mount skillrun router serve --mcp; the Router exposes enabled capabilities.
Trust boundary
Team distribution is not a marketplace or sandbox promise.
SkillRun makes capabilities inspectable, packageable, versioned, and evidenced. It does not make arbitrary third-party code automatically safe. Signatures, provenance, and publisher identity are future high-risk design work.
Available now
Local .skr import, replace, inventory, switchboard, local/remote Team Catalog review, Router status, mount plan/apply, run evidence, and release asset attestations.
Team Library route
Team catalog and Desktop Team Library use stable Core JSON surfaces to review shared catalog URLs, plan installs, and keep apply guarded to local artifacts.
Explicit non-goals
No Public Marketplace, automatic dependency install, remote execution of unknown code, or OS sandbox claim.
Next step
Run the local lifecycle first, then use Desktop Team Library to inspect a shared catalog URL before choosing any local install.