Now booking new clients Lake Charles, Louisiana
Free resources › AI skills and routines
Free download

Turn the job you repeat every week into a skill, then a routine.

The four steps from our video, from a chat to custom software, with a guide to find which one you're on. Plus a blank skill built the way ours are, three starter skills for a local service business, and the six routines we showed, each drawn as when it runs, what it opens, what comes back, and who checks. Hand the folder to Claude and it saves your first skill with you, and only suggests a schedule once you trust it. Made in Lake Charles, Louisiana.

Get the download

We'll email you the link. It's free, and the files are yours to keep.

The link comes from nick@redwaterrev.com. You'll also get our newsletter on using AI in a local business. Every one of those emails has a one-click unsubscribe. This browser remembers your email, so your next download is one click. See our privacy policy.

The four steps

From a chat to custom software, one step at a time.

The one rule for the whole climb: prove it by hand first. Automate a job you haven't proven, and you just do the wrong thing faster.

Step 1

Try it

A chat window, one question at a time. Good for learning what you're bad at, thinking out loud, and first drafts. But it starts from zero every time, because it doesn't know your business. This is where most people stop.

Step 2

Skills

A saved recipe for a job you repeat: how to do it, what good looks like, and how to check it. One line runs it, and it comes out the same way every time, whoever on the team runs it.

Step 3

Loops and routines

A skill that runs on its own, on a schedule or when something happens. The work gets done without anyone asking for it, and a named person checks what it did.

Step 4

Custom software

Its own database, an app on your team's phones, and direct links to QuickBooks, Square, and the phone system. The whole team works in one place, and the AI works inside it.

Which step does this job belong on? Pick one job you do often and read down this list. It's a guide, not a test.

Our morning research brief climbed this way. It started as a skill Nick ran by hand each morning, and it built the brief the same way every time. Then he forgot to run it on six days in one month. Forgetting is the sign it's ready. Now it's a cloud routine set for 6 every morning, with an alert if it's late. A job earns the next step by working on the one it's on.

Skills

A skill sounds fancy. It's just a folder.

One folder per job you repeat, with a plain-English file that tells your AI when to use it, what to ask, the rules, and the steps. Here's the shape, modeled on the skill we write proposals with.

.claude/skills/call-notes/one folder per skill
├─ SKILL.mdwhen to use it, what to ask, the rules, and the steps
│  ├─ name + descriptionyour AI reads this to decide when to reach for it
│  ├─ What to ask firstasks you for anything missing instead of guessing
│  ├─ Read these firstyour price list, job notes, and voice guide
│  ├─ Hard rulesread before it writes a word
│  ├─ Stepsthe job, in order
│  ├─ What good looks likethe checks before it calls the job done
│  └─ Lessonsa dated line for every mistake, so it isn't repeated
├─ template.mdwhat a finished one looks like
└─ example.mda finished example to copy

Skills fix themselves. It's a standing rule for every one of our skills, and the download writes it into your AI's rulebook too:

The download has a blank skill and three starter skills for a local service business. They're written for this download and modeled on jobs our skills do. Each one drafts and never sends, and hands prices, promises, and safety calls to a person.

Admin

Call notes

Turns a call, a site walkthrough, or a voice memo into decisions, to-dos with owners and dates, and a drafted follow-up. Anything about safety goes to a person.

Customers

Weekly customer update

Drafts a short update for a job that runs longer than a week: what got done, what's next, and what you need from them. Every date and price waits for your OK.

Books

Invoice reader

Reads a vendor invoice or receipt, checks the math, flags possible duplicates, and logs it for your bookkeeper. It never pays anything or changes your books.

Routines

Run it by hand until you trust it. Then schedule it.

A routine is a skill that runs on its own. Every one needs a person who checks, and an alert if it goes quiet.

On your computer

A schedule on your computer

Runs at a set time while your computer is on. Ours: a 5 AM refresh of the community posts we write our content from.

In the cloud

A schedule in the cloud

Runs even when your computer is off. Ours: the morning research brief and the inbox sorter.

On a trigger

When something happens

A form comes in, a customer opens a proposal, or a system goes down. Ours: the alert we get when a client's system goes down.

The six routines from the video, each drawn the same way: when it runs, what it opens, what comes back, and who checks.

The morning research brief

When6 every morning, in the cloud. Our computers can be off.
It opensAI and business news, a podcast, and the chamber newsletter.
It returnsThe top stories and post ideas, in the app we plan content in.
Who checksNick picks the ideas worth posting. If it's late, an alert fires.

The inbox sorter

When5, 8, and 11 AM, then 2 and 5 PM, every day.
It opensThe inbox, plus a rules file of every sorting correction.
It returnsEvery email labeled and filed. Nothing deleted, nothing sent.
Who checksNick skims what it filed. Each correction becomes a rule.

