This page requires JavaScript to display.
The Nolan Scott Team Sells and buys businesses from $1M to $15M+, and advises on the real estate that comes with them. nolanscottteam.com →
Example 10 / 18 · a sample from our Rolodex of 100+ automations Claude Skill
Automation Breakdown · Claude Skill

Daily Ops Assistant

The default day-to-day operator: one assistant wrapping Gmail, Google Calendar, Close CRM, and Calendly with the house operating conventions baked in. Open-ended questions get an interactive daily dashboard; specific asks get handled directly, email drafted, event created, lead updated, conventions applied silently.

4 systems, one assistant
2 modes · dashboard or task
voice input, interpreted generously
0 emails sent · drafts only
True AI automation isn’t one clever workflow. It takes 20 to 40 workflows working together to make a real impact on a business. That’s what we do: a Rolodex of 100+ automations across different CRMs and platforms, ready to be custom-built for your specific CRM and software stack.
The Workflow
Scroll sideways · click any step for its explanation
status?
task
The default skill
Any operational task across Gmail, Calendar, Close, or Calendly runs through here, even when Victor doesn’t ask for “the dashboard” by name.
Voice-first
Victor often dictates from the car between meetings. The skill reads it generously, acts, and keeps the output scannable for desktop later.
Draft only, always
The assistant never sends an email. Drafts land in Gmail; Victor pulls the trigger.
▶
Victor Asks
often by voice
A\
Interpret the Ask
generous with voice
⇄
Dashboard or Task?
the fork
{ }
Pull the Day
5-step sweep
▦
Render Dashboard
locked visual format
{ }
Load Domain Rules
only what’s needed
M
Draft Email
never send
31
Calendar Event
emoji prefixes
C
Close CRM Update
individual names
Cy
Calendly
right link, right person
{ }
Apply Conventions
silently
{ }
Tight Handoff
one line
A\
Honest Read
pushback welcome
◈
The assistant at a glance
Click any step to see exactly what it does. The flow reads left to right: interpret the ask, fork to dashboard or task, act across the four systems with house rules applied, hand back in one line.
Gmail
Google Calendar
Close CRM
Calendly
Dashboard widget
Claude reasoning
Logic / rules
Trigger
How It Works

Dashboard or task, conventions either way

01 · Route the Ask
Two modes, one brain

“Morning brief” and “where do things stand” render the full interactive dashboard. “Draft a reply to Arianna about Doraville” skips it and just does the task. Dictated, run-on phone messages get interpreted generously, names and deals resolved against memory and Close before anything is asked.

02 · House Rules
Conventions applied silently

Every action carries the operating conventions without narrating them: email format and signature block, no em dashes, calendar events with their emoji prefixes, Close leads under the individual’s name with the BUSINESS BROKER tag, the right Calendly link for the right audience. Each domain’s rules load only when that domain is touched.

03 · Hand Back
Tight handoffs, no recaps

Nothing sends without Victor, emails stay drafts. Every task ends with a one-line handoff (“Draft is in Gmail. Event created Thursday 2pm, conflicts with the Hammock lunch, move one?”), direct and scannable for catching up on desktop later. Pushback over agreement; no filler.

Next example: OM Deal Reviewer →
AI · nolan scott team
Unpacking...