Hermes files forwarded email into a company wiki

thetomsays gives Hermes a dedicated inbox for maintaining company knowledge. Employees can forward an internal email thread to an update address, and the agent scans its contents for information that belongs in the company wiki.

The reported result is a working capture path from the tool employees already use. Instead of relying on someone to remember a separate wiki update after finishing an email conversation, the forwarded thread provides the input for the assistant to file. The author describes this as an effective internal automation, without sharing the company’s private pages or a measured completeness rate.

The account also identifies unfinished refinement: deciding which users may update departmental pages, which information requires approval or verification, and how scheduled audits should notify stakeholders. Those are governance questions around the workflow, not proof that all those controls were already implemented.

In replies, the author distinguishes the wiki from Hermes’s own memory and mentions Obsidian and Outline as possible choices rather than identifying a confirmed platform for this deployment. The useful detail is separating information capture from permission to change a shared record. Forwarding reduces the employee’s filing step, but does not establish that the assistant always extracts the right facts or resolves conflicting versions correctly. The source contains no complete original instruction; the prompt below is our suggested adaptation.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Reddit · thetomsays