Automation Blueprints Catalog
كتالوج مخططات الأتمتة
What this page is, and what it holds.
“Automation Blueprints Catalog” from the official documentation, reproduced in full. About 3 minutes to read.
Ready-to-run automation blueprints — set one up from the dashboard, CLI, TUI, any messenger, or the desktop app.
Outcomes taken from this page, not a template.
- Understand this page's topic and where it fits in Hermes.
Nothing summarised away.
The documentation body below is reproduced from the official source so commands and identifiers stay exact. Each section carries a short note describing what it contains.
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
Explains the idea itself. Read it slowly; the later sections build on it.
A blueprint is just a skill with a metadata.hermes.blueprint block in its
SKILL.md frontmatter. See
Creating Skills → Automation Blueprints for the
slot schema and how to publish one.