- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
The paper argues that agent Skills carry their capability but not their governance. Activation scope, authorization, and execution evidence live in the host environment and can be lost when a Skill is transferred, a problem the authors call the Capability–Governance Gap. They propose Skill-in-Skill (SIS), which packages a capability with execution constraints and governance rules as . In SIS, activation requires task match, scope, and authorization; state-changing actions require destination-issued grants; and a six-stage evidence trail supports verification. SIS is compared with an External Governance Sidecar (SIDECAR) that holds the same contract outside the package. The evaluation uses 120 self-constructed business-workflow tasks (10 categories, 3 repeats, three hosted models). On these tasks, SIS reduces per-run file reads by 7.6–11.2%, tool calls by 2.6–9.1%, and cumulative task-context.json reads by up to 90.3%, while verified completion is essentially unchanged. In a transfer test on DeepSeek (six trials per cell), SIS reaches 100% authorized completion after site rebinding and principal delegation, while SIDECAR is blocked in every trial; both are blocked when destination governance is absent.
Critical strengths
S1. Clean controlled comparison. SIS and SIDECAR share capabilities, contracts, tools, permissions, and budgets, so only placement differs. Results are paired per task, use bootstrap intervals, and include held-out instances. Per-class estimates are reported in full, including unfavorable ones such as DeepSeek's increases. This makes the results easy to interpret.
S2. Reasonable problem framing. Distinguishing capability from governance is a sensible way to think about portable Skills. So are separating applicability, scope, and authorization ( vs. vs. ), separating attempted actions from admitted effects, and returning unknown instead of inferring authorization from task success.
Critical weaknesses
W1. The contribution amounts to relocating the governance specification into the Skill package. The paper states that the sole architectural difference between SIS and its baseline is placement (l. 266–267). The formalism names the fields of the package but establishes no property; Eq. 4 is simply a conjunction of three predicates. Existing work already makes governance explicit through permission manifests and runtime enforcement, e.g., SkillGuard, Progent, Proof-Carrying Agent Actions, and ClosureBound, all of which the paper cites. Relative to these, the only new element is co-location, and none of them is compared empirically.
W2. The efficiency gains are small and appear to be an artifact of how the baseline exposes governance. In absolute terms, per-run file reads fall by 0.28–0.48 against a SIDECAR mean of about 4, and tool calls fall by 0.27–0.93 against a mean of about 10. The headline "up to 90.3%" is a cumulative count for a single file over 360 runs: 93 → 9 reads for MiMo, or about 0.23 reads per run. For DeepSeek, the main backbone, output tokens, cache-read tokens, and latency all increase (+3.2%, +2.6%, +2.6%). Fig. 6 shows where the saving comes from: task-context lookups fall from 198 to 24, while skill-instruction reads stay at 246 → 246. In other words, the governance content is loaded together with the Skill instead of being looked up later. A sidecar that injects the external contract into context once at load time would likely achieve the same saving. The paper neither tests this nor specifies where SIDECAR stores its contract.
W3. The main experiment never measures governance effectiveness. The central claim concerns governance, yet the 2,160-run study reports only resource use and verified completion. Completion is indistinguishable between placements (360/360 vs. 360/360, 355 vs. 356, 354 vs. 355). The tasks are stratified into normal, boundary, conflict, and reject instances (App. A), but no per-stratum results are reported. The paper also reports no counts of violation attempts, no blocked unauthorized actions, and no per-check verifier outcomes (Table 6). The evidence therefore shows only that SIS does not hurt completion, not that it governs execution better.
W4. The only governance experiment is true by construction. The 100% vs. 0% result in Table 5 follows directly from the setup. App. G states that SIDECAR "lacks the self-contained credentials required to satisfy destination gatekeeping, resulting in predictable pre-effect containment." The test also uses a single model and six trials per cell. It includes no adversarial conditions, such as tampered packages, malicious Skills, or prompt injection, even though Sec. 2 cites the relevant security literature.
W5. The design leaves the self-assertion problem unresolved. If the carried determines what a Skill may do, a malicious Skill can declare permissive governance for itself. If instead the destination's local policy decides (l. 226–227), the carried governance is only advisory, and it is unclear what portability adds over destination policy. The paper does not discuss this tension. App. G mentions "cryptographic provenance" but does not specify signing, issuers, or a trust chain.
Questions for authors
Where does SIDECAR store its contract? Is it inside task-context.json or read alongside it? How does SIS compare with a sidecar that is loaded into context once at Skill-load time?
Who signs or certifies the carried governance? How does the destination prevent a Skill from granting itself broader scope than local policy permits? If local policy always prevails, what does carried governance add?
Consider the site-rebinding example. A skill prepared for account A arrives at a site serving account B. The receiver needs to identify the capability version, the contract governing its requested action and the verifier for its effects. SIS makes that association part of the transferred skill. B still decides whether this actor may write to B. This distinction explains both the benefit of carrying governance and why a skill cannot authorize itself.
W1/W5. What travels, and who trusts it? Equation 4 states the activation conditions. The operational contribution is what follows: the destination compares the presented capability, contract and verifier digests with its own expected values, checks the actor and requested scope, and issues a local grant. Simply declaring a broader scope in the package cannot change those expected values or produce a grant. When destination governance was withheld, both placements were blocked before effect in all six trials. Appendix G describes signed delegation, but does not specify a general package signer or certification chain. SkillGuard, Progent, Proof-Carrying Agent Actions and ClosureBound motivate the use of manifests, mediated actions and evidence. Our specific contribution is the unit that binds these checks to a transferable agent skill, together with a measurement of what changes when that binding is carried inside the unit.
W2. Where the contract lives and how many accesses it saves. We checked the staged files in a matched pair of formal MiMo trials. SIDECAR stored the contract at
stage/sidecar/governance.jsonwith an adjacentbinding.json; SIS stored the pair understage/_sis/. Each task prompt explicitly pointed the agent to its respective binding file. Task-context reads in Table 3 are a separate access measure. On MiMo they fell from 93 to 9 over 360 runs, or 0.233 fewer reads per run for that file. Across models the total saving was 0.278–0.475 file reads and 0.269–0.933 calls per run. Figure 6 localizes the Qwen change particularly clearly: task-context reads fell from 198 to 24 while skill-instruction reads stayed at 246. One-time injection of an external contract could recover the same lookup saving. The study measures the two implemented paths. We also agree that DeepSeek’s increases in output tokens, cache-read tokens and wall time preclude a cross-model claim about those endpoints.W3. What the 2,160 runs say about governance. Verified completion includes checks on actor identity, accepted-effect authorization and write scope as well as artifact and final-state correctness (Table 6). In SIDECAR/SIS order, verified completions were 360/360 versus 360/360 on DeepSeek, 355/360 versus 356/360 on MiMo, and 354/360 versus 355/360 on Qwen. The supported claim is that the measured access savings coexist with similar observed verified outcomes. Aggregate completion cannot tell us how often agents attempted violations, which verifier checks failed or how those events were distributed across normal, boundary, conflict and reject fixtures. Table 5 supplies direct evidence about attempted writes for the separate transfer experiment.
W4. What the 6/6 versus 0/6 contrast establishes. The external binding stayed at the origin in the tested transfer protocol. A sidecar that travels with the capability and is successfully reassociated could satisfy the same receiving policy. The more informative observation about enforcement is within the SIS delegation cell: all six trials ultimately completed, yet 15 write attempts were rejected for scope, 10 for missing grants and 4 for the wrong entity. Across those trials, 7 grants covered 8 admitted effects. Completion and enforcement can therefore coexist in one workflow, and the attempted/admitted distinction has an observable consequence. These trials characterize destination gatekeeping under the tested transfer protocol.