Submission Desk
Prepare a public Hermes project for future review. The Hermes Bot Registry plans to accept public Bot packages, starter collections, and educational guides. Each listing would identify a recorded source version and show automated source scan, human technical review, and Hermes Desktop test status separately.
- 01
Share the main public GitHub link
The form asks what the project does, what accounts it needs, which files and tools it can use, which actions require approval, and whether the submitter has permission to share it.
- 02
Run the automated source scan
The planned scanner would read a fixed, limited set of public files without running the submitted code. It would look for private material, dangerous instructions, broad access, package conflicts, and missing release information.
- 03
Publish a plain-English report
The report would explain each finding, why it matters, and whether the automated source scan, human technical review, and Hermes Desktop test were completed. Projects the scanner could not assess would stay unpublished while human technical review is unavailable.
- 04
Create a listing with clear status labels
The listing would explain the project’s purpose, example requests, intended result, required access, recorded source version, and the status of each review step.
Create a new package specifically for public release
A live profile can contain credentials, memory, sessions, logs, cached documents, client information, and private instructions. Keep those files out of the public package and its Git history.
Read how to prepare a public profile packageProposed requirements for future public intake
- Main public GitHub repository URL
- Clear project type and current publisher
- A top-level file named distribution.yaml that tells Hermes which files belong to an installable package
- Names of required accounts, credentials, files, and tools
- License text for original and bundled work
- No secrets, memories, sessions, personal information, or client material
- Known limitations and actions that require a person’s approval
Human technical review is unavailable
A planned automated source scan could handle repeatable checks. Projects that require technical judgment would remain unpublished while human technical review is unavailable.
Prepare a submission packet for later
The form creates a Markdown record in your browser. Keep it with your public project until submissions open. The form does not upload a repository, run a scan, or add a listing.