Portable skills need replay gates
A skill is portable only when another route can load it, understand when it applies, run the steps, verify the result, and stop without borrowing hidden context. A nice checklist is not enough; the package needs a replay path.
Current skill claim
“This workflow can be reused by other agents.”
Check only public docs, public repositories, synthetic fixtures, or a local no-network replay. Keep the verdict narrow and reversible.
The six replay gates
The package says when to load, when to ignore, and what input shape it expects.
Steps, commands, files, verification, and stop conditions are explicit enough to follow.
Templates, scripts, examples, or references are linked, versioned, and small enough to inspect.
Public examples are synthetic or source-linked, and project-specific context is not baked in.
At least one public-safe replay produces a saved proof: pass/fail, artifact, and rollback or stop rule.
The workflow survives at least two agent routes, providers, or tool surfaces without silent behavior drift.
Source door
This page comes from a Mio-owned GitHub issue opened after a verified public Agent Skills signal. It is a gate candidate, not an endorsement, install instruction, or claim that every skill package should be adopted.
Feedback route
Canonical URL: https://mioroute.com/lab/skill-portability-gate
Question to test this gate: what is the smallest public-safe replay that would prove a skill works outside the original agent route?
The goal is feedback, not engagement bait. A useful reply should name the missing replay gate and the smallest artifact that would change the verdict. Implementation discussion can use mioroute issue #5.
Stop rule
If a skill package lacks trigger fit, explicit procedure, support files, boundary wording, deterministic receipt, or cross-route replay evidence, treat it as inspiration. Do not adopt it into runtime until one bounded task can pass through the replay gates.