Můj AI zaměstnanec v Claude — 3h práce za 15 minut

Core idea: “AI employee” = autonomous work with clear delegation (not just prompting)

The speaker argues that calling any LLM output an “AI employee” is misleading. A real AI employee/agent should:

• Have a trigger
• Perform the work on its own
• Produce functional, business-usable outputs without step-by-step human assistance

Calling output “an AI employee” is misleading unless the agent can execute a defined workflow autonomously and reliably.

---

How to delegate work to AI agents (3-step process)

1. Step 1 – Manual execution + verify it’s worth doing

   • Do the task yourself first to create a reliable method.
   • Output: a SOP (Standard Operating Procedure)—a step-by-step list describing how the activity should be done.
   • Warning: AI can tempt people to do unnecessary work just because it’s possible (“solve problems that don’t exist”).

2. Step 2 – Semi-automation using tools (AI assists, you still guide prompts)

   • Use AI tools like ChatGPT / Cloud Code to simplify substeps (e.g., collecting data, writing code, generating documents).
   • Goal: speed up without losing control.
   • Important: moving from step 1 → step 2 should bring real acceleration, not just more detailed output.

3. Step 3 – Agent automation (AI executes the workflow as specified)

   • An agent runs the SOP and handles the full process end-to-end (with optional human check points).
   • Strong recommendation: don’t skip steps 1–2; otherwise you risk building something messy that no one actually wanted.

---

Tooling guidance: what agent “types” to build

The speaker doesn’t push one “best” tool; instead, the focus is whether it works reliably and supports the delegation approach.

Scheduled agents

• Run at a set time and follow a complex workflow.
• Example preference: Cloud Code (especially for timed workflows).

Trigger-based agents

• Run when something happens (email received, notification, tagging in a project).
• Example preference: N8N (noted as widely documented with many tutorials and easy testing).

---

Why not rely on fully autonomous “black box” agents (yet)

• Solutions like OpenAI / OpenCl (as referenced in subtitles) or other fully autonomous systems are deprioritized.
• Reason: most businesses mainly need AI to execute your defined procedures with good oversight.
• Possible upgrade path:
  • After you have a base of working agents, an orchestration layer might help manage them all.

---

Demo/tutorial: “AI agent for a weekly newsletter”

A concrete workflow publishes an “EI Minute Newsletter” every Saturday by:

• Running on Friday at 3 PM
• Collecting notable AI-world items from the web
• Selecting the most relevant stories
• Producing:
  • A newsletter text file
  • A presentation for the community
• Indicating status so the person can proceed (e.g., record the video)

Architecture / components shown

• Warp as a terminal/editor to manage Cloud Code workflows
  • Workflow stored in a “messages” folder as .md / Cloud MD
• Cloud Desktop to schedule tasks and run them in the background

Workflow steps shown in the SOP

• Collect news
• Select interesting items
• Write newsletter
• Save output
• Summarize / prepare a presentation for the community

---

Human-in-the-loop vs full automation

Even when full automation is possible, the speaker prefers hybrid control:

• Agent collects options (e.g., ~60 stories)
• Human chooses which ~5 to include
• The system can use “bypass permissions” so it runs with fewer interruptions

---

Operational tips / risks

Bypass permissions mode

• Benefit: less disruptive (fewer/faster run interruptions, no frequent confirmation popups)
• Risk: the agent may perform dangerous actions (even irreversible ones)
• Mitigation: run with careful folder/workflow constraints

Hardware requirement

• The computer must be on and not sleep, since it runs code locally via Cloud Desktop
• For long automations, adjust sleep/suspension settings

---

Iterative improvement loop (like training a colleague)

After each run:

• Review what required edits
• Update the instructions (Cloud MD prompts/skills) so the agent learns preferences
  • Example: if output is too long, instruct it to shorten by a specific amount next time

This improves gradually with repeated weekly use.

---

Potential escalation: performance-aware newsletter generation

The speaker suggests connecting newsletter/email tooling (via MCP) so the agent can:

• Analyze performance of previous newsletters (length, headline, etc.)
• Improve subject matter/title and messaging based on results

This same idea could extend to other business areas (e.g., offers) by comparing what performed well vs poorly.

---

Key product/learning takeaway

The biggest benefit isn’t “autonomous AI replacing you,” but hybrid automation:

• Human provides judgment/inputs
• AI handles heavy drafting, structuring, and background execution

Claimed efficiency gain in the newsletter example:

• ~3 hours → ~15 minutes

---

Main speakers / sources

• Speaker: Vojta (introduced as “Hi, I’m Vojta, the best AI specialist in our office”)
• Tools/platforms referenced: Claude (in video title), Cloud Code, Cloud Desktop, Warp, n8n, ChatGPT, MCP servers/connectors