#Automations

Teach Arachne a task once, then run it again whenever you need it — on demand, without re-explaining a thing.

#Overview

Some work is one-of-a-kind. Much of it is not. When a task is something you will reach for again — the same kind of research, the same flow filled out, the same thing built and checked — you should not have to describe it from scratch every time. An automation captures that work so you can run it again on demand.

With Arachne, you describe an outcome in plain language and it carries the task through across real websites and applications, verifying each step. An automation takes one of those tasks and makes it repeatable: the goal is remembered, and you trigger it when you want it. The work still runs the same careful way — look, decide, act, verify — but you no longer pay the cost of explaining it each time.

#What you can do

  • Turn a task you have already run into a repeatable automation, so the next run is a single request instead of a full explanation.
  • Run an automation on demand whenever you need that outcome again.
  • Keep the routine work you do often ready to go, rather than rebuilding the request from memory.
  • Save a particular way of doing something as a reusable skill you invoke later by name — a close companion to automations for the steps you repeat most.
  • Run automations at the permission level that fits, so repeated work stays in your control even when it is hands-off.
  • Find the result of every run as an artifact you can reopen, reuse, and export.
Note

Automations and saved skills work together. An automation is a whole task made repeatable on demand; a saved skill is a particular way of doing something that you invoke by name. Use an automation for the outcome you want again, and a saved skill for the move you want to reuse inside many tasks.

#How to use it

  1. Run the task once, well. Describe the outcome you want clearly — the result, any links or constraints you already have, and the format you expect. Let Arachne find the path and verify the work. A clean first run is the foundation of a clean automation.
  2. Turn it into an automation. Once the task does what you want, ask Arachne to make it repeatable. The goal is captured so you can call on it again without describing it from scratch.
  3. Choose how much freedom it has. Set the permission level for the automation the same way you do for any task — Look only, Plan first, Ask before acting, Work in your workspace, or Act automatically. For routine work you trust, a higher level lets it flow; for anything sensitive, keep yourself in the loop.
  4. Run it on demand. When you need the outcome again, trigger the automation. Arachne does the work the same careful way and reports back with a result you can see.
  5. Watch the first repeat. The first time you run an automation again, keep an eye on it so you can confirm it still does exactly what you intended. After that you can let it run with more confidence.
  6. Adjust in plain language. If what you want has shifted, tell Arachne what to change. You refine the automation the same way you refined the original task — by describing the difference, not the machinery.
Tip

If a task has a step you find yourself repeating across many different jobs, save that step as a skill you can invoke by name. Skills keep your automations lean and let you reuse a proven move anywhere.

#Examples

Make a recurring research task repeatable

text
Pull this week's headlines for my three competitors, compare them side by side,
and flag anything that mentions a price change. Save this so I can run it again.

You see a comparison of the three competitors with price-change items raised as alerts — and a saved automation you can run again next week with a single request.

Run a saved automation on demand

text
Run my weekly competitor scan.

Arachne carries out the task it already knows, verifies each step, and hands you the up-to-date comparison and any alerts as a fresh result you can reopen and export.

Reuse a flow you complete often

text
Fill out the intake form on this site the way I usually do, then save this so I
can do it again for the next client.

You watch the form completed end to end, with a pause for your approval where you asked for one, and you get a saved automation ready for the next time you need the same flow.

#Tips

  • Get the first run right before you make it repeatable. An automation faithfully repeats the task you captured, so a clear, verified first run gives you a reliable automation.
  • Describe the outcome, not the steps. Say what the result should be and what matters in it; let Arachne find the path each time it runs, so the automation keeps working even as the web changes.
  • Match the permission level to the work. Routine, low-risk tasks can run at a higher level for speed; anything that changes something important is better kept at Ask before acting or Plan first.
  • Lean on saved skills for the moves you repeat across many tasks, and on automations for whole outcomes you want again — together they keep your routine work fast and consistent.