# 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.

Canonical: https://xcloud.host/use-cases/playbooks/hermes-weekly-report/
Published: 2026-10-01 · Updated: 2026-10-01 · Technical review: 2026-10-01
Evidence: Source reviewed; no production deployment test claimed
Editorial owner: xCloud editorial

Intent: Prepare a recurring weekly team report with Hermes and Telegram
For: administrator, team-owner

## Requirements and responsibilities

- Assign a named team owner for this task and confirm that all needed service accounts, sources and data are within the approved scope. Never place credentials or private keys in agent prompts. Sources: [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron); [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron); [xCloud Hermes Agent deployment guide](https://xcloud.host/docs/how-to-deploy-hermes-agent-with-xcloud/)
- Confirm the managed Hermes service is running and use only xCloud controls documented for this task; any upstream Hermes CLI, file or scheduled-job procedure needs an authorized operator and is not evidence of an xCloud panel feature. Sources: [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron); [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron); [xCloud Hermes Agent deployment guide](https://xcloud.host/docs/how-to-deploy-hermes-agent-with-xcloud/)

## 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

- Keep reconciliation manual when source exports are not accessible on the server; schedule only when the approved exports are present at each run time. Sources: [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron); [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron); [xCloud Hermes Agent deployment guide](https://xcloud.host/docs/how-to-deploy-hermes-agent-with-xcloud/)

## Dashboard and application procedure

### 1. 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.

Capability: Review the task result and retain human control
Sources: [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron)

### 2. 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.

Capability: Review the task result and retain human control
Sources: [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron)

### 3. 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.

Capability: Use the authorized Hermes terminal, CLI or documented task interface
Sources: [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron)

### 4. 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.

Capability: Use the authorized Hermes terminal, CLI or documented task interface
Sources: [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron)

### 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.

Capability: Review the task result and retain human control
Sources: [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron)

## Maintenance

- Compare each weekly report period and source set to the approved template; inspect deliveries before editing the job schedule. Sources: [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron); [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron); [xCloud Hermes Agent deployment guide](https://xcloud.host/docs/how-to-deploy-hermes-agent-with-xcloud/)

## Recovery decisions

- For a missed or duplicate report, pause the existing job and compare actual deliveries with cron history before editing it; avoid creating a duplicate job. Sources: [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron); [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron); [xCloud Hermes Agent deployment guide](https://xcloud.host/docs/how-to-deploy-hermes-agent-with-xcloud/)

## 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

- **Review the task result and retain human control** (app; manual): Human acceptance and follow-up; no external write is implied. Checkpoint: Verify the source/output and actual side effects before sharing or acting. Sources: [Hermes security guide](https://hermes-agent.nousresearch.com/docs/user-guide/security); [Hermes daily briefing tutorial](https://hermes-agent.nousresearch.com/docs/guides/daily-briefing-bot); [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron)
- **Use the authorized Hermes terminal, CLI or documented task interface** (app; manual): Upstream Hermes CLI/configuration workflow; requires an authorized operator and does not prove xCloud preconfigured the feature or exposed it in its panel. Checkpoint: Check the installed Hermes version and current upstream instructions; review scope and permissions before running a task. Sources: [Hermes quickstart](https://hermes-agent.nousresearch.com/docs/getting-started/quickstart); [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron); [Hermes memory feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/memory); [Hermes skills feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/skills); [Hermes agent email address tutorial](https://hermes-agent.nousresearch.com/docs/guides/agent-email-address); [Hermes GitHub PR review agent tutorial](https://hermes-agent.nousresearch.com/docs/guides/github-pr-review-agent); [Hermes delegation feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/delegation)

### Copyable agent brief

```text
Use the named timezone and compute the prior completed Monday 00:00 to current Monday 00:00 period. Select only the export whose filename and row dates match this period; if missing or mismatched, report that and stop—never reuse an older file. Match expected keys, distinguish missing from zero, recompute totals with units/currency, cite file/row for each figure, and return mismatches. Do not edit source systems.
```

### 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

- **Documented Hermes task path** (covered): Steps identify whether an action uses documented xCloud controls, upstream operator configuration or human review. Steps: step-1, step-2, step-3, step-4, step-5
- **Task-specific acceptance check** (covered): The final step validates this guide’s stated result. Steps: step-5

## Sources

- [Hermes automate with cron patterns](https://hermes-agent.nousresearch.com/docs/guides/automate-with-cron) — reviewed 2026-10-01
- [Hermes cron feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/cron) — reviewed 2026-10-01
- [xCloud Hermes Agent deployment guide](https://xcloud.host/docs/how-to-deploy-hermes-agent-with-xcloud/) — reviewed 2026-10-01
- [Hermes security guide](https://hermes-agent.nousresearch.com/docs/user-guide/security) — reviewed 2026-10-01
- [Hermes daily briefing tutorial](https://hermes-agent.nousresearch.com/docs/guides/daily-briefing-bot) — reviewed 2026-10-01
- [Hermes quickstart](https://hermes-agent.nousresearch.com/docs/getting-started/quickstart) — reviewed 2026-10-01
- [Hermes memory feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/memory) — reviewed 2026-10-01
- [Hermes skills feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/skills) — reviewed 2026-10-01
- [Hermes agent email address tutorial](https://hermes-agent.nousresearch.com/docs/guides/agent-email-address) — reviewed 2026-10-01
- [Hermes GitHub PR review agent tutorial](https://hermes-agent.nousresearch.com/docs/guides/github-pr-review-agent) — reviewed 2026-10-01
- [Hermes delegation feature guide](https://hermes-agent.nousresearch.com/docs/user-guide/features/delegation) — reviewed 2026-10-01

## Continue

[Review xCloud Hermes deployment options](https://xcloud.host/docs/how-to-deploy-hermes-agent-with-xcloud/)

- [Send a daily research briefing to Telegram](https://xcloud.host/use-cases/playbooks/hermes-daily-briefing/)