Instructions for tonbistudio/hermes-multi-agent-workflow, covering agents.md — read this first, what this repository is, the single most important rule, orientation: what's generic vs. what's theirs and architecture in one paragraph.
Use on the xresearch profile's hourly cron to scan X (Twitter) via Grok for pain points that AI-agent users complain about, write a sourced intake report to the orchestrator's shared vault, and create one intake Kanban task so the orchestrator picks it up. Single-device pain-point pipeline.
The pipeline driver for the Hermes Multi-Agent Workflow. Triggered by new intake tasks on the triage board. Dedups, scores, fans out research, routes, proposes at the human gate, and on approval lets the engine spawn the fulfillment chain. It is DELIBERATELY THIN: it calls engine/ for every deterministic step and only…
Scout skill template for the Hermes Multi-Agent Workflow. Runs on a cron under a source profile, searches for candidate items in your domain, writes a report to the intake vault, and creates one intake Kanban task on the triage board. COPY this per source (e.g. triage-scout-x, triage-scout-web) and fill the TODOs.
Use when helping a user set up, debug, or operate a self-hosted Buzz relay through Docker Compose. Do not use for general Docker questions or non-Buzz Nostr deployments.
Use when connecting a remote Hermes gateway to Buzz end-to-end. Do not use for a Buzz-managed ACP runtime; use the official buzz-acp relay-bridge guide instead.