Choose the right automation
Decide whether the work needs a Skill, Macro, Trigger, or Agent before building it.
Start with what begins the work
Choose the smallest kind of reuse that fits the job:
| If you need Jarvis to… | Choose | Example |
|---|---|---|
| Follow the same business rule | Skill | Use the agreed tone for overdue reminders |
| Repeat several steps in order | Macro | Run the month-end review checklist |
| React when a record changes | Trigger | Review a large invoice when it is submitted |
| Check a defined area as a specialist | Agent | Propose bank matches and raise exceptions |
A simple decision path
- If only the rule repeats, make a Skill.
- If several prompts repeat, make a Macro.
- If a record event must start the work, make a Trigger.
- If the work needs a packaged specialist with runs and findings, use an Agent.
A Skill can be used inside a Macro. A Trigger may begin work that uses a saved instruction. An Agent may prepare work that still returns to a person. These features can work together, but each should have one clear job.
Do not automate an unclear process
Write the current owner, start, finish, exception, and review point first. If two experienced people disagree about the right outcome, automation will repeat the disagreement faster.
Start with one ordinary case and one exception. Keep a new Trigger narrow, run a new Macro manually, and check the first Agent run before setting a schedule.
Keep people at the decision
Scheduling or reusing work does not remove its safety boundary. Important and hard-to-reverse actions still require a person. An ordinary reversible action can proceed only when the workspace and current conversation allow it.
Automate the preparation before the judgment. A short, well-evidenced exception list is often more valuable than trying to automate the final decision.
See complete examples
Use the playbooks for month-end close, large invoice review, and bank reconciliation.