mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-06-14 09:11:54 +00:00
021ed69141
* docs: finish Automation Blueprints terminology rebrand
Replace leftover "Automation Templates" wording from the Cron Recipes
rebrand, rename the copy-paste cookbook guide to Automation Recipes, and
point the marketing gallery link at the blueprints catalog.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: use Automation Blueprints instead of Recipes in guide
Rename the cookbook guide from automation-recipes to
automation-blueprints so sidebar and copy match the product term.
Co-authored-by: Cursor <cursoragent@cursor.com>
* docs: rename automation-blueprints-catalog to automation-blueprints
Drop the -catalog suffix from the reference page slug and title, and
move the copy-paste cookbook to automation-blueprint-examples so the
main Automation Blueprints doc is unambiguous.
Co-authored-by: Cursor <cursoragent@cursor.com>
* Revert "docs: rename automation-blueprints-catalog to automation-blueprints"
This reverts commit 605f1eeab5.
---------
Co-authored-by: Cursor <cursoragent@cursor.com>
36 lines
1.5 KiB
Text
36 lines
1.5 KiB
Text
---
|
|
sidebar_position: 7
|
|
title: "Automation Blueprints Catalog"
|
|
description: "Ready-to-run automation blueprints — set one up from the dashboard, CLI, TUI, any messenger, or the desktop app."
|
|
---
|
|
|
|
import AutomationBlueprintsCatalog from '@site/src/components/AutomationBlueprintsCatalog';
|
|
|
|
# Automation Blueprints
|
|
|
|
Automation Blueprints are ready-to-run automations. Pick one, fill in a couple
|
|
of fields, and Hermes schedules it as a cron job — no cron syntax required.
|
|
|
|
Every blueprint works from **every surface**:
|
|
|
|
- **Dashboard / desktop app** — open the Cron page, switch to the **Blueprints**
|
|
tab, fill the form, and click *Schedule it*.
|
|
- **CLI, TUI, and messengers** — type `/blueprint <name>` (e.g.
|
|
`/blueprint morning-brief`) and Hermes asks you for what it needs, one
|
|
question at a time, then schedules it. The name match is forgiving — a
|
|
prefix or near-spelling resolves. Power users can skip the questions by
|
|
passing values inline: `/blueprint morning-brief time=08:00`.
|
|
- **Desktop app** — click **Send to App** on any blueprint and it opens with the
|
|
command pre-loaded in your composer.
|
|
|
|
Blueprints never schedule anything silently — you always confirm before the job
|
|
is created. Manage created jobs anytime with `/cron`.
|
|
|
|
<AutomationBlueprintsCatalog />
|
|
|
|
## Writing your own
|
|
|
|
A blueprint is just a skill with a `metadata.hermes.blueprint` block in its
|
|
`SKILL.md` frontmatter. See
|
|
[Creating Skills → Automation Blueprints](../developer-guide/creating-skills.md) for the
|
|
slot schema and how to publish one.
|