Prepare a public submission

Prepare a submission packet

Assemble the information a planned public intake may require. This page creates a Markdown text document in your browser; it does not upload, scan, or submit anything.

Create a new public GitHub repository for the release. Remove credentials, memories, sessions, local databases, logs, client material, personal addresses, and private instructions before you publish it.

Submission packet

Your answers stay in this browser until you copy or download them. The progress label shows whether every required field and box is complete.

Draft

Project typeThe first option needs distribution.yaml at the top level. That file tells Hermes which profile files belong to the package.Public GitHub repositoryUse the main repository link. Leave out branch, file, archive, and private links.Public project nameA project name is enough. Leave out private contact information.What the project doesDescribe current behavior separately from ideas for later versions.Accounts and outside servicesName required accounts or variable names. Never include credential values. Write “None” when the project needs none.Files, tools, and actionsList file reading or writing, terminal commands, browser use, uploads, messages, purchases, and deletions.Schedules and automatic runsList every schedule, startup action, stop condition, and approval point.Extra software and setupList packages, scripts, build steps, applications, containers, and extra commands.Tests completed by the publisher (optional)Record only tests that happened: Hermes version, computer system, date, steps, and result.

Statements required when public submissions openI publish this repository or have the publisher’s permission to submit it.I removed secrets, credentials, personal data, private client material, memories, sessions, local databases, logs, and local machine paths from the current commit.I consent to an automated public source scan and a public report.I understand that an earlier report does not cover a later commit.

This prepares a packet. It does not submit or scan your repository.

Live previewFields or boxes still empty

# Bot Cabinet — Hermes Bot Registry submission packet

## Public GitHub repository
_Not provided_

## Project type
Installable Hermes profile package

## Public display name
_Not provided_

## What the project does
_Not provided_

## Accounts and outside services
_Not provided_

## Files, tools, and actions
_Not provided_

## Schedules and automatic runs
_Not provided_

## Extra software and setup
_Not provided_

## Tests completed by the publisher
_No testing claimed_

## Required attestations
- [ ] I publish this repository or have the publisher’s permission to submit it.
- [ ] I removed secrets, credentials, personal data, private client material, memories, sessions, local databases, logs, and local machine paths from the current commit.
- [ ] I consent to an automated public source scan and a public report.
- [ ] I understand that an earlier report does not cover a later commit.

Future Inspection Desk review

How the Inspection Desk would check one exact public version

The planned scanner would read a fixed, limited set of files without running submitted code. A public report would explain each finding and why it matters. Projects that require technical judgment would remain unpublished while human technical review is unavailable.

Return to the Submission Desk Read how to prepare a public package