Keeping going
The first is how to work through a long job without stopping to check in after every step. Left alone, an assistant tends to do one piece of work and hand it back. That’s right for a quick question and wrong for “go through these 40 records”. This skill is what lets your coworker recognise the second kind and keep going until the job is genuinely finished — deciding for itself when to press on and when it’s actually done. You can invoke it directly with/loop. See Keep working.
Driving a browser
The second is how to use a real browser properly: reading a page before acting on it, finding the right control rather than guessing, recognising a login screen, and handing over cleanly when it hits one. This is the difference between a browser that works on real websites and one that clicks hopefully. It’s why the live browser copes with sites it has never seen.This skill only matters when the live browser capability is switched on. With it off, your coworker simply never reaches for it.
Good to know
Built-in skills can’t be edited or deleted — they’re part of what a coworker is. Your own skills sit alongside them.
Common questions
Do these count against how many skills I can add?
Do these count against how many skills I can add?
No. Add as many of your own as the job needs.
Can I stop my coworker using one?
Can I stop my coworker using one?
Not directly, and you rarely want to. To stop the browser skill mattering, switch off the live browser capability. To stop a long autonomous run, tell it to stop.
Can I write a skill that overrides one?
Can I write a skill that overrides one?
You can write a skill covering the same ground, and your coworker follows the more specific one when it applies. That’s a reasonable way to impose your own rules on a long-running job.
Next steps
Keep working
The first one, in use.
The live browser
The second one, in use.
Creating a skill
Add your own.
What skills are
Back to the basics.