Reference closure in the received artifact

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

Hand one skill directory to another device. Its entrypoint references ../../references/checklist.md, present in the author’s repository, but the receiver gets only skills/reviewer/. The teaching contract distinguishes a required checklist from optional examples. Author accessibility does not establish receiver accessibility.

Mechanism

Enumerate entrypoint and downstream required references, resolving each relative to its containing file. Inspect files, versions and contents in the delivered layout. For external dependencies, ship the required package structure or include permitted material and update paths. Give optional gaps a stated fallback; report missing required material as incomplete execution.

Bad example

Copy only skills/reviewer/ while retaining ../../references/checklist.md. Because it opens in the author's checkout, tell the receiver that references passed validation.

Good example

Validate the receiver's actual skill package. Enumerate the required checklist and optional examples, resolve paths from each containing file and open every target. The current checklist did not accompany the single skill. Deliver the necessary package layout or package the permitted checklist and update its path. Report required gaps; use documented optional fallbacks. Recheck the delivered layout instead of borrowing the author's passing result.

Why the change matters

Relative resolution depends on received directories and shipped files. Author-side checks establish that layout only; receiver-side traversal exposes missing dependencies and flattening collisions, keeping pointers reachable where work runs.

Observable expectation

An illustrative report marks the checklist missing, then opens and verifies it after packaging is corrected. Where directories have identically named files, inspect for overwrites caused by flattening.

Every required reference needs a receiver-side result, and optional gaps need fallbacks. Existing but unreadable files do not pass.

Limits

Reachability does not establish license, meaning or safety, and private material must not be copied without authorization. Whole-package and single-skill installation have different dependency scope. This example does not run upstream installation commands.