Profile Distributions: Share a Whole Agent
Profile Distributions: Share a Whole Agent
Start with meaning, then move to detail.
This lesson explains Profile Distributions: Share a Whole Agent as part of getting started with Hermes correctly. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect What this means, Why git?, When should you use a distribution?, then verify failure modes and version compatibility.
No prior experience is required; follow the steps on a safe test setup first.
A clear outcome before you read.
- Understand Profile Distributions: Share a Whole Agent without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
What does the source say, and in what order?
- 01What this means
Start here to understand the core idea or structure.
- 02Why git?
Read this after the foundation, then connect it to the previous step.
- 03When should you use a distribution?
Read this after the foundation, then connect it to the previous step.
- 04The lifecycle: author to installer to update
Read this after the foundation, then connect it to the previous step.
- 05For authors: publishing a distribution
Read this after the foundation, then connect it to the previous step.
- 06Step 1 — Start from a working profile
Read this after the foundation, then connect it to the previous step.
- 07Step 2 — Add a distribution.yaml
Read this after the foundation, then connect it to the previous step.
- 08Step 3 — Create a .gitignore before the first commit
Read this after the foundation, then connect it to the previous step.
- 09Step 4 — Push to a git repo
Read this after the foundation, then connect it to the previous step.
- 10Step 5 — Tag versioned releases
Finish here to verify the result and special cases.
Copy only after you understand the effect.
my-research-agent/
├── distribution.yaml # manifest: name, version, env-var requirements
├── SOUL.md # the agent's personality / system prompt
├── config.yaml # model, temperature, reasoning, tool defaults
├── skills/ # bundled skills that come with the agent
├── cron/ # scheduled tasks the agent runs
└── mcp.json # MCP servers the agent connects tohermes profile install github.com/you/my-research-agent --aliashermes profile create research-bot
research-bot setup # configure model, API keys
# Edit ~/.hermes/profiles/research-bot/SOUL.md
# Install skills, wire up MCP servers, schedule cron jobs, etc.
research-bot chat # dogfood until it feels rightRead the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.