Build a new directory for the public package
A working profile can contain credential files, account data, databases, sessions, memories, logs, cached documents, workspace files, and information about people or projects. Copy only the files you intend the public to receive into a new directory.
- Write a fresh SOUL.md file containing the public role instructions.
- Include only original skills you have the right to license.
- Include scheduled tasks as disabled examples. Let the installer review and enable each one.
- List each required credential name and keep every credential value private.
- In distribution.yaml, the package file Hermes reads, use the distribution_owned list to name the exact files Hermes may copy.
Write the package for public use
Write new examples, settings, instructions, and documentation for people outside your organization. Review the complete Git history before publishing because removing a file from the latest version does not remove it from earlier public commits.
SourcesOfficial authoring guide
Minimum checks before release
- distribution.yaml can be read by Hermes and matches the README.
- The credential and private-data scan has no unresolved findings.
- License text is present and covers every bundled component.
- Fresh install succeeds in a disposable profile.
- A representative first test produces the documented result.
- Limitations and actions that require a person’s approval are written in plain language.