PTENES
Skip to content
MODULE 3.4

🧱 Ready-made agents and workflows

A skill does one task. A workflow does one entire job — several steps linked together, from start to finish. Here you get ready-made templates to copy, adapt, and plug into your Jarvis.

6
Topics
~55
Minutes
Advanced
Level
Practice
Type
Progress in this module0%

0 of 6 sections read

💡 New here? Three words before you start

  • Workflow — a sequence of automatic steps: it does A, then B, then C, without you having to move it from one to the next.
  • Subagent — an AI specialized in just one thing (researching, reviewing, writing) that your main agent calls when needed.
  • Template — a ready-made template. You copy it, replace what’s yours, and use it. You don’t build from scratch.
1

🔄 What Is a Workflow: Linked Steps

A skill is a ask: it does one thing well. A workflow is the recipe: it links several pieces in order, and the result of one step becomes the input for the next. Instead of copying the result from one place to another, the workflow does it automatically.

Think of ordering food through an app: you tap once, and a series of steps happens behind the scenes — confirms the payment, alerts the kitchen, calls the delivery driver, and sends you the status. You don't handle each step yourself. An AI workflow is the same idea, but for work: search → check → summarize, or idea → text → image, chained together.

🔑 The central idea

The difference between a task e a job:

  • •Skill (one task): "summarize this text" → the summary comes back. Done.
  • •Workflow (a task): "research the topic, check the sources, and give me a report" → multiple steps, one final result.
ONE WORKFLOW · one’s output becomes the next one’s input 📥 inputyour request 🔎 step 1search ✅ step 2check 📄 resultsummary ready You trigger it once at the start; the steps run in sequence until the result is ready.
Each box is a step. The arrows show the sequence: nothing is copied by hand between them—the flow carries the result forward.

Key concepts

📌 Skill = building block · workflow = recipe
📌 One's output = the next one's input
📌 You handle one time
📌 Make a work, not a tiny task
2

🧩 Ready-made subagent templates

A subagent is an AI with just one role. Instead of asking one generic AI to do everything, you build a small team: one that just research, one that just reviews, one that just writes. Each one does their part better because they have a narrow, clear instruction.

The good news: you don't have to invent these roles. There are ready-made templates — standard descriptions of “what this agent is, what it does, and what it doesn’t do.” You copy the template, tweak a detail or two, and you’ve got your team member.

✓ A good subagent template

  • ✓Has one role (researcher, reviewer...)
  • ✓Says what to do and what not to do
  • ✓Defines how to deliver the result
  • ✓It’s short — it fits in one paragraph

✗ A bad template

  • ✗"Do everything" — an unfocused role
  • ✗Without limits: it doesn’t know what to avoid
  • ✗Doesn’t say what the expected deliverable is
  • ✗Huge and confusing

💡 Practical tip

Start with two or three subagents, not ten. A researcher, a writer, and a reviewer already cover most jobs. More agents mean more things can go wrong. Grow the team only when you feel the need.

Key concepts

📌 Subagent = single role
📌 Template ready to copy
📌 Say what to do e what to avoid
📌 Start with 2–3, not 10
3

🔬 A Ready-to-Use Research Workflow

The research workflow is the “Columbus’s egg” of workflows: three simple steps that, together, save you hours. Search the sources, check whether they’re reliable and agree with each other, and summarize in a report with the sources noted. Each step has a clear purpose.

The middle step — checking — is what separates research from rumor. That’s where the workflow discards anything without a source and flags anything uncertain. Without it, all you have is a polished summary of something that may be wrong.

🧪 Workflow ready to copy (research in 3 steps)

Goal: go from a vague topic to a short report with sources—without manually reading ten tabs. Paste it into Claude or ChatGPT, replacing what’s between < >.

Você é meu agente de pesquisa. Faça este workflow em 3 passos,
me mostrando o resultado de cada passo antes de seguir:

TEMA: <o que você quer pesquisar, ex: melhores planos de celular pré-pago>

PASSO 1 — BUSCAR: liste de 4 a 6 fontes recentes sobre o tema,
com o título e o link de cada uma.

PASSO 2 — CONFERIR: para cada fonte, diga se é confiável e se
concorda com as outras. Descarte as duvidosas e me avise quais.

PASSO 3 — RESUMIR: escreva um relatório de 1 página com:
  - 3 a 5 conclusões principais (cada uma com a fonte ao lado),
  - 1 ponto em que as fontes discordam,
  - o que ainda ficou em aberto.

