Skills & Automations

Teaching It New Tricks.

A one-off ask is useful. A saved skill is leverage. A scheduled skill is work that happens without you. This page is how you move from the first to the third. And why the compound gets brutal after month two.

Skills

A skill is a recipe. A set of instructions that teaches your agent how to handle a specific task the same way every time. Without skills it's a capable conversationalist. With skills it's a specialist who produces structured reports, runs multi-step workflows, and interacts with external services on your behalf.

Auto-activated

No menu. No slash command. You describe what you need in plain English and your agent selects the right skill on its own. Often chaining two or three in a single turn.

Role-tuned

Your agent ships with skills pre-seeded for your profession. A mortgage broker's skill library looks nothing like a conveyancer's, and neither looks like an FX compliance officer's.

Permanent

Once a skill exists it stays. It survives context resets, restarts, and Monday mornings. Teach your agent once and it has the skill for every client afterwards.

Compounding

Every skill you save raises its baseline. What started as a twenty-minute walkthrough becomes a three-second automatic behaviour. And the next workflow builds on top of that floor.

How a Skill Fires

You don't invoke skills by name. You describe the outcome you want and your agent picks the tool. One message can trigger two or three skills in sequence. It plans the chain and reports back what it did.

you Generate a report on 42 Bridge Rd Richmond and email it to David.
it I'll pull the Richmond VIC report and send it to david@agency.com. That's two skills: property report and email delivery. Confirm and I'll ship.

One sentence, two skills, one confirmation gate. The chain is visible before it moves.

Save a Workflow as a Permanent Skill

The highest-leverage move you can make with your agent: when you figure out a workflow together. A way of formatting a report, a sequence for onboarding a client, the three checks you always run before a listing goes live. Tell it to save the workflow. Next time, it fires automatically.

Saved skills are the compound. Every one you save turns a twenty-minute walkthrough into a three-second automatic behaviour. By month three your agent has a skill library you did not build top-down. It grew from the work you actually do.

you That onboarding flow we just walked through. Save it as a skill so you run it automatically next time.
it Saved as Client Onboarding. Next time you say "onboard a new client" I'll run the same seven steps and surface the same three checks.

Your Skill Library

Every workspace ships with a role-tuned starter library and grows from there. Click the Skills icon in the room header to see everything your agent has. You don't activate skills from this panel. It's a reference view. Your agent uses skills automatically when the message calls for them.

Email summarisation

Triaged by sender, contract-urgency, and deadline pressure. Not chronological. The one that actually matters goes first.

Report generation

Structured output in the format your clients expect. Citations, timestamps, source documents. Nothing hand-waved, nothing uncited.

Compliance check

Runs a file against your regulatory checklist. Section 32, AUSTRAC, Tranche 2, whatever your profession demands. And returns a pass/fail per line with evidence attached.

Cron Jobs

A cron job is a skill on a timer. Set it once; your agent runs it forever on the schedule you named. The output posts to your room when the job fires. A morning briefing waiting for you at 8am, a weekly recap every Friday at 5pm, a compliance scan at 6am the day before settlement.

Runs while you sleep

Cron jobs fire whether you're at your desk or not. The 6am briefing is ready before your first coffee. The Friday recap lands before you close the laptop.

Plain-English schedule

Tell it "every weekday at 8am" or "the first Monday of each month": it parses the cadence, confirms it back to you, and sets it up. No crontab syntax, no timezone maths.

Full capability at runtime

When a cron fires your agent has every skill, every integration, and its full memory available. A scheduled compliance scan can read your inbox, check your CRM, and post a flagged list back to the room.

Outputs land in your room

Cron results post to your chat like any other message from your agent. Nothing to check, no inbox to babysit. You review it when you arrive.

Scheduling a Job

Describe what you want done and when. Your agent parses the cadence, confirms the schedule, and sets it up. No crontab syntax required.

you Every weekday at 8am, check my calendar and any overnight emails and post me a morning briefing.
it Done. Morning Briefing runs Mon-Fri at 08:00 AEST. I'll lead with anything contract-urgent, then calendar, then the rest.
you Every Friday at 5pm send me a recap of the week. Settlements closed, deals in flight, anything blocked.
you Daily at 6am, run a compliance scan over every active file and flag anything outside the checklist.
you Check my inbox every two hours and ping me if anything looks contract-urgent.
you First Monday of each month, run the portfolio review skill and email the output to the team.

Managing What's Running

Click the Cron Jobs icon in the room header to see every scheduled task with its next-run time. Or ask your agent in chat. List, modify, pause, remove, or fire-now, all in plain English.

List jobs

"What cron jobs are running?": it returns the active list with next-run times.

Modify a job

"Push the morning briefing to 9am.": it edits in place and confirms the new schedule.

Pause or remove

"Pause the weekly recap." / "Remove the compliance scan.": it acts and logs the change.

Run now

"Run the morning briefing now.": triggers once immediately, schedule untouched.

Pre-Seeded for Your Profession

Day-one skill libraries aren't generic. Your agent ships knowing the regulations your profession actually lives under. Not a scraped summary, but a working checklist it runs against real files.

Real Estate

Section 32 check

Feed it a vendor statement and it cross-checks every disclosure against the VIC Sale of Land Act. Missing title, unregistered easement, absent planning certificate. Flagged, cited, timestamped.

AUSTRAC TTR flagging

Your agent watches incoming deposits and earnest money against the $10k threshold. Anything that crosses. Or any structuring pattern that smells like avoiding it. Surfaces with the transaction trail attached.

FX & Remittance

s.26K filing

Your agent assembles the s.26K suspicious matter report from the customer file, transaction history, and your own notes. Ready for your review before submission to AUSTRAC.

Tranche 2 readiness

Your agent walks your client onboarding against Tranche 2 requirements as they mature. Beneficial ownership, enhanced due diligence, PEP screening. And tells you exactly what's missing before the regulator does.

Legal & Advisory

Contract review & clause extraction

Reads contracts, flags non-standard terms, extracts key dates and obligations into structured summaries.

Regulatory deadline tracking

Maintains a live calendar of filing deadlines, compliance windows, and renewal dates. Alerts before they arrive, not after.

Client communication drafting

Drafts advice letters, disclosure notices, and follow-up correspondence in your firm's voice. Always requires your approval before sending.

Medical & Allied Health

Patient correspondence

Drafts referral letters, follow-up summaries, and appointment confirmations. Privacy-gated per practice policy.

Clinical document processing

Reads lab reports, discharge summaries, and specialist letters. Extracts key findings into structured notes.

Medicare & billing compliance

Flags billing anomalies, tracks item numbers against service records, maintains audit-ready documentation.

Where the Value Compounds

The arc is three stages, and each one multiplies the last.

Stage One

One-off action.

You ask, it does it, you review. Useful. Twenty minutes saved. A transaction.

Stage Two

Saved skill.

The same ask takes three seconds from then on. It runs the same steps every time, citing the same sources. A floor.

Stage Three

Scheduled cron.

The skill runs on a timer whether you're at the desk or not. Work happens without you. This is where the compound starts to hurt. In the good way.

One-off action → saved skill → scheduled cron. By month six your agent is doing things you don't remember asking for. Because you only asked once, and the asking became the saving, and the saving became the schedule. Nothing is re-explained. Nothing is re-triggered. The floor keeps rising.

Where to Go Next