Package, document, and version the skill

A skill is distributed as a directory. Make that directory understandable without your memory.

Validate the SKILL.md format and naming rules. Run the bundled script tests. Check every relative link. Search for absolute paths, temporary reports, credentials, private project names, and generated files that do not belong in the package.

Add a license when you intend others to reuse the skill. Add version information in metadata if your distribution process needs it. State compatibility only for real requirements. Record the owner and source repository in the surrounding project documentation rather than inventing non-standard required fields.

The final package should contain:

release-readiness/
├── SKILL.md
├── assets/
│   └── release-report.md
├── references/
│   └── npm.md
└── scripts/
    └── validate-report.mjs

Do not bundle evaluation outputs, local caches, copied repositories, or secrets. Keep the evaluation suite beside the skill in its development repository if you want to run regressions.

Install the packaged folder in a clean supported environment. Confirm it is discoverable, run one positive and one negative activation case, complete a full readiness review, and validate the report. Installation is part of the test. A folder that only works from its source checkout is not portable.