Your module's agent is a new team member. On day one it's smart, but it doesn't know your work. You give it three things:
| Think of it as | Example | |
|---|---|---|
| Tools | Its hands: the actions it can take. | Log a visit, look up a customer, create a work order |
| Skills | Its training binder: how your company does things, step by step. | How we triage a support request |
| Scripts | Its power tools: code it runs for jobs that need precision. | Read a spreadsheet, convert a drawing, check a schedule |
Tools: what it can do
Each tool is one action, like create a work order. The platform wraps every tool with the safety checks: the agent can only do what the person it's helping is allowed to do, only in your workspace, and every action is recorded. The platform also has tools of its own you can hand your agent, like reading files someone shared from their PC. See Agent tools.
Skills: what it knows
A skill is a short guide written in plain words: when to use it, the steps, and the rules. The agent reads it only when the job calls for it, so you can give it lots of skills without slowing it down. A skill can carry reference notes and templates too. See Skills and scripts.
Scripts: when it has to be exact
Some jobs shouldn't be guessed: adding up a column, reading a file format, checking dates. A skill can include a script that does it exactly, every time, with any libraries it needs.
Tips from the pros
- One tool, one job. Create a work order and close a work order, not do work orders.
- Write skills like you'd train a new hire. What good looks like, what to never do, and who to ask.
- Ask the Module Builder: "give the agent a skill for how we schedule crews".