hermes-agent-profiles

Create and manage directory-locked Hermes agent profiles with isolated skills, personalities, and CLI tools.

1|Updated Mar 15, 2025
One-click install
npx skills add https://github.com/adikpb/dotfiles --skill hermes-agent-profiles-adikpb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hermes-agent-profiles
Source: https://github.com/adikpb/dotfiles/tree/main/.hermes/skills/autonomous-ai-agents/hermes-agent-profiles
Command: npx skills add https://github.com/adikpb/dotfiles --skill hermes-agent-profiles-adikpb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Running multiple AI agents on one machine normally means shared config, mixed sessions, and conflicting working directories. This Skill lets you create independent Hermes agent profiles, each locked to its own directory with its own skills, SOUL.md personality, and toolset. ## Core Features & Use Cases - Profile creation and cloning: Create named profiles via hermes profile create <name> --clone, inheriting model config and API keys while keeping memory and sessions isolated. - Directory locking and config sync: Lock each agent to a working directory with terminal.cwd, symlink .env for shared secrets, and propagate config changes to all children with the hermes-sync script. - Specialist agent setup: Includes a create-agent script and a full OSINT agent reference with free-only tool recommendations installed via uv tool install. - Use Case: Set up an osint agent locked to ~/Desktop/hermes/osint with maigret, sherlock, and holehe installed, a custom SOUL.md, and its own gateway, running alongside your main generalist agent in separate terminals. ## Quick Start Ask the agent to create a new specialized Hermes profile named osint cloned from the default profile, locked to a work directory, with a SOUL.md and the recommended free OSINT tools installed via uv.

Frequently Asked Questions about hermes-agent-profiles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a specialized Hermes agent profile?▼

Run `hermes profile create <name> --clone` to inherit your main profile's model config and API keys, then `hermes profile alias <name>` to create a shell command. Set the working directory with `<name> config set terminal.cwd /path/to/dir` and add a SOUL.md for personality.

How do I lock a Hermes agent to a specific directory?▼

Set the terminal working directory with `<profile> config set terminal.cwd /absolute/path/to/workdir`. Every terminal command in that agent starts from that directory, and project context files resolve relative to it.

Should I use uv or pipx to install Python CLI tools?▼

Use `uv tool install <package>` for all Python CLI tools; pipx is explicitly not supported by this setup. The one exception is theHarvester, whose PyPI package is a stub, so it must be cloned from GitHub and installed with `uv sync`.

Why does my profile alias not work inside a setup script?▼

Non-interactive script shells often do not load `~/.local/bin/` onto PATH, so the bare alias command fails. Use `hermes -p <name>` explicitly in scripts; the alias still works in interactive terminals.

Do Hermes profiles sandbox filesystem access?▼

No. Profiles isolate Hermes state such as config, sessions, memory, and skills, but they do not sandbox the filesystem. Directory locking only sets the starting working directory; the agent can still read and write anywhere.

How do I keep API keys in sync across multiple profiles?▼

Symlink each child profile's `.env` to the main profile's `.env` with `ln -sf ~/.hermes/.env ~/.hermes/profiles/<name>/.env`. The hermes-sync script also re-checks and restores this symlink when pushing config updates.