Your First Useful Tasks

Hermes is installed and connected. Now let's make it earn its place. This lesson walks through a few concrete, non-developer tasks you can hand to Hermes today. The goal is not to show off advanced tricks. It is to help you build the habit of delegating real work, and to see the self-improvement loop start to pay off.

What You'll Learn

• How to phrase a task so Hermes can act on it
• Three practical starter tasks for students and professionals
• How scheduled automations let Hermes work on a timer
• How to help Hermes save a good result as a reusable skill

How to Phrase a Task

Talking to Hermes is closer to briefing a capable assistant than typing a search query. A good request has three parts: what you want, where the inputs are, and how you want the output. You do not need perfect wording. Hermes will ask if it needs more, and you can correct it as you go.

Compare these two requests:

• Weak: "summarize my notes"
• Strong: "Summarize the lecture notes in my Documents/notes folder from this week. Group them by subject and keep each summary to three bullet points."

The strong version tells Hermes the inputs (this week's files in a specific folder) and the output you want (grouped by subject, three bullets each). That is the difference between a vague answer and something you can actually use.

Three Starter Tasks

Here are three tasks that work well for a first session. Adapt the details to your own life.

1. Turn a Long Document Into a Short Brief

Paste or point Hermes at a long article, a PDF, or a set of notes, and ask for a brief.

"Read this report and give me a one-paragraph summary, then list the three decisions it asks me to make and any deadlines mentioned."

This is useful for students working through readings and for professionals triaging long emails or documents. Because Hermes can take multiple steps, you can follow up: "Now draft a two-sentence reply I could send to acknowledge it."

2. Build and Keep a Running Checklist

Ask Hermes to gather scattered to-dos into one place.

"Look through the meeting notes in my Documents/work folder from this week and pull out every action item assigned to me. Format them as a checklist, sorted by the earliest deadline first."

The payoff here is that Hermes can repeat this. Next week you can say "do my action-item roundup" and, because it remembers how you like it, you get the same tidy checklist without re-explaining.

3. Prepare a Recurring Summary

Many people want the same kind of summary on a schedule: a weekly study recap, a Monday-morning project status, a digest of saved articles. Set it up once with Hermes, refine it until you like it, and you have a routine you can re-run any time.

"Every Friday afternoon, create a recap of the notes I added this week, grouped by subject, and message it to me on Telegram."

That last example introduces a feature worth knowing about: scheduling.

Scheduled Automations

Hermes has built-in scheduling (often called cron, after the classic Unix scheduler). That means you can ask it to do something on a timer rather than only when you message it. A weekly recap, a daily reminder to review your tasks, a morning digest. Hermes can run these automatically and deliver the result to whichever platform you connected.

Start small. Schedule one low-stakes recurring task, see that it fires correctly and delivers what you expect, and only then add more. A scheduled task that quietly does the wrong thing every day is worse than no automation, so confirm the behavior once before you trust it on a timer.

Helping Hermes Save a Skill

Recall from earlier in the course that Hermes can write itself reusable skills. Your first useful tasks are exactly where this starts to matter.

When you and Hermes land on a result you are happy with, especially one that took a few rounds of refinement, it is worth letting Hermes capture the approach. You can simply tell it: "That is exactly the format I want. Please remember how to do this so we can repeat it." Hermes can save the routine as a skill and note your preferences in memory.

The next time you ask for the same kind of work, it reads its own skill and recalls your preferences, and you get a good result on the first try. The teaching you did once becomes a permanent capability. This is the compounding payoff the course mentioned at the start, and it shows up fastest on recurring tasks like checklists and weekly summaries.

A Word on Cost

Each of these tasks involves the language model doing some thinking, and if you are on a cloud backend that costs a small amount. None of the starter tasks above are expensive, but it is a good habit to keep an eye on your provider's usage dashboard in the early days so there are no surprises. We will return to cost in the safety lesson, because runaway usage is one of the risks worth managing.

Key Takeaways

• Phrase tasks with three parts: what you want, where the inputs are, and how you want the output.
• Strong starter tasks include summarizing long documents, building running checklists, and preparing recurring summaries.
• Hermes can run tasks on a schedule (cron); start with one low-stakes recurring task and confirm it before trusting it.
• When you get a result you like, ask Hermes to remember it so the approach becomes a reusable skill.
• Each task uses the language model, so watch your provider's usage dashboard early on to avoid surprises.