←BaldanAll skillsLet's talk

Skill 06 · Automation & AI Agents

Work that runs itself.

Automation is software doing the repetitive work: on a schedule, when something happens, or when you ask in plain words. Here is every way it's done, from a ten-line script to an AI agent, shown with things that actually run in your browser.

PythonPlaywrightn8nPower AutomateUiPathAirflowGitHub ActionsLLMsMCPOpenRouter
Open the workflow lab

Running right now

This page is running an automation.

A real one, in your browser: it listens to every change made across Wikipedia and its sister sites, keeps the article edits, and alerts on new pages and big changes. Start it, then change the rule while it runs.

Readya real automation, in your browser

When

anything changes on any Wikimedia site

0

If

it's an article edit on a Wikipedia in any language

0

And

it's a new page, or ≥ 3,000 bytes changed

0

Then

post an alert below

0 alerts

Change the rule while it runs:

Press start: alerts appear here as real changes match the rule, usually within seconds. The languages of Indonesia are much quieter, so expect long waits with that filter.

Real changes from Wikimedia's public EventStreams feed, read directly by your browser. Page titles, usernames and comments are dropped on arrival; nothing is stored. Pauses itself after 90 seconds.

01 · One chore, six ways

The same morning chore, automated six ways.

Every morning: get yesterday's orders from a supplier portal, add them up per store, update the sales sheet and tell the team. The four steps keep their colour, so you can watch who does the work change.

Python scripton a small serverSupplier portalwebsite onlySales sheetGoogle SheetsTeam chatWhatsApp · Slack07:00cronYouevery morningRobotclicks like a personAI agentan LLM choosing toolsRun historyevery run, retry and log lineAsk a human when unsureguardrail: an approval stepDownloadlog in, export to ExcelAdd upper store, by handPasteinto the sales sheetMessagetype it to the teamlog in
1/6

You remember, open the portal and log in.

Swipe the drawing sideways to see all of it.

The chore, before

By hand

The same clicks every single morning, done by a person who has better things to do.

Starts when
you remember to
Reaches systems through
the screen
Who can build it
anyone
Breaks when
you're busy, ill, or make a typo

Often done with

BrowserExcelChat app

02 · Rules or reasoning

Where rules end and judgement begins.

Most automation follows fixed rules, and that's a strength. AI earns its place only where a task needs reading, writing or judgement. Slide to see what changes.

fixed rulesopen-ended judgement

Fixed rules

Use plain automation: it's exact, cheap to run and easy to test. Most automation lives here.

Fits here: RPA bot, Pipeline, No-code workflow

Same input, same output
always
Cost per run
next to nothing
When it goes wrong
loudly, with an error
How you test it
ordinary tests

0 good calls of 0 answered

Pick the kind of automation you'd use for each task.

01Back up the database every night at 2 am.

02When someone fills in the website form, add them to a sheet and send a welcome email.

03Type 300 invoices into an old desktop accounting app that has no API.

04Read customer emails, work out what each one wants and draft replies for a person to check.

05Every night, pull sales from five systems, clean them and rebuild the dashboard tables.

06Sort incoming support tickets by topic and urgency.

07Run the tests and publish the website every time code is pushed.

08Download a report from a supplier's website every morning. It has no API.

03 · Worth it?

Is it worth automating?

Building takes time, and so does keeping it running. Put in how often a task happens and how long it takes, and see when the automation pays for itself.

How often is it done?

How long does it take by hand?

Upkeep is the part people forget: logins expire, a website changes, an API is renamed.

0 h32.9 h65.8 hby handautomatednowmonth 6month 12month 18month 24

By hand, per month

2.5 h

Pays for itself after

10.4 months

Saved over 5 years

76.2 h

Max worth building (5 yrs)

6.3 days

How long you can spend making it faster and still come out ahead over five years
how often ↓ · time saved →1 sec5 sec30 sec1 min5 min30 min1 hour6 hours1 day
50× a day
5× a day
Daily
Weekly
Monthly
Yearly

Your numbers, simple arithmetic: time by hand × how often, against build time plus monthly upkeep. The grid idea comes from xkcd 1205, “Is It Worth the Time?”; the values are computed here. It counts hours only: automation also removes typos, runs while you sleep and doesn't forget.

Explore

Go deeper.