Make the skill understandable and maintainable by someone else.
1. Portable paths
Use relative references within the package and document environment assumptions. Avoid hard-coded personal directories or undeclared executables.
2. Version ownership
Assign maintainers and record changes that alter behavior or required tools. Pin references where reproducibility matters and review stale API guidance.
3. Adoption evidence
Provide a small demonstration with before-and-after output and known limitations. Installation is not proof that the skill performs the intended workflow.
Worked scenario
A colleague installs the package on a clean machine and runs the fixture suite without your local shell aliases.
Apply it
Package the skill, write setup instructions and have a clean environment execute its checks.
Check your understanding
The package works without undocumented local state. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.