SkillRun
中文

Positioning

MCP is how tools are called. SkillRun is how executable skills become dependable.

MCP, Agent Skills, and SkillRun belong at different layers. SkillRun does not replace MCP or Agent Skills; it gives executable capabilities a package, contract, lifecycle, and evidence trail before they are exposed to local clients.

MCP

Invocation surface

Defines how an AI client talks to tools. It does not decide whether a capability is packaged, checked, tested, installed, or evidenced.

Agent Skills

Authoring and discovery layer

Teach an Agent a workflow through SKILL.md and supporting files. They are excellent for knowledge transfer, but Markdown alone is not an execution contract.

SkillRun

Runtime, contract, and evidence layer

Turns SOP-backed capabilities into Skill Capsules with Manifest checks, typed actions, preflight, artifacts, run evidence, and optional MCP Router exposure.

What each layer owns

Run the 5-minute path

Primary job

MCP Let clients invoke tools

Agent Skills Let Agents discover and learn workflows

SkillRun Make executable skills inspectable, runnable, packageable, and auditable

Artifact

MCP Server connection and tool schema

Agent Skills SKILL.md plus references, scripts, templates, and examples

SkillRun .skr package, Manifest, registry entry, switchboard exposure, and run evidence

Execution boundary

MCP Protocol shape only

Agent Skills Natural-language guidance for the Agent

SkillRun Manifest hashes, permissions, schemas, preflight, structured envelopes, and fail-closed checks

Team distribution

MCP Everyone still needs a trusted server or local setup

Agent Skills Easy to share context, harder to govern execution

SkillRun Team catalog and Desktop Team Library can review, plan, and explicitly install local packages

What it is not

MCP Not a package manager or audit log

Agent Skills Not a deterministic runtime by itself

SkillRun Not a marketplace, OS sandbox, or signature trust system

The intended team path

  1. 01 / Author

    Write SKILL.md and action code, then generate a Manifest from the declared capsule boundary.

  2. 02 / Package

    Run validate and pack so SOP, schema, permissions, examples, and source hashes move together as a .skr artifact.

  3. 03 / Review

    A teammate inspects the catalog item, sees the install plan, checksum, warnings, and local registry impact before applying anything.

  4. 04 / Expose

    Only after local import and explicit enable does the Router expose selected capabilities through skillrun router serve --mcp.

Boundaries that keep the story honest

  • SkillRun is not MCP-first; MCP is one invocation surface for enabled Runtime Capsules.
  • SkillRun is not trying to replace Agent Skills; it complements them when a workflow needs executable code and evidence.
  • Team distribution is not a Public Marketplace. The current path is local catalog, local review, explicit install, explicit enable.
  • Checksum verification proves integrity, not publisher identity, sandboxing, or business trust.
  • SkillRun does not automatically install dependencies or run unknown remote code.