Hermes BibleUnofficial Docs
← All docs Docs / Guides & Tutorials

Tutorial: Daily Briefing Bot

Tutorial: Build a Daily Briefing Bot In this tutorial, you'll build a personal briefing bot that wakes up every morning, researches topics you care about, summa

Guides & Tutorials
Section
Guides & Tutorials
Source
hermesbible.com/docs/guides/daily-briefing-bot

Tutorial: Build a Daily Briefing Bot In this tutorial, you'll build a personal briefing bot that wakes up every morning, researches topics you care about, summa

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. What We're Building
  2. Prerequisites
  3. Step 1: Test the Workflow Manually
  4. Step 2: Create the Cron Job
  5. Option A: Natural Language (in chat)
  6. Option B: CLI Slash Command
  7. The Golden Rule: Self-Contained Prompts
  8. Step 3: Customize the Briefing
  9. Multi-Topic Briefings
  10. Using Delegation for Parallel Research
  11. Weekday-Only Schedule
  12. Twice-Daily Briefings
  13. Adding Personal Context with Memory
  14. Step 4: Manage Your Jobs

Section map

What We're Building

Maps what we're building to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Prerequisites

Maps prerequisites to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 1: Test the Workflow Manually

Maps step 1: test the workflow manually to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 2: Create the Cron Job

Maps step 2: create the cron job to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Option A: Natural Language (in chat)

Maps option a: natural language (in chat) to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Option B: CLI Slash Command

Maps option b: cli slash command to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

The Golden Rule: Self-Contained Prompts

Maps the golden rule: self-contained prompts to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Step 3: Customize the Briefing

Maps step 3: customize the briefing to the Guides & Tutorials documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Guides & Tutorials doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: What We're Building, Prerequisites, Step 1: Test the Workflow Manually, Step 2: Create the Cron Job, Option A: Natural Language (in chat). Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: tutorial, daily, briefing, build, personal. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitGuides & Tutorials documentation

Use when you need orientation for tutorial: daily briefing bot before applying exact upstream commands.

Verify firstWhat We're Building

Open the source anchor for What We're Building and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Guides & Tutorials, then open the linked source page for exact current syntax.
  2. Start with the source section for What We're Building; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Prerequisites if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page