How to verify it worked: the final report should have sources next to each conclusion and cite at least one disagreement. If you get a smooth text with no sources, step 2 was skipped — ask it to redo the check.

💡 Practical tip

Ask to see the result of each step before the next one. That way, you catch problems early: if the sources in step 1 are already bad, there's no point in summarizing. Checking along the way is cheaper than finding the error at the end.

Key concepts

📌 Search → check → summarize
📌 Checking is the step that matters
📌 Source next to each conclusion
📌 Review each step before the next
4

🎨 A ready-to-use content workflow

Creating content from scratch is tiring. A workflow turns it into a production line: idea → script → text → image. Each stage delivers something concrete that the next one uses — the outline guides the text, the text suggests the image. You provide the idea and review things at the handoff points.

The image below is the blueprint for this pipeline. Notice that it's not magic: it's the same chaining logic from topic 1, applied to creative work. The value is in not starting from scratch with every post.

Illustration of a content production line: an idea goes in one end and comes out as a linked sequence of script, text, and image, representing a ready-to-use workflow.
A content production line: the idea goes in, and the workflow carries it through to the finished post, step by step.

🏭 The 4 stages of the line

  • 1.Idea: you (or an agent) define the topic and audience.
  • 2.Script: the AI builds the structure—title, topics, call to action.
  • 3.Text: writes the content following the outline.
  • 4.Image: suggests/generates artwork that fits the text.

You review between stages. Did you approve the outline? Move on to the text. Don’t like it? Make adjustments before spending the rest.

Key concepts

📌 Idea → script → text → image
📌 Production line, not improvisation
📌 Review at handoffs
📌 It doesn't start from scratch with every post
5

🪡 Adapt a template to your workflow

The template is the skeleton; you add the substance. Adapting means changing three things: the tools (where it searches, where it saves), the steps (remove what you don't need, add what's missing) and the delivers (the format you want at the end). There's no need to rewrite the workflow — just adjust these pieces.

Golden rule: change one thing at a time and test. If you change everything at once and it breaks, you won’t know which change caused it. Small adjustments, one at a time, keep control in your hands.

1

🔧 Swap the Tools

Where the template says “search the web,” point it to your drive, your spreadsheet, your email.

2

➕ Adjust the steps

Remove a step that doesn’t work for you, add one that’s missing (e.g., “translate into Portuguese”).

3

📦 Define the Deliverable

Specify the final format: email, post, spreadsheet, audio. Same workflow, different output.

4

🧪 Test one change at a time

Did it change? Run it. Did it work? Next one. Did it break? You know exactly what happened.

TEMPLATE · skeleton 🔎 search (web) 📄 save (generic) 📤 deliver (text) adapt YOUR WORKFLOW · with substance 🔎 your spreadsheet 📄 your drive 📤 your email
The skeleton (on the left) stays the same; you just replace each box with the your tools (on the right). That's how you adapt a template.

Key concepts

📌 Template = skeleton; you add the flesh
📌 Change the tools, steps, deliverable
📌 One change at a time
📌 Test after every adjustment
6

🔒 Chain Safely

The longer the workflow, the more chances a small mistake can snowball. The fix is simple: checkpoints between steps. Before an action that affects the real world—sending an email, deleting a file, spending money—the workflow pauses and asks for your OK.

The practical rule: steps that only read or draft can run on their own; steps that make a real difference require confirmation. This keeps the workflow fast, but nothing irreversible happens without you seeing it.

✓ It can run on its own

  • ✓Search for and read information
  • ✓Draft a text (without sending it)
  • ✓Summarize, organize, compare
  • ✓Generate a suggestion for you to review

✗ It asks for your confirmation

  • ✗Send an email or message
  • ✗Delete or overwrite files
  • ✗Spending money / shopping
  • ✗Publish something for the public

🎯 The habit that saves you

Whenever you build a new workflow, ask: "which step here is irreversible?". This is the step that adds a checkpoint. Everything else can run on its own.

Key concepts

📌 Checkpoints between steps
📌 Read/draft = on your own
📌 Real change = requires OK
📌 Mark the irreversible step

✋ Before you continue — what sets a workflow apart from a standalone skill?

🎓 Module summary

✓
Workflow = linked steps — one becomes the next one’s input, and gets a whole job done.
✓
Has ready-made templates — subagents with a single role and research and content workflows to copy.
✓
Adapting means replacing parts — tools, steps, and delivery; one change at a time.
✓
Chain things together safely — checkpoints before any irreversible step.

Next module:

3.5 — ⚡ Automation and triggers: how to get your Jarvis to act on its own, at the right time, without you asking.