Create Hermes Cron Jobs from Blueprints

/blueprint provides reusable templates for common Hermes automations. A blueprint defines the shape of a job and exposes named slots for the details that vary, such as schedule, source, query, destination, or topic. It reduces repetitive setup without removing the need to inspect the job that gets created.

Official cron guide: https://hermes-agent.nousresearch.com/docs/user-guide/features/cron

Choose guided or direct creation

Run /blueprint with no arguments to browse the catalog. /blueprint <name> starts a guided slot-filling conversation on the next agent turn. If every required value is already known, /blueprint <name> slot=value ... can create the job directly. Jobs created in a messaging surface deliver back to the current chat or thread unless the template says otherwise.

Guided mode is safer when a slot affects permissions, data scope, or schedule. Direct mode is efficient for a well-understood template with reviewed values.

Blueprint checklist

• Read the template purpose and every required slot.
• Use explicit timezones and unambiguous schedules.
• Point sources at public or properly authorized data.
• Keep credentials in configured secret stores, never slot text.
• Verify the delivery channel or thread.
• Add no-change, retry, and escalation behavior.
• Confirm the selected model and skills fit the work.
• Inspect the concrete cron job after creation.

Templates are not permissions

A catalog entry can describe a useful pattern, but it cannot grant authority to send email, publish content, spend money, change DNS, or mutate customer records. Those boundaries must remain explicit in the generated job. Prefer a read-only first run when a template touches an unfamiliar source.

Pitfalls

• Filling a timezone slot with an ambiguous abbreviation.
• Putting API keys or passwords into slot values.
• Assuming a curated template is automatically safe for every account.
• Creating a duplicate job instead of updating an existing one.
• Forgetting that the current chat may become the delivery destination.
• Skipping the first-run review because template creation succeeded.

Verification steps

1. List the catalog and select the narrowest matching blueprint.
2. Review all filled slot values before creation.
3. Inspect the resulting job's schedule, prompt, skills, model, and destination.
4. Run it once manually with low-risk inputs.
5. Confirm the result reaches the correct surface.
6. Exercise a no-change or unavailable-source case.
7. Leave the schedule active only after the concrete job passes review.