1
The core frame: junior operator, not magic money printer
The video's practical warning is that Hermes does not replace having an actual offer, distribution, customers, or judgment. Hermes creates leverage around repetitive operator work: research, monitoring, drafting, follow-up, summarization, reminders, and turning messy inputs into organized outputs.
Best mental model: attach Hermes to a business function people already pay for: sales pipeline, content intelligence, trend monitoring, market research alerts, or client follow-up operations.
Bad use
“Send a thousand generic AI emails,” “trade for me while I sleep,” or “automate the whole business.” These workflows create risk, spam, or unrealistic expectations.
Good use
“Research 25 qualified accounts,” “draft messages for review,” “watch for fresh opportunities,” “summarize call notes,” and “ask before sending anything externally.”
2
Practical Hermes setup before using these workflows
You can run many of these as one-off prompts in a normal Hermes chat. For repeatable systems, use Hermes skills, cron jobs, memory, messaging delivery, and connected data destinations such as Sheets, Notion, or local files.
- Confirm Hermes is healthy.
hermes doctor
hermes status --all
- Use a normal chat for first drafts.
hermes chat
- Schedule recurring operator work when the prompt is stable.
In chat, ask Hermes to create a recurring cron job, or use the CLI cron commands.
hermes cron list
hermes cron create "0 8 * * *"
- Keep memory clean.
Save durable facts such as client preferences or recurring constraints. Do not save temporary task progress, one-off leads, or stale status updates as memory.
Important: if a workflow sends messages, places orders, trades, modifies client records, or publishes content, keep human approval in the loop unless you have explicitly designed and tested a safe automation boundary.
3
Workflow 1: Lead generation and outreach research
Video timestamp: 1:44, prompt at 3:18The most realistic monetization workflow is also the least flashy: qualified prospecting. Hermes can research accounts, qualify them against an ideal customer profile, explain the angle, and draft reviewed outreach. It should not become a spam engine.
Exact prompt discussed in the video
Find 25 B2B companies in crypto, SaaS, or creator tools that look like they could benefit from a short-form content system. For each one, capture the company name, website, what they sell, why they might need content, and one personalized outreach angle. Do not send anything, put the research into a table, and draft three message variants for review.
Reusable prompt template
Find [NUMBER] [BUSINESS TYPE] companies in [INDUSTRY / NICHE] that look like they could benefit from [YOUR OFFER]. For each one, capture: company name, website, what they sell, who the likely buyer is, why they might need [YOUR OFFER], one personalized outreach angle, and any obvious risk or reason they might not be a fit. Do not send anything automatically. Put the research into a table and draft [NUMBER] first-message variants for my review.
How to operationalize it
- Define the offer in outcome language: “weekly pipeline of qualified leads with custom opening angles,” not “AI outreach.”
- Define the ideal customer profile: company size, niche, trigger events, budget clues, geography, and exclusions.
- Ask Hermes to produce a table, not send messages. Columns should include fit reason, personalization angle, confidence, and next step.
- Review the table, delete weak fits, then manually send or approve messages.
- Track replies and follow-ups in a CRM, Sheet, or Notion database.
Productized service idea: sell a weekly prospecting system for agencies, founders, consultants, or freelancers. Deliver qualified leads plus custom opening angles.
4
Workflow 2: Content research and idea briefs
Video timestamp: 4:39, prompt at 5:33Creators and founders do not just need more content; they need better angles. Hermes can repeat the research loop: check competitors, YouTube, X, keywords, comments, and recent winners; then convert the findings into a filming or posting brief.
Exact prompt discussed in the video
Act as my YouTube research operator. Find 10 recent videos in the AI agent niche that are outperforming their channel average. For each one, capture the title, channel, views, upload date, hook pattern, why it likely worked, and how I could adapt that pattern without copying the video. Return the top three ideas I should film this week.
Reusable prompt template
Act as my [PLATFORM] research operator for [NICHE]. Find [NUMBER] recent posts/videos/articles from [SOURCES] that appear to be outperforming their creator or channel average. For each one, capture the title or post text, creator/channel, engagement metrics, publish date, hook pattern, why it likely worked, target audience, and how I could adapt the pattern without copying the content. Return the top [NUMBER] ideas I should create this week, each with a draft title, opening hook, and angle.
What the output should include
- Title or post text.
- Channel or creator.
- Views, likes, comments, or other engagement metrics.
- Upload or publish date.
- Hook pattern: contrarian, tutorial, teardown, comparison, warning, speedrun, result reveal, or challenge.
- Why it likely worked.
- How to adapt the pattern without copying the source.
- Top three recommended ideas for this week.
Service angle: package this as weekly content intelligence for founders, creators, or agencies. Recurring research is more valuable than a one-time list of ideas.
5
Workflow 3: Real-time trend scout
Video timestamp: 7:06, prompt at 7:49Content opportunities decay quickly. A useful trend scout watches high-signal sources, filters aggressively, and alerts you only when the item is fresh, relevant, and actionable.
Exact prompt discussed in the video
Every morning at 8:00 a.m. check X, YouTube, Hacker News, and AI news sources for topics related to AI agents, Claude Code, OpenClaw, Hermes, and AI automation. Only send opportunities that are fresh, relevant, and actionable. For each one, include the source, why it matters, the recommended response format, and a draft hook.
Reusable prompt template
Every [SCHEDULE] check [SOURCES] for topics related to [KEYWORDS / PRODUCTS / INDUSTRY THEMES]. Only send opportunities that are fresh, relevant, and actionable. For each opportunity, include: source link, timestamp or publish time, why it matters, who should care, recommended response format, urgency level, and a draft hook or first paragraph. Do not send me generic news; filter for items I can act on today.
Recommended alert format
Opportunity: [short title]
Source: [link]
Freshness: [when it appeared]
Why it matters: [plain-English significance]
Who should respond: [creator/founder/agency/client]
Recommended format: [short, thread, video, blog, client alert]
Draft hook: [1-2 sentence opener]
Confidence: [low/medium/high]
Action window: [today / this week / monitor only]
Keep the agent as a scout, not the final taste-maker. It increases surface area, but you still decide what is worth sharing or reacting to.
6
Workflow 4: Polymarket and prediction-market research alerts
Video timestamp: 9:10, prompt at 10:13The video is explicit: do not start by letting an AI agent trade real money on autopilot. The useful workflow is research and alerts: watch markets, notice unusual movement, connect the move to news, and tell the human what to verify before taking action.
Exact prompt discussed in the video
Monitor these Polymarket categories for unusual movement: crypto, elections, AI, sports, and macro. Do not place trades. When a market moves more than 8% in 24 hours or volume spikes unusually, send me a brief with the market link, current price, possible reason for the move, related news, and what I should verify before taking any action.
Reusable prompt template with stronger guardrails
Monitor these prediction-market categories: [CATEGORIES]. Do not place trades. When a market moves more than [THRESHOLD] in [TIME WINDOW] or volume spikes unusually, send me a brief with the market link, current price, previous price, volume change, possible reason for the move, related news, conflicting evidence, and what I should verify before taking any action. Label each alert as low, medium, or high confidence. Never provide financial advice; provide research context only.
Threshold guidance
- 8% in 24 hours: sensitive, likely more alerts, useful for broad monitoring but can create noise.
- 25% in 24 hours: more selective, fewer alerts, better for avoiding notification fatigue.
- 25% in 1 hour: urgent anomaly threshold; useful only if you can respond quickly.
Safety note: alerts are not financial advice. Include “do not place trades,” require source links, and ask for verification steps before action. Real trading needs authentication, wallet controls, approvals, balances, order signals, risk controls, and many safety checks.
7
Workflow 5: Client operations and follow-up systems
Video timestamp: 12:40, prompt at 13:28Client ops may be the least flashy workflow, but it is often the most valuable. Founders lose time and trust when follow-ups, promised tasks, client preferences, and deadlines fall through the cracks. Hermes can turn messy notes into clean next steps.
Exact prompt discussed in the video
I just finished a client call. Turn these notes into a clean follow-up message, a list of actions, owners, deadlines, and reminders. Save the durable client preferences to memory, but do not save temporary task progress as a memory. Ask me before sending anything externally.
Reusable prompt template
I just finished a [CLIENT / PROSPECT / INTERNAL] call. Turn these notes into: 1) a concise follow-up message, 2) action items with owners and deadlines, 3) risks or open questions, 4) reminders I should schedule, and 5) durable preferences or facts worth saving for future work. Do not save temporary task progress as memory. Do not send anything externally until I approve it. Here are the notes: [PASTE NOTES].
Recommended follow-up output format
Follow-up message draft:
[ready-to-review email or chat message]
Action items:
- Task: [task]
Owner: [person]
Deadline: [date]
Status: [not started / waiting / scheduled]
Reminders to create:
- [reminder] on [date/time]
Durable preferences worth saving:
- [client preference or stable fact]
Do not save as memory:
- [temporary progress, one-off status, stale details]
Service angle: sell a founder/client assistant system that converts calls into follow-ups, reminders, owners, deadlines, and durable client preferences.
8
Turn the workflows into sellable packages
Qualified Lead Pipeline
Deliverable: weekly table of qualified accounts, fit reasons, personalization angles, and reviewed outreach drafts.
Buyer: agencies, B2B founders, consultants, freelancers.
Content Intelligence Brief
Deliverable: weekly top trends, winning hooks, competitor patterns, and three content briefs.
Buyer: creators, founder-led companies, social agencies.
Fresh Opportunity Alerts
Deliverable: daily or real-time alerts with response recommendations and draft hooks.
Buyer: creators, agencies, newsletter writers, community managers.
Research Alert Feed
Deliverable: monitored market/category alerts with movement, possible cause, related news, and verification checklist.
Buyer: analysts, traders, niche research communities.
Client Ops Assistant
Deliverable: call-note cleanup, follow-up drafts, action registers, reminders, and durable preference capture.
Buyer: busy founders, agencies, consultants, account managers.
Internal Operator Stack
Deliverable: one or more Hermes workflows that save your own team time before being sold externally.
Buyer: yourself first; then clients with similar operations.
9
How to verify each workflow is working
- Lead generation: at least 70% of the researched accounts should match the ICP, and each outreach angle should contain a company-specific reason rather than generic praise.
- Content research: each recommended idea should trace back to a visible pattern in the source examples, but should not copy a title or premise verbatim.
- Trend scouting: every alert should be fresh, linked, relevant to your keywords, and paired with a clear response format.
- Prediction-market alerts: every alert should show the threshold that triggered it, related news, uncertainty, and verification steps before action.
- Client ops: follow-up drafts should be sendable after review, action items should have owners and deadlines, and memory suggestions should contain only durable preferences or stable facts.
10
Troubleshooting common failures
The output is too generic
Add a sharper ICP, more exclusions, examples of good and bad fits, and a requirement for evidence links or company-specific reasoning.
The monitor is too noisy
Raise thresholds, narrow sources, require an action window, and ask Hermes to suppress items that are merely interesting but not actionable.
Outreach sounds spammy
Require short human-reviewed drafts, ban exaggerated claims, and ask for one specific observation about the company before any pitch.
Memory gets cluttered
Separate durable preferences from temporary status. Save stable facts only; put tasks and one-off progress in reminders, a CRM, or a project tracker.
11
Guardrails and quality checks
- Sell outcomes, not AI. The customer cares about qualified leads, better briefs, or fewer dropped follow-ups, not which agent produced them.
- Human approval before external action. Especially for outreach, client messages, trading, publishing, and account changes.
- Use memory sparingly. Durable client preferences belong in memory. Temporary task progress does not.
- Log sources. For research products, every claim should have a source link or a confidence label.
- Prevent alert fatigue. Tighten thresholds and filters when a monitor becomes noisy.
- Start with one workflow. The video's closing advice is to build one workflow that saves time or creates opportunities, then let that pay for itself.
- Sharbel A. — “5 Ways I Make Money With Hermes Agent”, uploaded 2026-05-18, retrieved 2026-05-20.
- Video description links mentioned by the creator: FREE YouTube Agent, FREE X Agent, and FREE Polymarket Copy Trading Agent.
- Hermes Agent documentation for commands, cron jobs, skills, memory, tools, gateway, and agent workflows.
This guide is transcript-derived and cross-checked against the local Hermes Agent skill reference for current command surfaces. The prompts are preserved as completely as the transcript allows, with expanded templates added for practical reuse.