The New Hire Setup: How to Onboard Claude Like an Actual Employee
A five-step system for turning Claude from a search bar into a documented, skill-running member of the team.
Posted
4 days ago
Duration
Format
Tutorial
educational
Views
3.5K
109 likes
57 · 43
Big Idea
The argument in one line.
Claude only becomes useful for real delegation once it receives the same onboarding a human hire would get: business context, a department-based folder structure, documented workflows, and skills built from those workflows.
Who This Is For
Read if. Skip if.
READ IF YOU ARE…
A solo business owner or small team lead who wants to hand recurring, non-revenue tasks to Claude instead of doing them by hand.
Someone already using Claude casually for chat or search who is frustrated it never seems to know anything about their actual business.
A creator or service provider with clearly definable departments (marketing, sales, ops) willing to spend real time documenting workflows before automating.
SKIP IF…
You want a five-minute plug-and-play automation - this setup requires real documentation work before Claude produces anything useful.
Your business has no repeatable workflows yet, or you're still pre-revenue and finding product-market fit.
TL;DR
The full version, fast.
Most business owners treat Claude like a search bar, so it only ever gives generic answers. This video teaches a five-step onboarding process instead: find the one to three tasks with the best time-to-money ratio, feed Claude a business overview document so every answer is grounded in real context, break the business into department folders, interview Claude to map one workflow in exact step-by-step detail with examples of good and bad output, then connect the tools that workflow needs and package it as a skill file Claude can run on a schedule. Demonstrated live by turning a three-hour competitor-research routine into a slash-command that runs in minutes.
Free for members
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
A student, Brad, describes going from constant guilt about stopping work to being able to go home for dinner, after adopting the five-step 'new hire setup' for onboarding Claude.
00:46 – 01:53
02 · Step 1: Find your revenue-generating activities
Draw a line down a page: revenue-generating activities on the left, non-contributing tasks (email, bookkeeping, proposals, thumbnails) on the right. The right column is what gets handed to Claude.
01:53 – 03:52
03 · Step 2: Context - the Business Overview Generator
A free prompt interviews the owner and produces a business overview document covering company identity, revenue model, offer stack, team, market position, growth profile, and 90-day priorities.
03:52 – 06:39
04 · Creating the Claude workspace
A dedicated project folder becomes Claude's working environment; the business overview is dropped into a context folder and Claude is asked a real question ('who is my ideal customer?') to show grounded, non-generic answers.
06:39 – 08:44
05 · Step 3: Departments as folders
The business is broken into department folders (marketing first) so Claude can pull the right context for a given task instead of guessing.
08:44 – 10:51
06 · Step 4: Mapping workflows - the interview prompt
A second free prompt, 'Map One Workflow', has Claude interview the owner with four questions to fully document a task before automating it.
10:51 – 13:47
07 · Interviewing Claude on competitor research
Live demo: the owner answers which department the task belongs to, what triggers it (8am EST daily), and walks through the exact click-by-click process of researching competitor YouTube channels with vidIQ.
13:47 – 16:03
08 · Showing Claude what good looks like
A real, well-done competitor brief is uploaded as the success example, with explicit failure modes named (fabricated data, off-audience ideas). Claude writes the full documented workflow to the marketing/workflows folder.
16:03 – 18:58
09 · Step 5: Creating skills + connecting tools
Skills are explained as workflows Claude can run on demand or on a schedule. Before building one, the required tools (vidIQ, Gmail, and others) are connected through Claude's Connectors settings.
18:58 – 23:12
10 · Building and running the Coffee Competitor Brief skill
The documented workflow is turned into a skill file structured with the DBS framework (Direction, Blueprints, Solutions), then run live with /coffee-competitor-brief, pulling real vidIQ outlier data and comments in a couple of minutes.
23:12 – 23:47
11 · The structure is the point
Closing note: the specific competitor-research skill matters less than the reusable structure - folder, business overview, connectors, documented workflow - that now underlies everything built afterward.
Atomic Insights
Lines worth screenshotting.
Productivity as a business owner is measured by time in versus money out, so the first step of delegating to Claude is finding the one to three tasks with the best time-to-money ratio.
Without a business overview document, every answer Claude gives comes from generic training data instead of the owner's actual numbers, offers, and customers.
A Business Overview Generator interview extracts seven things: company identity, revenue model, offer stack, team and operations, market position, growth profile, and ninety-day priorities.
Breaking a business into department folders lets Claude pull the right context for a task instead of guessing which part of the business it belongs to.
Mapping a workflow means answering four questions: what task and department, what triggers it, how you do it step by step, and what good versus bad output looks like.
Uploading real examples of good and bad output is what lets Claude imitate an actual standard instead of inventing its own.
A skill file is a workflow packaged into three parts: a direction file for what the skill does, a references folder for blueprints, and a solutions folder for repeatable scripts.
Connecting tools like vidIQ or Gmail before building a skill is what expands what Claude can actually execute versus just discuss.
A skill built this way is portable - the same structured workflow document can be handed to Claude, Codex, Gemini, or Grok, not just one vendor's tool.
Once a workflow is documented and a skill is built, a three-hour research task can run in a couple of minutes on a schedule.
Takeaway
Claude needs onboarding, not just a prompt.
WHAT TO LEARN
Real delegation to an AI assistant depends on the same five things a human hire would need: context, a clear place to work, department scope, a fully mapped workflow, and a packaged skill built from it.
01Cold open + Brad's result
A documented setup, not raw AI capability, is usually the difference between an owner who still does everything themselves and one who can stop working after a normal workday.
Guilt about stopping work often comes from unfinished, undocumented tasks sitting in your head; once a task is fully mapped and handed off, the guilt tends to go with it.
02Step 1: Find your revenue-generating activities
Sort your own task list into two columns before automating anything: what directly drives revenue, and what doesn't - only the second column is a candidate for delegation.
A task belongs on the non-revenue side even if it feels important, as long as it doesn't directly move the time-to-money ratio (bookkeeping, proposals, thumbnails, email).
03Step 2: Context - the Business Overview Generator
An AI model with no context about your business defaults to the same generic answer it gives everyone else; there is no edge in that, only sameness.
A single reusable context document (company identity, revenue model, offer stack, team, market position, growth profile, 90-day priorities) is worth building before any task-specific automation.
04Creating the Claude workspace
A dedicated project folder that Claude can read and write into turns it from a chat window into an actual working environment tied to real files.
Once real business context is loaded, the same question produces a specific, usable answer instead of a generic one; the difference shows up immediately.
05Step 3: Departments as folders
Structuring a workspace by department (marketing, sales, finance, ops) lets an AI assistant find the right context automatically instead of the owner re-explaining it every time.
Folder structure isn't just organization; it's what scopes which files and workflows an assistant is allowed to pull from for a given task.
06Step 4: Mapping workflows - the interview prompt
Before any task can be handed off, the exact trigger, steps, and definition of 'done' have to be written down; most delegation failures trace back to skipping this.
Using an AI interview to extract a workflow surfaces steps the owner would otherwise forget to mention, because it asks the follow-up questions a new hire would ask.
07Interviewing Claude on competitor research
The more specific the walkthrough - exact tools, exact clicks, exact thought process - the more reliably an assistant can reproduce the outcome later.
A schedule and trigger, like every morning at 8am, turns a task from something you remember to do into something that just happens.
08Showing Claude what good looks like
A single well-labeled example of a good outcome, and ideally a bad one, does more to align an assistant's output than any amount of written instruction alone.
Naming what to avoid explicitly, such as no fabricated data or off-audience ideas, prevents the most common failure mode before it happens.
09Step 5: Creating skills + connecting tools
A workflow only becomes a real automation once it's paired with the tools it needs; a documented process with no data source behind it can only describe the work, not do it.
Packaging a workflow as three files - what it does, the detailed playbook, and the repeatable scripts - keeps a skill portable enough to hand to any AI agent, not just one vendor's.
10Building and running the Coffee Competitor Brief skill
A task that used to take three hours of manual research can run unattended in a couple of minutes once the workflow and the tools are both in place.
Turning on auto-approval for a trusted, well-tested workflow is what actually saves time; manually approving every step defeats the purpose of automating it.
11The structure is the point
The specific automation shown matters less than the underlying structure - context, departments, documented workflows, and skills built from them - because that structure transfers to any task in any business.
Glossary
Terms worth knowing.
Business Overview Generator
A free prompt that interviews the owner about company identity, revenue model, offers, team, market position, growth profile, and 90-day priorities, then outputs a single markdown file Claude can use as context in any project.
DBS framework
The three-file structure behind a Claude skill: Direction (what the skill does), Blueprints (the detailed reference playbook), and Solutions (the repeatable scripts that do the actual work).
Connector
An integration such as Gmail, Google Calendar, or vidIQ that gives Claude read or write access to an outside tool, so a skill can execute steps instead of only describing them.
Claude Cowork
An agentic mode inside the Claude desktop app that can read and write files on your computer and run multi-step tasks with tool approvals, distinct from a plain chat conversation.
Skill file
A saved, invocable workflow - triggered by a slash command or a schedule - that Claude runs step by step, built from a workflow the owner documented in detail first.
“Most business owners don't onboard Claude to their business like it is a real employee, and that's the exact reason they are still drowning in work.”
cold-open thesis statement, no setup needed→ TikTok hook↗ Tweet quote
00:35
“This is when you stop treating Claude like an idea slot machine or a fancy Google search and you actually onboard it like a real hire in your business.”
sharp reframe with a memorable metaphor→ IG reel cold open↗ Tweet quote
00:49
“Productivity as a business owner is measured by how much time you put in versus how much money you get out from that time.”
“Without this, Claude will know nothing about you, nothing about your business. Therefore, every task you give it, it's just going to be using the generic model training data that everyone in the world has.”
names the real reason generic AI answers fail→ newsletter pull-quote↗ Tweet quote
06:20
“Context is literally everything. If you don't provide proper context, the AI model is just using the same generic responses and results it gives to everybody else.”
“If you were to hand it to another employee, if you were to actually off board this task from yourself to someone else, what is every line item that you would give them that needs complete, in what order, and what does success look like?”
reframes documentation as offboarding, not just writing instructions→ IG reel cold open↗ Tweet quote
19:36
“Skills are what allowed Brad in the beginning of this video to go home at night and feel not guilty for taking time off to eat dinner.”
ties the whole system back to the emotional payoff→ TikTok hook↗ Tweet quote
23:29
“The point is not to look at this competitor brief skill and run with that. The point is to look at the structure of how I set this up.”
closing thesis, reframes the entire demo as a template→ newsletter pull-quote↗ Tweet quote
The Script
Word for word.
Read-along
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
17px
metaphorstory
Most business owners don't onboard Claude to their business like it is a real employee, and that's the exact reason they are still drowning in work. One of our students, Brad, was in that exact spot, but everything changed.
So I'm almost through Clawdomatic. I'm doing weeks worth of work and hours. The biggest thing I've gained out of it is when I take time off and by time off guys I mean like going home for dinner.
Like when I go home for dinner then I can make the decision to not work the rest of the night and this is the biggest change for me. I don't feel any guilt. I don't feel any pressure.
What changed for him is a Claude setup and it's simple enough that I can build the whole thing with you right now. It's called the new hire setup and it's five steps. This is when you stop treating Claude like an idea slot machine or a fancy Google search and you actually onboard it like a real hire in your business.
Step number one is to discover your revenue generating activities. Productivity as a business owner is measured by how much time you put in versus how much money you get out from that time, which means you need to find the top one to three tasks that you do that have the best time to money ratio and only focus on those things.
You can use a piece of paper to do this or anything for that matter to document this. What I want you to do though is draw a line. And on the left side of that line, write down your revenue generating activities.
For me, that would be filming content, getting on calls with my students, things like that that directly contribute to a healthy time to money ratio. And on the right side of that line, I want you to list every task you are doing right now that isn't contributing to your business in a meaningful way. That might be things like responding to emails, doing your own bookkeeping, creating proposals, graphic design, thumbnails, anything you can think of that doesn't directly contribute to your bottom line, that's what you need to put in the right column.
In the right column is the exact thing that you wanna hand off to Claude in the rest of this setup. Now what I want you to do is save that list for later because we are going to need it. And it's going to be your roadmap for the things you need to focus on and the things that you need to hand off to Claude to automate.
Step number two is we need to set context and get our environment prepared for Claude to be able to handle the tasks that are taking up our days. Context and environment is the most important part of the setup because without this, Claude will know nothing about you, nothing about your business.
Therefore, every task you give it, it's not going to be direct towards helping you. It's just going to be using the generic model training data that everyone in the world has. Beneath this video, I've left a free resource and it is called the business overview generator.
What this does is it interviews you with Claude and Claude extracts seven things, your company identity, your revenue model, your offer stack, your team and operations, market position growth profile, and your ninety day priorities.
Without this, anything you set up after this won't matter. This gives Claude context into who you are and what you do. And then it outputs at the end of this a file that you can bring into any project, any Claude folder, and it is a single source of truth for your company and everything that you do and who you serve.
And so in this free resource, which again I left in the description of this video, what you can do is you can copy this prompt down here. There's a little copy button in the upper right hand corner and once you copy this, you can go to any AI model, I recommend Claude. You can paste it in and then have it interview you.
And it's going to be asking you questions right here. And I like doing this part with an AI model because it covers your blind spots.
So if you miss something or it has a follow-up question, it can really make this document very good. And what it's going to output for you that you need to download is a business overview document. This business overview document is super important.
It gives company identity, your revenue model, and everything else that Claude would need to know in order to help you achieve your goals. That's part one of step two. You need to create context for Claude so that every decision it makes for you in the future is directly tied to your real business stats, your data, and your ninety day goals.
Now before we move on to step three, what we need to do is set up our environment. And so in order to set up a proper environment, you must have Claude desktop installed. If you do not have the Claude app installed on your computer, you must go and do that right now because it allows you to work off the folders in your computer when you choose something like Claude Cowork or you choose Claude Code.
So what I can do is I can create a folder on my computer and that becomes Claude's project. It's workspace that every context, every job position, everything is stored.
And so that's what I'm going to do. I'm going to select new folder and then I'm going to just call this folder my business name. I'm going to call it AI foundations.
And then I can even put test right here so I remember to delete this. And I can click into this and now this is Claude's working environment.
So in order to set up your environment properly, select a new folder once again and add context. And this is where you wanna upload your business overview document. You wanna put your business overview in the context folder.
So I'm going to do that now. As you can see, have my business overview, a copy of it. I'm going to throw that in my context.
And the way you get that is by using the free resource I have in the description, filling it out and Claude will give you a file that you can download to your computer which is a markdown file and you wanna put that in your context folder. So now, if I'm using something like Claude Cowork or Claude Code, what I can do is I can select a project or a folder and I can add a folder here.
And that allows you to select a folder from your desktop which becomes your working environment where Claude can complete work for you. And I can hit open and I will hit always allow.
And now you can ask it questions about your business. I could ask it a question like, who is my ideal customer which that interview prompt is going to help you find out.
I can hit allow. And as you can see it's now reading files on my computer which is super powerful. We don't have any file limits or anything weird like that.
And it read the business overview copy. Now it's responding. It says based on your business overview, you have two ideal customers because AI foundations is really two businesses stapled together with almost zero crossover.
Here's how I define each. Community side, your ideal member. The non technical solo entrepreneur or small business owner who generally wants to build AI themselves.
Beautiful. The done for you side and then it gets into my ideal clients. So now Claude is not just using generic training data that everyone else is using.
That's where most people stop. It's now using my actual data that I've set up for context for every future conversation I have. And so what you're going to learn and understand as you use Claude Moore is that context is literally everything.
If you don't provide proper context, the AI model is just using the same generic responses and results it gives to everybody else. So there's really no unfair advantage or competitive edge in that. And so what you wanna do now is move on to step number three.
After you have your general context, you wanna get a little bit more specific about the right side of that list that you filled out in the beginning of this video. Now the third step of this five step process is to break your business down into departments.
Departments are things like your marketing department, your sales department, communication department. Whatever departments you have in your business that you want Claude to assist you in or enhance, that's what you need to create.
Each department becomes a folder. And so here I am back in our Claude workspace that we created and the beautiful thing about these Claude workspaces on your desktop is that you can create items on your computer. And so if I wanted to I could say something like, hey there Claude.
What I want you to do is I want you to create department folders in this folder. So I want you to create a marketing department to start. So create that folder for me.
And of course, you can do this as well but I do wanna show you that Claude is really good at creating things for you. And this is going to be a new folder on my desktop within that folder that we already have the AI Foundations test folder.
And it says done. The marketing folder is created inside your AI Foundations test folder. Want me to add any other departments?
And so you can go on and you can set up folders for each department of your business. And so once you break your business up into departments, Claude can now go into those folders specifically to complete tasks for you.
If I go and take a look in the actual folder, as you can see now, we have our context with our business overview and our marketing folder. And so now anything marketing related that we have, we can put in here.
Similarly, if we wanted a financial folder, if we wanted a sales folder, communication, scheduling, whatever departments in your business that are taking up your time and making you drown in work, you wanna create a folder for it so you can start chipping away and automating a lot of the process.
Any output files you have can go here. Any skill files you have, any job files, anything marketing related can be organized in the marketing folder now in subdirectories as well which is very nice and it helps you organize your own business. Now this is where things start to pick up.
Step number four is mapping your workflows. I've worked with hundreds of businesses and the ones who have failed have failed because they didn't complete this step. And that is simply mapping out what a completed job looks like from start to finish.
So that list you filled out in the beginning of this video with your revenue generating activities and the things that you were doing that don't generate any revenue, you wanna take all of those things that need to be completed but aren't necessarily revenue generating, and you want to map out what the workflows look like from start to finish.
If you were to hand it to another employee, if you were to actually off board this task from yourself to someone else, what is every line item that you would give them that needs complete, in what order, and what does success look like?
And so beneath this video, in that free resource that you used earlier, I also have another prompt for step four and it's map one workflow. The goal of this is to have Claude interview you once again. And this time, it's going to help you map out a work flow in your business and that asks you four questions in order to extract everything that is involved in completing the task that's draining your time.
So what you need to do is you need to copy this prompt, the map one workflow prompt. And you need to paste this into your Claude CoWork or ClaudeCode workspace, the same one that we've been building throughout this video. And you should do this in a new chat.
So I'm going to select new and now I'm going to make sure I'm in my folder and paste in this prompt. What this prompt is going to do is it's not only going to read the business overview folder first, but it's going to ask you four questions one at a time and it's going to interview you until it can map out the workflow that you want automated.
So just literally a step by step process, an SOP if you would, that you would hand to actual people in order to complete this task. Everything is becoming a workflow in business. And if you do not have your workflow properly mapped out, Claude is not going to be able to help you each step of the way.
And so I'm going to send this off. You can use pretty much any model for this. It's not too heavy of a task.
It's just going to follow this prompt. It's going to read your business overview document, and then it's going to start interviewing you on the task that you want automated. And question by question, what it's going to do is ask you about the one task that's causing you the most pain.
And you just need to answer every question. Which department does it belong to? Let's say I wanna automate my competitor research eventually.
I spend too much time researching competitors, understanding what's actually relevant in the space, and it doesn't contribute to any meaningful revenue. So let's say I want that automated.
First, we need to get it documented and we need to tell Claude which department it lives under. Then we will automate it in the next step. But first, we need to document this entire workflow.
And so I could even use this voice tool over here and press and hold to record to answer all of these questions. And you can just talk to it like it's a human. You can say, the one task I want automated is competitor research, uh, or at least the one task I want documented rather is competitor research and that's going to live under my marketing department.
And then I can send it off. And the reason that you wanna break your business into departments and the way that I've done it in this video is so that Claude can enter a specific folder and grab context in outputs and anything it needs from these workflows that you're creating. It says competitor research under marketing, got it.
What starts it? And then it asks you some more follow-up questions. I could say, right now the only thing that starts it is when I physically go in and do it but I would prefer if it started on a schedule every day.
And then instead of just every day, you wanna be specific. So maybe every morning at 8AM Eastern Standard Time.
And then I can send that off. Then it says, walk me through how you do it now start to finish. Pretend I'm on my first day and I've never done this.
Don't skip the obvious stuff. And so this is really going to make you think about each individual step. And you wanna be as specific as possible because Claude can do most things if you are specific about it.
I'm talking what tools do you use? What tabs do you open up in those tools? What is the exact thought process that goes behind doing the job that you want documented and automated.
And so I can tell Claude. Right now, the way that I get it done is I open up YouTube and I open up my competitor list, which I will give you. Uh, I will upload the document of all of my competitors.
And then I go look at their recent videos and I see if they're performing greater than three x their channel average by using the vidIQ tool. And that's an extension on my YouTube that I use.
And I'm mainly seeing if there's any breakout content that relates to the topics that I make videos about so I can tackle that. And then I go into the comment sections of their videos and I see what questions are people asking so I can make better content around the same topic mixed with my format and my style. So as you can see, I'm being very specific about the exact way that I get things done right now.
I can send that off. And you should probably be even more specific than I just was. I'm talking every click, every decision, every thought.
Anything that this agent would need to understand in order to complete the job in the exact way that you would do it. And it says, that's clear. And I did forget to upload those competitors which I can do that whenever.
And then it says, what does it look like when it's done Describe a good one and a bad one and an actual example if you can. And so most business owners leave out examples because they're too lazy to go and actually find out what are good examples of what success looks like and what are bad examples of what failure looks like.
So you wanna go find successful examples of how this has worked well in the past, and you might have to go through and do it yourself. If you're already doing it yourself, that's okay. If you're trying to automate your emails, you might wanna go capture what good email responses look like and what bad ones look like.
If you're trying to automate your lead follow-up, then you might wanna look at what a good lead follow-up response looks like, ones that have converted well in the past. If you wanna automate your scripting or your LinkedIn posts, you wanna find examples of success and examples of failure. And you wanna upload documents.
You wanna give context. And here you really wanna map out the workflow and tell Claude what does it look like when it's done right so it can model its automation after success. And so what I've done is I've uploaded a competitor brief that has actually been done very well.
And I can tell Claude, the uploaded brief is an example of what it looks like when it's done correctly. The main things that I want to avoid are fabricated data and suggested content ideas that do not fit my audience or my videos at all. And then what I can do is I can send this off.
And so you wanna be more specific than this. For the sake of this video and brevity, I want to be efficient but you wanna get very specific in mapping out your work flow because this makes the back half of the automating part super easy. And after it has all four answers, it's going to write out the entire workflow and it will save it to your folder.
That's done. Saved it to marketing workflows competitor research on your machine. And so you can open it over here in the right hand sidebar and you can read the entire workflow that it created and what a good competitor brief looks like based on things that have actually worked well in the past.
And the more specific you get, the better this workflow actually is. You can go to your folder as well and see where it saved this.
So if I open up AI Foundations test and I go to marketing, it created a workflows folder and saved my competitor research workflow in here. This can be used now to create an automation that handles the entire thing for me. And that's step number five of this five step setup is to create skills around your workflows.
Skills are files that Claude can use to run on a schedule or whenever you invoke them. So if I wanna say invoke the competitor research skill and generate me a report, it can go through all of those steps that we just listed.
And there are some things, of course, that can't really be automated right now. Filming videos, I can't really give Claude the task to film videos. Getting on Zoom calls for me, can't really do that.
Those are revenue generating activities you need to complete yourself. But things like creating video thumbnails, creating scripts, answering emails, health checking the code base, anything that is like knowledge work, you can turn into a skill file and a step by step workflow that Claude can run.
Any tool that has an API that you use that you wanna automate processes in it, you can add those tools, run the workflow, and have it automated on a schedule.
Let me show you how. So step number one before you tell Claude to turn that workflow into an automation is you need to connect the proper tools that you need. So you can go to the customize tab in the left hand sidebar.
And once you're there, you're going to be able to see all of your skills but you also want to look at your connectors. So go down to your connectors tab and then this is where you connect all of the tools that you need in order to complete that job.
You can connect Drive, Microsoft, Google Calendar, Gmail, Higgs Field, Notion, Slack. If you hit add and browse connectors, you can see the thousands of tools that you have access to when it comes to connecting.
Pretty much anything you can think of can be connected to Claude and you can perform actions in those applications. And so you wanna connect to any tool that you possibly can. And so for my case, what I wanna do is I wanna connect to something like vidIQ because vidIQ has all of the YouTube data that I need.
It has my YouTube data. It has my competitor data, keyword research data. Anything I need for YouTube is on vidIQ.
So this one tool is expanding Claude's capabilities. If I click in here, as you can see, this has 17 interactive tools, 30 read tools, and five write tools.
It can generate video scripts for me, titles, and this is just a tool on the Internet that I have an account for. Also, can look at channels videos, find a b roll, generate videos, do keyword research. It can do so many things when it comes to YouTube.
So for my competitor research tool that's going to be based around YouTube, this would be a good tool that I need to add. If I wanted to get the report emailed to me, then I could connect something like Gmail and Claude could send a Gmail for me on a schedule after the brief gets done using vidIQ's capabilities.
So connectors are what allow you to turn Claude into a workaholic because you connect all the tools you currently work out of and you offload those capabilities that you would usually be doing manually to the machine and it's documented in the workflow.
And so I've got all my tools connected that I need and I wanna tell Claude, hey there Claude, what I want you to do now is take that workflow that we just uploaded and I want you to create a skill file out of that. I want you to call it coffee competitor brief.
That way while I'm getting my coffee, I can run this skill file and it can complete that competitor research brief for me. And eventually, I wanna set it up on a schedule.
So look at that workflow for how I get things done. I've connected vidIQ which is the only tool I need for this and let's create a skill around it. And so skills are what allowed Brad in the beginning of this video to go home at night and feel not guilty for taking time off to eat dinner.
Okay? That's what stuck with me most from that is he was able to go home. He was able to not feel guilty about stopping work.
And so many others who have implemented this skill framework have felt the exact same way. And so the keyword here that I want you to read and understand is create a skill file.
A skill file is an actual setting in Claude right here in the customize tab. Skills are things that you can hand to any agent for that matter. You can hand it to Codex.
You can hand it to Gemini, Grok. Anything that you want to run your workflow, you can give it a tool and then you can give it a skill file and it will run that workflow for you.
And a skill file is essentially the workflow except Claude will format it in a way that it understands how to run it. So if I click into my emoji sparkle skill, there's three files in here.
We have the skill dot m d which is the workflow as you can see here. This is the direction.
We have references. So any file that this skill or workflow references or needs a blueprint for, that goes in the references folder. As you can see in my emoji sparkle skill, uh, it takes any sentence and adds a fitting emoji to it.
We have three things, direction, what the skill does, blueprints, the detailed playbook and then solutions which are scripts that can do repeatable work.
And so this skill is packaged up nicely with three files that Claude can use in order to get the job done every time and that's what we're going to turn all of our workflows into is skill files. It says where should the finished brief land each morning?
I can do folder plus chat. How should the brief handle day over day continuity? I can just say clean daily snapshot and then we can get moving.
And so that's what I also like about building in Claude. It asks you those follow-up questions. I will select always allow and always allow on that.
And for now, I'm going to say automatically approve so that I don't have to do that anymore. And after doing the workflow, it makes everything that follows with skill creation super easy.
So now we just told it to create a skill and take that workflow that we created. And what it did was it created the skill in one shot. And so now we have a skill file called coffee competitor brief.
I can even hit save skill, and now that skill has saved to my Claude account. So whenever I type in slash coffee, as you can see, we have coffee competitor brief, I can run that and it completes all of the work in my workflow for me.
Now of course, some tasks will be harder than others to automate. Some will have a bigger review process and you need to actually manage the skill and to go in and review the result and make changes and review the result again and make more changes and handle edge cases. But this is the general structure that you want.
And so now I can just type in this slash coffee, like I said, and hit enter. And now that entire workflow is running for me.
Something that used to take me three hours. If I actually wanted to sit down, research all the channels, go through, analyze what their old views were versus what their new views were, the topics and everything in between, that was a lot of time saved in a couple of minutes of just thinking about how I want that workflow done.
And take a look at everything it's using here. It's using everything from every step. It's using our folder, our business overview, our connectors, which was the tool that we added, vidIQ that has my competitor data and all the YouTube search traffic.
And what it's doing is it's pointing videos from people in my same industry. And so I can make this any way I want. Right now it's going through the filtering and mining comments step where it's actually going in the comment section of all of these videos of the breakthrough videos on these people's channel and pulling in comments so I can figure out the best content to make that answers everyone's questions.
But the point is not to look at this competitor brief skill and run with that. The point is to look at the structure of how I set this up. And now everything I create runs out of this folder that we created.
And if I have marketing context that I wanna throw in and I have certain analytics, I have certain files, certain posts that I want Claw to replicate, then I can just put it in here.
So step by step, systematically, you wanna go through and begin automating all of these tasks and putting them in your folder hierarchy. Now, you wanna go deeper on this, watch this video right here because it's going to explain this setup even deeper.
The Hook
The bait, then the rug-pull.
A student named Brad went from feeling guilty every time he stopped working to going home for dinner without a second thought, and the entire change was one Claude setup, walked through here in five steps: discover, set context, break into departments, map workflows, and turn those workflows into skills.
Frameworks
Named ideas worth stealing.
00:00list
The New Hire Setup
Discover
Set Context
Breakdown (Departments)
Map Workflows
Create Skills
A five-step sequence for onboarding Claude into a business the way you'd onboard a human hire, rather than using it as an ad hoc search bar.
Steal forany owner-operator business trying to actually delegate recurring work to an AI assistant
20:24acronym
The DBS Framework
Direction
Blueprints
Solutions
How a Claude skill file is structured internally: a direction file stating what the skill does, a references folder with the detailed playbook, and a solutions folder with the repeatable scripts.
Steal fordesigning any reusable AI skill or agent tooling, regardless of platform
CTA Breakdown
How they asked for the click.
VERBAL ASK
23:41next-video
“Now, you wanna go deeper on this, watch this video right here because it's going to explain this setup even deeper.”
Soft outro pointing to a follow-up video rather than a hard product pitch on camera; the actual monetization (aifoundations.io/join, the free New Hire Setup Kit) lives only in the description, not spoken.
A Turkish AI educator demos Claude Cowork's new Save Skill feature live: one recorded pass of a real content-research task becomes a reusable, natural-language-triggered workflow.
A coach who replaced most of his team with AI reduces every online coaching business down to three roles: the leader who sells, the scientist who builds systems, and the artist who builds the brand.
An unscripted screen recording of a real operator's Claude Code sessions — three isolated terminal setups, a tiered planner/executor model stack, and a text-approved autonomous agent — running an eight-figure marketing business in real time.
A 15-minute breakdown of eight productized AI-consulting offers built on Anthropic's new Record-a-Skill feature — and the one habit that decides whether you make $300 or $5,000 a month from the same skill.
A full walkthrough of turning one raw talking-head clip into a fully animated, brand-matched short — with a single Claude Code prompt instead of a video editor.
A YouTube creator argues the real AI job threat isn't robots — it's coworkers who learned to direct agentic AI — then live-demos three tasks it can already do and a three-step plan for learning to manage it yourself.
00:10
00:17
00:31
00:40
00:54
01:11
01:44
01:57
02:05
02:13
02:27
02:46
03:05
03:41
04:33
05:01
05:29
06:26
06:46
07:10
07:31
08:12
08:43
08:46
09:11
09:47
10:05
10:23
11:03
11:28
11:53
12:19
12:44
13:34
13:56
14:16
14:35
14:54
15:14
16:02
16:10
16:34
16:54
17:10
17:26
17:43
18:16
18:33
18:49
19:03
19:14
19:24
19:39
19:57
20:15
20:32
20:49
21:06
21:23
21:40
21:57
22:30
22:47
23:03
23:17
23:29
10:15
13:26
37:20
15:24
12:23
14:03