The systems alert

WhenEvery 15 minutes, on our CRM.
It opensEvery system on our map, ours and our clients'.
It returnsAnything down gets a push to our phones and an AI agent on the fix.
Who checksJack and Nick. If the fix needs a person, it names who.

The database watchdog

WhenEvery 2 minutes, around the clock.
It opensEach client database it watches.
It returnsThree misses in a minute means a restart, never twice in 20 minutes.
Who checksUs. If the watchdog goes quiet for 45 minutes, an alert fires.

The payment check, in a tree-care company's app

When7 every morning, inside the app we built them.
It opensEvery unpaid invoice with a card payment in progress.
It returnsAsks the card processor if it went through, and records the answer.
Who checksThe office and their bookkeeper, in the payments report.

The email delivery check, in the same app

WhenRight after each send, plus a daily sweep of the last 14 days.
It opensEvery proposal and invoice email the office sent.
It returnsDelivered, opened, bounced, or marked as spam.
Who checksWhoever pressed Send gets an email if it didn't arrive.

None of the six sends anything to a customer on its own. The download writes all six out, with a blank routine card to plan your own and a checklist to run before you schedule anything.

In the download

Everything from the video, ready for your business.

ai-skills-routines/the folder you download
├─ README.mda one-minute start
├─ START-HERE-FOR-YOUR-AI.mdyour AI reads this and sets you up
├─ four-steps.mdthe four steps, and which one you're on
├─ skills/saved recipes for jobs you repeat
│  ├─ skill-template/a blank skill, with notes on each part
│  ├─ call-notes/notes, to-dos, and a drafted follow-up
│  ├─ weekly-customer-update/a weekly update on longer jobs
│  └─ invoice-reader/reads and logs vendor invoices
├─ routines.mdsix real routines and a blank routine card
└─ workflows-by-area.mdadmin, books, teams, and sales

Workflows by area. Pick the area that eats the most of your week. Each one has a place where a person signs off, and a real example with the step it lives on:

Unzip it, open the folder in Claude Code (the Claude desktop app's Code tab is the easiest way in), and type:

Read START-HERE-FOR-YOUR-AI.md and set me up.

Your AI finds which step you're on, picks one job you repeat every week, does it with you by hand, and saves it as a skill. It only suggests a routine once you trust the skill, and nothing gets sent on your behalf.

Who it's for

Owners who've tried a chat and are ready for step 2.

We're two brothers in Lake Charles who build AI tools for local businesses, and we still climb these same four steps every time we bring in a new system. This is for the owner who opens a chat window now and then, keeps pasting in the same background, and has a job every week that takes longer than it should. The starter skills are written for a local service business, and your AI rewrites them for your trade: tree services, electricians, roofers, cleaners, contractors, and inspectors in Lake Charles, Sulphur, Moss Bluff, and Westlake, or wherever you are.

If your AI doesn't know your business yet, set up its memory first with our AI memory setup. You can climb steps 1 to 3 on your own. When your team needs it all in one place, with its own data, that's step 4, and it's what we build. See our work.

Questions

Common questions.

Is it really free?

Yes. No card and no trial. The files are yours to keep and change.

Do I need to know how to code?

No. A skill is a text file written in plain English. Your AI writes it with you from your answers and one real example of the job, and you correct it in plain words.

What do I need to get started?

A computer and a Claude account. Claude Code comes with the paid Claude plans, and the Claude desktop app's Code tab is the easiest way in. You can also upload the files to a Claude chat. Have one real example of a job you repeat every week, like a call transcript or a vendor invoice.

What's the difference between a skill and a routine?

A skill is a saved recipe for one job: the steps, what good looks like, and the checks. You run it with one line. A routine is that same skill running on its own, on a schedule or when something happens, with a named person who checks the result and an alert if it goes quiet.

Will it send emails or change things on its own?

Not as written. The skills in the download read and draft. Your AI starts every connection read-only, you press send, and it only suggests a routine after you've run the job by hand and trust it. Prices, promises, and safety calls stay with a person.

Which step should I start on?

Most owners are on step 1, a chat window now and then. If you paste the same background into every chat, or ask for the same job every week and it comes out different each time, you're ready for step 2. The download has a short guide to find your step and what to do first.

Can Redwater set this up for my business?

Yes. We're based in Lake Charles and build this kind of thing into local businesses. Book an AI audit and we'll tell you honestly whether it's worth it for you.

Ready for step 4?

You can climb steps 1 to 3 on your own. When your team needs it all in one place, with its own data, start with an AI audit. We'll walk through how your business runs and where software would save the most time.

Book your AI audit →