Teach a task the smart way: describe it first, record only t

How this helps you

You get a reliable skill from a short clip, and rules that stop it doing the wrong thing on bad days.

✦ Try it

Add these rules to [skill name]: If there's nothing new since the last run, reply 'no new activity' and stop. This is read only: never post, like, reply or message unless I ask. If the site is logged out or shows a captcha, stop and tell me. Never write a specific date, post or person's name into the steps; always use what's new that day. Then repeat the full steps back to me.

Fill in: [skill name] is the skill the Bot made from your demonstration. Change 'read only' if the job does need to act, and list exactly which actions are allowed.

What they did

Kacper Rutkiewicz uses Teach a task on a site with no API. He found the recording is the small part. Teach a task records the Bot's cloud computer (not yours) for up to 10 minutes: clicks, typing and pages, with no sound, and it doesn't know why you clicked. So he writes the finish line in chat first, lets the Bot try, gives feedback with a screenshot of a perfect result, and records only what it still can't do (his was about 20 seconds: adding a GIF and picking a category). The built-in learn from demonstration skill turns the clip into a skill. For a daily community report he then added anti-jobs: say no new activity when there is none, stay read only, stop and tell him if logged out or shown a captcha, and never hard-code a date, post or name.

Who it's for: Anyone automating a website that has no connector: community platforms, old admin panels, niche ticket systems.

Before you start

Check first that no plugin, API or MCP connection exists for the site. If one does, skip the browser.
Log in on the Bot's computer before recording. Never type a password while recording.
Remember all your Bots share one computer, so a login there is visible to every Bot.

How to try it

Write the finish line in chat: what the result looks like, the sections, and what the Bot must never do.
Let the Bot try. Send a screenshot of a good result and say what's missing.
Record only the step it still gets wrong: open the Bot's computer, click Teach a task, do the step, stop.
Ask it to repeat the steps of the new skill back to you, and correct them.
Run it by hand two or three times on safe inputs, add anti-jobs (the prompt below), then make it a routine.

What to expect

The Bot replies with the updated numbered steps and the four rules at the end. On a quiet day the routine sends a one-line 'no new activity'.

Common mistakes

Talking through the recording. There's no audio; put the why in writing.
Recording a 20 minute job. Split it into small skills and chain them.
Turning it straight into a routine. Kacper's Bot made a routine without being asked; say 'skill first' and schedule only once it's proven.

Related tips

Teach a task by doing it once: Do the workflow while it watches; it records the steps.
Do it by hand, save a skill, then schedule: Most automations break because they're scheduled before they've worked once.
Connectors before the browser: One task got about 45x cheaper by switching to a connector.