Hermes BibleUnofficial Docs
← All docs Docs / Using Hermes

Profile Distributions: Share a Whole Agent

Profile Distributions: Share a Whole Agent A profile distribution packages a complete Hermes agent — personality, skills, cron jobs, MCP connections, config — a

Using Hermes
Section
Using Hermes
Source
hermesbible.com/docs/user-guide/profile-distributions

Profile Distributions: Share a Whole Agent A profile distribution packages a complete Hermes agent — personality, skills, cron jobs, MCP connections, config — a

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. What this means
  2. Why git?
  3. When should you use a distribution?
  4. The lifecycle: author to installer to update
  5. For authors: publishing a distribution
  6. Step 1 — Start from a working profile
  7. Step 2 — Add a distribution.yaml
  8. Step 3 — Push to a git repo
  9. Step 4 — Tag versioned releases
  10. What the repo looks like
  11. Distribution-owned vs user-owned
  12. For installers: using a distribution
  13. Install
  14. Source types

Section map

What this means

Maps what this means to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Why git?

Maps why git? to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

When should you use a distribution?

Maps when should you use a distribution? to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

The lifecycle: author to installer to update

Maps the lifecycle: author to installer to update to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

For authors: publishing a distribution

Maps for authors: publishing a distribution to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Step 1 — Start from a working profile

Maps step 1 — start from a working profile to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Step 2 — Add a distribution.yaml

Maps step 2 — add a distribution.yaml to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Step 3 — Push to a git repo

Maps step 3 — push to a git repo to the Using Hermes documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Using Hermes doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: What this means, Why git?, When should you use a distribution?, The lifecycle: author to installer to update, For authors: publishing a distribution. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: profile, distributions, share, whole, distribution. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitUsing Hermes documentation

Use when you need orientation for profile distributions: share a whole agent before applying exact upstream commands.

Verify firstWhat this means

Open the source anchor for What this means and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Using Hermes, then open the linked source page for exact current syntax.
  2. Start with the source section for What this means; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Why git? if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page