Overview
When Hermes completes a process successfully, explicitly ask it to turn the process into a skill.
The best candidates have three characteristics:
- The task will recur.
- The sequence is stable even when the input changes.
- The output has reached a quality level worth preserving.
A morning briefing is a strong example. The underlying information changes every day, but the procedure remains consistent: inspect the calendar, identify urgent email, summarize team activity, collect relevant documents, note preparation tasks, and deliver a concise report through the preferred channel. Once the format is refined, the procedure can be packaged as a skill and attached to a cron job.
Corrections should be concrete. Instead of saying only that an output is bad, specify what should change: lead with the answer, remove long explanations, include links to drafts, use a particular carousel layout, or place B-roll above the on-camera subject. Concrete correction gives Hermes material that can be incorporated into the reusable procedure.
Periodically inspect the skill library. Keep procedures that are current, improve procedures that are almost correct, and archive workflows that no longer reflect the way work is done.