Skins & Themes
Skins control the visual presentation of the Hermes CLI: banner colors, spinner faces and verbs, response box labels, branding text, and the tool activity prefi
- Section
- Core Features
- Source
- hermesbible.com/docs/user-guide/features/skins
Skins control the visual presentation of the Hermes CLI: banner colors, spinner faces and verbs, response box labels, branding text, and the tool activity prefi
Excerpt from the official Hermes Agent documentation, quoted for reference. View sourceWhat this page covers
- Change skins
- Built-in skins
- Complete list of configurable keys
- Colors (colors:)
- Spinner (spinner:)
- Branding (branding:)
- Other top-level keys
- Custom skins
- Full custom skin YAML template
- Minimal custom skin example
Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.
Upstream outline
Section map
Change skins
Maps change skins to the Core Features documentation path, with the source page reserved for exact commands and updates.
Built-in skins
Maps built-in skins to the Core Features documentation path, with the source page reserved for exact commands and updates.
Complete list of configurable keys
Maps complete list of configurable keys to the Core Features documentation path, with the source page reserved for exact commands and updates.
Colors (colors:)
Maps colors (colors:) to the Core Features documentation path, with the source page reserved for exact commands and updates.
Spinner (spinner:)
Maps spinner (spinner:) to the Core Features documentation path, with the source page reserved for exact commands and updates.
Branding (branding:)
Maps branding (branding:) to the Core Features documentation path, with the source page reserved for exact commands and updates.
Other top-level keys
Maps other top-level keys to the Core Features documentation path, with the source page reserved for exact commands and updates.
Custom skins
Maps custom skins to the Core Features documentation path, with the source page reserved for exact commands and updates.
Implementation notes
- Use this Core Features 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: Change skins, Built-in skins, Complete list of configurable keys, Colors (colors:), Spinner (spinner:). Read those source anchors before changing installs, credentials, automation, or runtime configuration.
- Useful search signals for this doc: skins, themes, control, visual, presentation. These are derived from the public title and summary so the clone remains lightweight.
Decision table
Use when you need orientation for skins & themes before applying exact upstream commands.
Open the source anchor for Change skins and confirm platform-specific requirements before changing configuration.
Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.
Verification checklist
- Use this page to orient yourself within Core Features, then open the linked source page for exact current syntax.
- Start with the source section for Change skins; do not rely on the local summary for commands or secrets.
- Check platform, install method, provider, and credential assumptions before changing a real environment.
- Review the source section for Built-in skins if the page involves setup, automation, messaging, or runtime behavior.
- After applying anything from the source, run the smallest relevant smoke test before widening scope.
Risk notes
Keep human review before sending public posts, customer messages, trading instructions, or team notifications.
Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.
What this page covers
- Skins control the visual presentation of the Hermes CLI
- banner colors, spinner faces
- verbs, response box labels, branding text
- the tool activity prefi
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