asset-self-containment-checklisted

# Asset Self-Containment Check Check one asset folder for hidden dependencies on the rest of this repository, then report or fix deviations. This is distinct from [markdown-link-auditor](../markdown-link-auditor/SKILL.md), which checks whether links *resolve*; this skill checks whether an asset's references *escape its own package* — the "packaging over linking" rule stated in this repo's `.github/copilot-instructions.md`. ## Use this skill when - An asset is being prepared for copying into another repository or a personal customisation folder. - A review needs evidence that an asset does not silently depend on sibling repo paths. - An asset behaves correctly here but is suspected to break once extracted. ## What counts as an asset A single self-contained unit: a `SKILL.md` folder, a `WORKFLOW.md` folder, one `*.agent.md` file (plus any folder it bundles resources in), one `*.instructions.md` file, or one `*.prompt.md` file. ## Audit workflow 1. **Define scope.** Identify the one asset folder or file to check. If the user names a parent folder containing multiple assets, ask which asset to check unless exactly one exists there. 2. **Inventory the asset.** List every file inside the asset folder (or the single file, for agents/instructions/prompts without a bundled folder). 3. **Scan for escaping references.** Search the asset's content for: - relative paths using `../` that resolve outside the asset folder - absolute paths beginning with `/`,