Book a demo
Book a demo
Login

Playbook Hermes Agent

Prepare a weekly team report with Hermes cron

Build a weekly report from an explicitly named source set, validate one manual run, and schedule one Telegram delivery with a clear owner.

Technical review: · Source reviewed; no production deployment test claimed

Published · Updated · xCloud editorial

Read this guide as Markdown

Requirements and responsibilities

Illustrative situation

Illustrative scenario: an operations team wants a Monday reconciliation of the previous closed week’s named CSV exports, including missing record keys and recalculated totals.

Choose the approach

Dashboard and application procedure

Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.

Step 1 of 5

Name the closed-period records

Where
Team report owner and approved source exports
Permissions
Report owner and source-system owners
Inputs
Named reporting timezone; prior completed Monday 00:00 through current Monday 00:00; exact dated export filename pattern; expected keys/units
Action
Define the report period as the previous completed Monday 00:00 through this Monday 00:00 in one named timezone (include exact dates in each report). At each run, select only the export named for that period, for example `team-ops-YYYY-MM-DD.csv` keyed by the period start. Confirm the file date and period match; never reuse a prior file when this period’s export is missing.
Expected result
One period-specific input file is identified, or the run explicitly reports that this period’s file is missing.
Verify
Inspect the filename/date and row period fields against the named timezone window before calculating.
If it fails
If a source is not connected or permission is unclear, omit it and state the limitation.

Sources: Hermes automate with cron patterns

Step 2 of 5

Define reconciliation rules

Where
Team-approved report contract
Permissions
Report owner
Inputs
Expected record keys; totals and tolerance; output schema
Action
Require a table of expected vs found keys, explicit missing vs zero labels, period totals recomputed from source rows, source filename/row references and unresolved mismatches. Preserve units/currency and never fill missing values with assumptions.
Expected result
Recipients can compare reports week to week.
Verify
Have one representative recipient confirm the sections answer a real team question.
If it fails
If the report needs actions or decisions beyond summarization, identify an approver for those separately.

Sources: Hermes automate with cron patterns

Step 3 of 5

Reconcile one completed week manually

Where
Hermes terminal/conversation with approved exports
Permissions
Authorized Hermes user
Inputs
One closed-period export set and the report contract
Action
For the current completed Monday-to-Monday period, locate only that period’s matching export. If it is missing or mismatched, report the blocker and stop; otherwise reconcile record keys, calculate totals from the supplied rows, distinguish missing keys from zero values and cite file/row evidence.
Expected result
A draft report is produced without sending or changing external systems.
Verify
Check period boundaries, source citations and totals against originals.
If it fails
If the current period file is missing, malformed or dated for another week, stop and request the correct export; do not fall back to a previous week.

Sources: Hermes cron feature guide

Step 4 of 5

Schedule a weekly reconciliation

Where
Authorized Hermes terminal/CLI reached through xCloud SSH if enabled
Permissions
Hermes operator authorized to create cron jobs
Inputs
Validated report prompt; weekly time; configured Telegram home channel
Action
Check the scheduler’s configured timezone and expected next run, then use the upstream form `hermes cron create "0 9 * * 1" "<validated closed-week report prompt>" --name "Weekly team reconciliation" --deliver telegram`. Verify CLI syntax and that source exports will be present at run time; xCloud does not document a cron dashboard.
Expected result
One weekly job appears in Hermes cron listing.
Verify
Inspect schedule, target and prompt; verify the job runs with the intended timezone.
If it fails
If delivery target is unsupported or missing, keep the report manual until an owner configures a supported channel.

Sources: Hermes cron feature guide

Step 5 of 5

Audit report completeness and delivery

Where
Hermes cron run history and configured Telegram destination
Permissions
Report owner
Inputs
First two closed-week outputs, expected keys and original exports
Action
Compare period dates, keys, missing-vs-zero classification, recalculated totals and source row references against originals. Check actual delivery; pause the existing job if reports duplicate or cover a stale period.
Expected result
Team can see whether the report is reliable and correctly scoped.
Verify
Check actual deliveries before making any schedule changes.
If it fails
For missed/duplicate runs, pause the existing job, inspect history and edit that job rather than adding another.

Sources: Hermes cron feature guide

Maintenance

Recovery decisions

AI handoff

Configure the needed provider, channel, credentials and permissions separately. This guide does not imply xCloud has preconfigured upstream tools or scheduled jobs.

Supported scope

Copyable agent brief

Manual checkpoints

  • Before enabling a weekly job, confirm the named timezone, dated-file naming rule and an approved mechanism that places each new period export in the Hermes-readable workspace. The task must stop on missing/mismatched current-period input; it must not fall back to stale files.
  • Review the task-specific acceptance check and inspect actual output, configuration or run history before relying on it.
Feature coverage

Sources

Continue

Review xCloud Hermes deployment options