Modern Creator
Eliot Prince · YouTube

Claude Skills Full Course: Beginner to Expert

A two-and-a-half-hour build-along that turns one SEO prompt into a five-skill department with a manager on top, a plugin wrapper, a brand voice layer, and a stack of marketing skills.

Posted
1 months ago
Duration
Format
Tutorial
educational
Views
83.5K
1.3K likes
Big Idea

The argument in one line.

The best Claude skills are captured from work you have already done well, then climbed one level at a time, from a wrapped prompt to connected tools, chains, and a manager skill, only as far as the pain actually requires.

Who This Is For

Read if. Skip if.

READ IF YOU ARE…
  • You use Claude Chat or Cowork daily and keep pasting the same long prompts back in by hand.
  • You run a service business (SEO, marketing, consulting) and want repeatable deliverables like audits, reports and invoices produced on command.
  • You have built a few skills already but they misfire, drift, or trigger on the wrong requests and you want rules for fixing them.
  • You want to see how skills hand off to each other and how an orchestrator skill routes a vague goal to the right specialist.
  • You manage a team or ghostwriters and want one brand voice applied to every document that leaves the company.
SKIP IF…
  • You only work in Claude Code and want CLI or repo-level skill authoring; this is taught almost entirely in the Claude desktop app with Chat and Cowork.
  • You want a short overview; the material is a long live build with real waiting time on each run.
  • You expect hand-written SKILL.md files; nearly everything is generated through the built-in skill-creator from prompts and conversation.
TL;DR

The full version, fast.

A Claude skill is a saved, step-by-step procedure that Claude runs on command or fires on its own when your phrasing matches its description. Each skill has three parts: a description with trigger phrases, a SKILL.md holding the decisions and order of work, and reference files holding templates, checklists, examples and scripts. Skills come in two types (deterministic templated outputs and non-deterministic judgment work) and five levels: run, ask, connect, chain and manage. Build them by wrapping a proven prompt, by running a task with Claude until the output is right and then capturing it, or by recording your screen. Keep one job per skill, keep the main file short, push maths into code, add three to five examples of great output, and only climb a level when the business pain justifies it.

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.

Create a free account →
Chapters

Where the time goes.

00:00 – 03:37

01 · Intro and the build plan

Credentials, the course map, and the end goal: a full SEO department of skills built live, plus 101 skill ideas.

03:37 – 06:01

02 · What a Claude skill is

A set of instructions Claude keeps and runs on command, like a checklist that runs itself, firing either by slash command or automatically from context.

06:01 – 13:59

03 · Anatomy: description, SKILL.md, reference files

Walks through a real SEO blog writer skill: the description and triggers, the five-stage SKILL.md, and templates and checklists kept as references. Decisions go in the main file, detail goes in references.

13:59 – 17:58

04 · Running, uploading and editing skills

Slash command versus natural trigger phrases, plus uploading, toggling, downloading and editing skills in the Customize panel.

17:58 – 26:57

05 · Two types and five levels

Deterministic versus non-deterministic skills, then the five levels: run, ask, connect, chain, manage. Levels are not a scoreboard.

26:57 – 35:57

06 · Way 1: wrap a proven prompt

Turns on skill-creator and wraps a tested SEO audit prompt into a level-one search visibility audit skill, then runs it on a live site.

35:57 – 55:38

07 · Way 2: build from expertise in Cowork

Researches best practice, feeds in past transcripts, writes an SOP, tests it on a real transcript, corrects the output, and only then captures it as the SEO blog writer skill. Adds missing trigger phrases by editing conversationally.

55:38 – 1:06:48

08 · Way 3: record a skill

Narrates a Search Console to Google Doc to Gmail reporting routine on screen; Claude turns 199 recorded steps into an SEO client report skill that uses Claude in Chrome and connectors.

1:06:48 – 1:13:58

09 · Six rules for great skills

One skill one job, keep the main file tight, write code for mechanical bits, build from work done well, give three to five examples, stop skills fighting. Plus character limits and naming gotchas.

1:13:58 – 1:21:38

10 · Level 3: connectors and the strategy skill

Sets up Apify and Semrush connectors and turns a strategy prompt into a six-month SEO strategy skill with forecasting scripts; fixes the 1,024-character description error live.

1:21:38 – 1:32:42

11 · Level 4: chaining skills into a loop

Links audit, strategy, blog writer and report so each knows its handoff. Chooses offer-then-wait over auto-run and stores outputs in a Cowork folder so the chain has history.

1:32:42 – 1:40:49

12 · Level 5: the orchestrator

Builds an SEO department manager skill that takes a plain-language goal, reads project memory, and picks which skills to run. Tested on a seasonal ski site.

1:40:49 – 1:48:50

13 · Plugins as a filing system

Packages the five skills, references and declared connectors into one shareable SEO department plugin, genericized for other users.

1:48:50 – 2:06:52

14 · Building a brand voice skill

Analyzes human-written articles into a voice profile, adds anti-AI-slop and banned-word references, runs with-and-without evals, removes a bad trait, and rewrites a real article in editorial mode.

2:06:52 – 2:09:30

15 · What to build next

Start from the tasks you hate. An interview prompt to find worthwhile skills and a list of 101 ideas sourced from real business pain.

2:09:30 – 2:18:11

16 · Bonus: the brand print skill

Audits a folder of logos, fonts and guidelines into a brand spec, then builds a skill that applies the brand to invoices, documents and pages. Contrasted with Claude Design for deliberate design work.

2:18:11 – 2:31:58

17 · Bonus: five marketing skills

Director of psychology teardown, trend jack, clipper army, lead magnet and email sequences, each run live on real content.

Atomic Insights

Lines worth screenshotting.

  • A skill is a standard operating procedure Claude keeps on file, so the same process produces the same shape of output every time.
  • The description is the only part Claude reads when deciding whether to fire a skill, so vague trigger phrases cause accidental runs.
  • Write trigger phrases in the words you naturally use at work, not in phrasing you have to remember.
  • Put decisions and order of work in SKILL.md; put long examples, style guides, templates and schemas in reference files that load only when needed.
  • Deterministic skills fail loudly, like a missing invoice column, so they are the easiest first builds.
  • Non-deterministic skills such as brand voice fail quietly; they look fine on day one and drift without an obvious error.
  • Skill levels are not a scoreboard: a level-one skill that saves two hours a week beats an over-engineered level-five system that needs babysitting.
  • Never lock a process into a skill until you have run it end to end and corrected the output at least once.
  • Running the task first surfaces house rules, like banning em dashes or forcing FAQ sections, that nobody would have written into the skill up front.
  • Skills built in Claude Chat or Cowork are available in Claude Code, but skills built in Claude Code do not flow back to Chat and Cowork.
  • Never ask a language model to do maths; have it build the spreadsheet or script that does the maths.
  • A good test of any skill is to run the same job with and without it and compare the two outputs.
  • Skill descriptions must stay under 1,024 characters, the word Claude is reserved in skill names, and stray colons or quotes can break the file.
  • In one eval, a brand voice skill passed 97% of its rule checks versus 50% without it, at roughly four times the runtime.
  • If an orchestrator runs the same skills in the same order every time, it is just a chain with extra steps and does not need to exist.
  • Chained skills need shared memory, either a Claude project or a Cowork folder that holds every audit, strategy and report.
  • A plugin bundles skills, connectors and a readme so a whole workflow can be shared and installed without missing pieces.
  • Voice analysis only works on human-written source material; feeding it AI-assisted text teaches it nothing new.
Takeaway

Prove one skill before you stack them

WHAT TO LEARN

Skills work when they capture a process you have already run and corrected, kept to one job, then linked and managed only after each piece holds up alone.

02What a Claude skill is
  • A skill is a saved procedure Claude can run on command or fire automatically when your request matches its description.
  • Prompts you paste by hand are the obvious first candidates, because the process is already proven and only needs a wrapper.
03Anatomy: description, SKILL.md, reference files
  • Keep decisions, order of work and hard rules in SKILL.md, and move long templates, style guides and examples into reference files.
  • Audit trigger phrases often; a vague phrase like write up this transcript will fire the skill on unrelated work.
04Running, uploading and editing skills
  • Use the slash command when you need a guaranteed run and trigger phrases when you want the skill to slot into normal conversation.
  • Skills can be uploaded, toggled off, downloaded and edited in plain language, so fixing a missed detail takes one message.
05Two types and five levels
  • Decide whether the output has a fixed shape or requires judgment, because judgment skills fail quietly and need ongoing review.
  • Pick the lowest level that solves the pain; a simple daily skill often beats a complex orchestrated system.
06Way 1: wrap a proven prompt
  • Turn on the built-in skill-creator and let it build the skill from your prompt instead of hand-writing the file.
  • Run the new skill on a real input yourself rather than trusting a self-test, so you see the actual output.
07Way 2: build from expertise in Cowork
  • Ground the process in your own past material and current research, not in whatever the model invents from scratch.
  • Run the full task, correct the output in plain language, and capture the skill only when the result is one you would ship.
08Way 3: record a skill
  • Screen recording works for processes that span several web tools and are easier to show than describe.
  • The recorded skill may swap your manual clicks for connectors or browser control, picking the most efficient route to the same result.
09Six rules for great skills
  • When output quality slips, split the skill into smaller jobs before adding more instructions.
  • Have the model write scripts or spreadsheets for arithmetic, file conversion and bulk renaming instead of doing them itself.
  • Store three to five examples of excellent output so the skill can grade its work against a real standard.
  • Respect the 1,024-character description limit, avoid the word Claude in skill names, and watch for colons or quotes that break the file.
10Level 3: connectors and the strategy skill
  • Connectors let a skill pull live data and push finished work into tools like Google Drive, Notion or Gmail, removing copy and paste.
  • Feed a skill's error message straight back to Claude; it fixes over-long descriptions and missing reference files quickly.
11Level 4: chaining skills into a loop
  • Chain skills by defining what each one hands off and what the next one expects to receive.
  • Default to offering the next step rather than auto-running it, so you keep control over when expensive work happens.
  • Give chained skills a shared folder or project so later runs can read earlier audits, strategies and reports.
12Level 5: the orchestrator
  • An orchestrator earns its place only when the right next skill depends on the situation; a fixed sequence is just a chain.
  • A manager skill that reads project history can spot timing issues, like a seasonal deadline, that individual skills miss.
13Plugins as a filing system
  • Package related skills and their connectors as a plugin so they install together and nothing goes missing when shared.
  • Remove the standalone copies after installing a plugin, otherwise every skill exists twice and triggers become ambiguous.
14Building a brand voice skill
  • Build voice profiles from human-written work only, and correct the profile before turning it into a skill.
  • Use with-and-without evals to see which rules a voice skill actually enforces and what it costs in time and tokens.
  • Treat a voice skill as never finished; collect ten to twenty annoyances from real use and feed them back in batches.
15What to build next
  • Start from tasks you hate or that drain you, not from impressive-sounding skills.
  • A dull deterministic skill like a branded invoice generator can save more time than a clever one.
16Bonus: the brand print skill
  • Audit brand assets into a written spec first, then build a skill that applies logos, colors and fonts to every output.
  • Keep dedicated design tools for deliberate projects and let a brand skill cover everyday documents.
17Bonus: five marketing skills
  • Marketing skills work best layered on existing drafts, critiquing hooks and structure rather than writing from nothing.
  • Skills that need business context, like lead magnets or email sequences, should run on top of a folder or connector that holds it.
Glossary

Terms worth knowing.

SKILL.md
The main markdown file inside a Claude skill. It holds the step-by-step instructions, the order of work, and the rules for what good output looks like.
Reference files
Supporting files bundled with a skill, such as templates, checklists, worked examples, style guides or scripts. Claude loads them only at the step that needs them.
Trigger phrases
Example wording in a skill's description that tells Claude when to run it automatically, without the user typing a slash command.
skill-creator
A built-in Anthropic skill that knows the required structure of skills and builds, packages and can test new skills from a prompt or conversation.
Claude Cowork
A mode in the Claude desktop app built for longer multi-step tasks, with a visible task list and access to a chosen local folder.
Connector
An integration that lets Claude read from or write to an outside tool such as Gmail, Google Drive, Notion, Semrush or Apify.
Deterministic skill
A skill whose output always follows a fixed shape, like an invoice or audit template, so errors are easy to spot.
Non-deterministic skill
A skill that applies judgment, taste or voice, with no single correct output, so it needs ongoing review and tuning.
Orchestrator skill
A manager skill that knows what a set of other skills do, takes a plain-language goal, and decides which skills to run and in what order.
Plugin
A package that groups related skills, their reference files, required connectors and a readme so the whole set can be installed or shared at once.
GEO
Generative engine optimization: shaping content so AI search tools and answer engines cite it, alongside traditional search ranking.
Evals
Automated test runs that compare outputs with and without a skill against its rules and report pass rates, time and token cost.
Resources

Things they pointed at.

27:23toolskill-creator (Anthropic built-in skill)
39:12toolClaude Cowork
28:28toolWispr Flow (dictation)
45:19toolyoutube-transcript.io
56:04toolClaude in Chrome extension
58:07toolGoogle Search Console
1:15:34toolApify
1:16:27toolSemrush
1:17:28toolDataForSEO
1:17:28toolFirecrawl
1:17:28toolNotion
43:29bookStart With Why (Simon Sinek)
2:17:29toolClaude Design
2:30:53toolKit (formerly ConvertKit)
Quotables

Lines you could clip.

03:37
“A skill is simply a set of instruction Claude keeps to run on command.”
Clean one-line definition with no setup→ TikTok hook↗ Tweet quote
25:56
“A level one skill that frees up two hours a week of work for me is a massive, massive win versus a level five skill that kind of needs a lot of troubleshooting and managing just to get it working.”
Contrarian take against over-engineering→ IG reel cold open↗ Tweet quote
52:24
“A lot of people will just bake the Claude skill and then it will fall down because they haven't tested and refined the process of doing it before actually creating the skill.”
Names the most common mistake→ newsletter pull-quote↗ Tweet quote
1:09:40
“I will never get Claude to do maths directly. What I'll do is I'll get it to build the spreadsheet that does the maths.”
Memorable, practical rule→ TikTok hook↗ Tweet quote
1:37:33
“If you run the same skills in the same order every time you failed, you are then a chain with extra steps. A chain does not need a manager.”
Sharp line read from the generated orchestrator→ newsletter pull-quote↗ Tweet quote
1:41:17
“Plugins, which in my mind, the easiest way to describe it is a filing system.”
Demystifies a confusing feature in one line→ IG reel cold open↗ 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.

metaphoranalogystory
Welcome to the definitive course on Claude's skills. I built over 450 skills over the last year or so for my own business, for the 3 ,000 plus students I've taught to use AI Live, and for businesses I've consulted with. I'm pretty much doing this stuff all day, every day, and essentially what I'm gonna do is I'm gonna transfer everything that I've learned.
and known through practice, research and iteration and actually building these things. I'm going to transfer all of that knowledge to you today. So even if you've never touched a Claude skill in your life and you're just starting to use this stuff, we're going to go from these beginner routes all the way up to advanced level.
So I'm going to walk you through the route to get there so you can build full teams of AI skills running in your business to act like little employees working together. No fluff, here's exactly what we're going to learn today. I'm going to take you through the plan of what we're actually building so you can build along with me knowing the end result and the order we're going in.
We're going to talk about what a clawed skill actually is. Even if you sort of know what they are, I'm going to help you conceptually explain them to other people or if you have no idea what they are, we're going to go through the basic definition and how it differs from what you already use with AI. We're going to talk about the anatomy of a skill and the different parts, how they all stack together to create a high performing file that runs inside Claude.
We're going to talk about the map, the two types of skills and the five different levels. But again, you can mix and match and pair these together and understand where you are in the build process and how you're constructing your skills. Once we've done that, we're going to actually start building and you can build along with me.
We're going to talk about the three key ways to build a cloud skill and we're going to build together step by step. One, two, three. Then we're going to talk about what separates a good skill or an average skill from a really great one that is high performing in your business.
We're going to talk then about managing. The skills, keeping them up to date, sharing them, using them maybe across multiple people. Then we're going to start to actually build into the levels.
So we're going to start to connect skills to the outside world and outside tools so they can execute more work for you. We're going to learn how to link them together to create chains of them that run in teams. And we're even going to stitch them all together with an orchestrator, a manager that can manage these like a line manager for you that checks in and out of your team of skills before showing you.
you how to package these all up in a neat plugin, talk about what those are and then finish off with some other ideas about what you should be building, finding pain points in your business and I'm even going to give you 101 of my best skill ideas for you to walk away with and build for yourself. So in this course we're actually going to be building a full team of SEO clawed skills these are going to act as a whole seo department for your work and we're going to build everything live step by step you can build along with me as well if you don't want to do seo or you think this might not be that useful for you i still recommend watching and building along with me because this is really about building the skills and the knowledge for you to go and implement on your own things so there's two ways you could really watch this you could actually build along with me or you could just watch and learn along the way take notes for you to then impart on your own ideas of what you want to build for your business work life whatever it is and while we go along as well this guide has all the prompts and steps that i'm using in this video you can grab it below there's a link in the description where you can get it for free it's inside something called my ai recipe vault if you go and grab the link below and sign up
You can get the complete Claude Skills course guide. This is going to be your walk along with all the prompts, etc. in here for you to use along the way.
So there's some super powerful stuff in here if you want to build along with me. So what? is a Claude skill?
Well a skill is simply a set of instruction Claude keeps to run on command. It's essentially giving it a step -by -step checklist or a standard operating procedure that tells Claude exactly how to complete a task. So you can write down a process once, give it to Claude in something called a skill .md file and then anytime you want Claude or any other AI platform to actually run that process or that task it can go and look at the step -by -step instructions and follow that process and the benefit of that is you give you the same output every time so every time you ask claude to do something it follows the process to give you the same output you can think of it as simply as a prompt if you've got a really great prompt that gives you a great output every time that's essentially a set of instructions of how to complete a task you can take that prompt and build it into a skill that's the most basic form but you can go a lot deeper and wrap a lot of stuff up in these skills to complete a task and the beauty of this is you might think well i've already got prompts why do i need to build them into skills well every time you want to find a prompt or complete some work you have to go find that prompt copy and paste it in actually repeat the process
And it's not that smooth in a very basic level. A skill actually can fire for itself. You can either tell it to run that process or it will naturally run these processes based off other work it was doing.
So a lot of the time you might build these standard operating procedures into your clored workflows and you might not even know that the skill is running. It just might run automatically. For example, I might be asking about the performance of a particular website and it might just go and run my SEO audit skill automatically without me even thinking consciously to go and run that process.
Equally, we're going to build something called like a voice copywriting skill, which teaches how to write in your tone of voice for your brand. Every time you output a document, for example, it might run that voice copywriting skill to make sure it's actually applying your tone of voice, your anti -AI writing rules. to your output, whether that's proposals for clients, LinkedIn posts, or general documentation around your business, work, life, whatever it might be, even just replying to an email.
So a skill is a set of instructions, step -by -step, that tells Claude how to complete a task, wrapped up and ready to run, that you can either run on command, you can just tell it to go and do that job and it will do it. or it might just start doing it automatically because you've roughly asked and described the job that you're doing in the rest of your work.
Next, I want to talk about what actually makes up a Claude skill, the anatomy of a Claude skill. It can be as simple as one file with just a wrapped up prompt, but it can also be a folder of information with several different files in there, and I want to break this anatomy down for you here. So I'm actually going to show you in my Claude environment here an example of a skill, and you're going to start to see how we can...
start using these to find the Claude skill you go to customize on the left here and then you'll see it'll automatically jump into skills it will give you a discover tab for others that are already built into Claude or you can click yours and it might show you some that you already have if you've been building them you can actually scroll down and you can click on one and it will bring you in to the actual the back end of the skill, what these actually look like.
Now, there are three main parts to a Claude skill. Number one, you'll get the overview, the description. This is exactly what it sounds.
It literally describes what's going on here. So this is an SEO blog writer skill, one of the ones we're going to be building today. It converts my YouTube transcripts, voice notes, rough content ideas into SEO optimized, published, ready blog posts in my voice.
So we already know what it is. going to do. We also have built in here the trigger words and these are really important in the description because you can see here any time that I would say something like turn this into a blog post, use the SEO content writer, turn this into an SEO article, write this up into a blog post from a transcript.
Claude is just going to automatically do that job. I don't have to specially invoke the skill with slash commands necessarily. I can just sort of be working naturally and say, hey, can you do this job?
Or anytime it realizes it should be doing that job, it's going to fire this skill. So it's always reading this description about what the skill does and how to actually invoke the skill and make it run. Now we also have this button here, the contents.
And the contents is made up from two key areas. You have the skill .md. And a skill .md is...
literally just a markdown file. It's a text file of the instructions here. So you can see on my screen here, we've then got the SEO blog writer.
These are the instructions that it has to follow. It's got a five stage step by step workflow. It goes through stage one.
It goes through stage two of drafting the article. It has the article structure of exactly how I want these set up. The voice rules, what it shouldn't do.
Has stage three, wrap the SEO in production package. Again, how to wrap it all up. It does a voice audit to make sure it's running against my voice that I've trained Claude on, on that skill.
And it's also got an editorial pass to act as a grumpy, grouchy newspaper editor without asking permission. And then it's got the output. So essentially, what you can see here is that this is just a really long set of instructions.
It's essentially a super -duper detailed prompt. Now, if I was to try and just use this prompt on its own, it would do an okay job, but it's quite a lot to just run in one prompting floor chat. So what we actually package with it as well are reference files.
You don't necessarily have to have reference files for all of these, but these are a little extra knowledge base for it to run off. And generally, these are things like templates, checklists. other things it needs to refer to to actually get the job done.
It might be a little bit of knowledge in there, or it can actually have things like Python scripts that can actually run automations for you in here as well. But in this one, for example, what I love to package in my Claude skills are an article template. So it's got a template of how it should use for everything.
It's got the metadata block, for example. It's got an internal links block, external links block, how the H2 body section should be formatted, how the headers should be formatted. All my articles essentially come out in this uniform templated manner based on all the other prompts that I've got in there to get the quality up.
We also have a checklist at the end because I think I had a review process at the end and it says, hey, can you go and review this as a grumpy editor? This is the checklist that it would actually go through to rate itself against. So it can actually rank and rate its work against this secondary checklist, which is its review cycle.
So inside a Claude skill, we have three main areas. We have the description, which I showed you at the start, which is what the skill does and how it's triggered, like how it should run. We have the skill .md file.
This is the main set of instructions as to how the job gets done and what. And in what order? And then we have the reference files.
These are not fetched at every stage of the process, but fetched when a clawed skill needs to do something specific, like the final template, a review checklist, any extra supporting information. And these reference files can also have scripts, essentially code that a skill can... call when running the same process over and over again you don't need to worry about too much these at the start of this but it's worth knowing that you know you can have code written into these reference files as well now sometimes people get a little confused about what should go in a skill .md file the main instructions and what goes in a reference file For me, I like to think it as the decisions it needs to make along the way.
So you can think about how the jobs run, what order things happen in, what good looks like, what it must never do. Essentially, as we said at the start, the step -by -step instructions about how to complete a job. What goes in the reference files are the supporting detail.
So you can think of these as the long worked examples, a full style guide. So you could say in the main skill .md file, hey, make sure to apply my full style guide at this stage. And then you could keep the full style guide in a reference file for it to go and reference at that point in the job, along with any schemas, formatting.
what good looks like, what bad looks like. Those long worked examples are some great examples to go in the detail versus the main skill .md file. Often, Claude, when you're building these, we'll know.
and it will understand where to put each thing. But I think it's important for you to understand this when you're building as well so you can delineate between the two options that you have when you're building. Now, the final area to talk about here is the description and the triggers.
The triggers are really important because you want to make sure it's actually firing at the right time. So you could actually write into your description area at the top of a skill here, remember. You could actually not have any trigger phrases in there and just make sure that it's only triggered when you...
actually command and select that skill to run versus actually making sure these trigger phrases are actually quite right so in here I've got an example write up this transcript here it's quite vague like I would probably actually looking at this remove this trigger phrase because I do a lot of things with transcripts and I don't want it to accidentally fire a skill so if you find your skills are accidentally firing through the way you're working then you might want to check your trigger phrases to make sure they're actually aligned.
Equally, I have multiple brands. So I actually sometimes name the trigger phrases to actually make sure it's running for Half Day Thursdays, which is my AI community that helps people gain more freedom of time in their life versus ElliotPrince .com, which is my personal brand. So if I'm building similar skills between the two, I have to delineate in my description of like, hey, can you do this in the Half Day Thursdays brand, not the Elliot Prince brand, for example, in my trigger phrases.
So really important. here try to actually make sure it's putting trigger phrases in there that are words and ways of phrasing things you actually use naturally in your work not that you kind of have to keep remembering and thinking like how how do i invoke that skill again and don't worry of course we're going to get into all of this how they actually run in this course so let's get into how you actually use a claude skill because if we're trying to build before we even know how to use them then we're going to be in trouble I showed you that SEO content writing skill and I talked about trigger phrases and how to run them on command.
I want to show you exactly what that means. So there's two ways you can actually run a Claude skill in your account. The first thing is you can hit forward slash here and then it's going to give you a list of all the skills that are available to you.
Now you can scroll down this list and actually start running them or you can type in here and you can say. SEO blog writer and it will come up with there. You'll see the little description of how it runs and you can click that and it's going to highlight blue and you'll see now that Claude's skill is actually ready to run.
It's 100 % selected in my account. So if you want to make sure that you're definitely 100 % using a Claude's skill, you use that slash command. It's called a slash command method.
Now the other way we can run this is by actually saying those trigger phrases. So when I was talking about trigger phrases in the previous... section we actually were talking about just using them conversationally in your workflow so i would say something like hey i want to turn this youtube video transcript into an seo blog post here's the transcript let's get to work and because i used one of those trigger phrases turn this youtube transcript into an SEO blog post.
Now, this wasn't an exact same phrase that I had in the main description there, but it's really close. It's close enough that Claude's going to be like, okay, I know I need to use that skill. If I go and grab a YouTube transcript and we will paste it into the chat here, it'll come up pasted there and then run this.
You'll see that it actually starts to get to work. I haven't had to put a massive long prompt in there. The skill should invoke automatically because I've used the right phrasing.
Here you go. You can see it in the description. of what's going on, turning the video into an SEO, reading the SEO blog writer skill to convert this into this.
So you can see it's loaded the skill there and it's starting to use it. It's using the template structure, the SEO checklist, all of the reference files in there as well to actually complete this job for me. And that's the beauty of a skill.
Once you have a defined process, you can just start using them conversationally in your work and it will automatically then be able to run that task. We could also set this to run on a schedule to go and scrape my recent YouTube video transcripts, bring them into Claude and actually create the blog post and then connect up to my website and go and publish that blog post for me automatically as well.
We can teach you that whole process, which is kind of what we're going through in this video in many ways. Now, before we build as well, we'll just talk through some of the customized area of Claude because I want to show you how to actually add a skill to your account because some people might send you skills or you might.
download them or you might come across the files in many different ways because you can just share these files between people as well. So if you've been sent a skill file, they're actually really easy to upload to your account. All you have to do is go to customize on the left hand side here.
You go to add and then you go to upload skill. You'll also see there's buttons like create a skill, create with Claude, record your screen, which we're going to go into. But to add one that someone sent to you, you click upload skill.
You go and find a skill, for example, add that to your account, click save. and then it's going to be ready to run in your environment. You can upload that and you can invoke it just as I described before.
You can see this one is actually got a whole bunch of reference files in there along with the description as well. And as well, you can turn them off and on. You can turn them off and on on the top right here.
If you have them in your account, but you're like, they just fire when I actually am not working on that sort of project, you can turn them off. You can also download them. So you can go and download any skill in your account and send them to other people as well as the ability.
to edit the text so if you just want to actually change a trigger phrase or a description you could just go in and type it yourself really easily or you could actually click the top three buttons here to click replace in chat or even remove it delete it from your account for example so it's very easy to sort of manipulate move upload these skills in your account And now you understand the sort of basic fundamentals of a skill, how to add them and download them from accounts.
We can get on to actually going deeper into the types and levels of skills that you can build. Now, when you're building clause skills, it's really important to understand that there's actually two types of skills that generally we're building and they... deliver slightly different outputs the first one i like to call deterministic skills and these always give the same outcome you know exactly how you want the process to finish it might be something like an audit an invoice a monthly report it essentially comes out as a templated output when you think about the seo blog writer skill, I was giving it a messy input and it was giving me a templated output essentially for that skill.
Now, I also have them for an invoice. An invoice, for example, I always know it needs to come out in the exact same PDF format with the headers in the same place. Really, we're just switching in and out the numbers and some of the details in there.
So it's actually really easy when you're building a deterministic skill. It's really easy to understand when they fail because it's pretty loud. If my invoice comes out and it's not in the right template or there's a column missing, the numbers are wrong, it's really obvious to see and it's pretty easy to fix.
These are generally the easiest types of skills to build because you say, well, this is the output I want in this template. Here's the type of information going in and you're essentially just taking that information and placing it in that template for me. Fairly simple.
but super, super powerful in getting rid of some of the busy work in your life. Now, on the other side, we have what I call non -deterministic skills. And these are skills that more carry judgment, taste, voice, and there's no set output that comes every time.
So again, you might think of this as like your voice skill, your brand voice skill. It can be applied across many different situations and there's a lot of decisions and judgment and taste sort of building in there, thinking patterns, for example, that need to be taken into account. And these can be harder to build because it's not as obvious when they go wrong or they require a lot more back and forth and training.
They could be thinking frameworks, second opinions on certain frameworks as well. It's really hard to actually define the perfect output because every output is slightly differently and that means they fail. kind of quietly they might look good the first time you've actually built them and run them but there's no clear flag of an error or where they're slightly drifting they have to take you have to keep a little closer eye on them and they tend to take longer to build and train and get into the place you want so really when you're building think about it in these two ways is this a deterministic skill where i just want this clear defined output or is this non -deterministic which actually is applying more judgment, taste and voice across others.
They're sort of more non -deterministic ones. You can think of them more of like they're an art rather than a science. There's no perfect formula or perfect output.
They always require tweaking and upgrading versus deterministic, which is almost a mathematical or an equation or a scientific output that comes out the exact same time, the exact same way every time. Now, we also have five. levels.
So we've just gone through the two different types. There's also five different levels of Claude Skills, which really comes down to complexity. We have level one, which is essentially, it's essentially a very simple wrapped prompt.
We can just trigger it. It doesn't really require any extra input. It doesn't require anything from us.
It doesn't connect. It just, hey, can you just do this for me? And it will run automatically.
Very, very simple. The level two is an ask. So it actually needs some more information for you.
So yes, it can run really easily, but you might need to give it more input. You think about the SEO blog writer skill. It's an ask because it needs a transcript.
It's going to ask me some questions to actually get towards the final result rather than maybe an SEO audit skill where I can just give it, hey, can you audit this website? And it will go and run the audit. The level two needs more input, more of my human insights and expertise built in before it can actually deliver its great output.
These are the two levels that most people sit at because it's very similar to writing a normal prompt. Ready to go in cloud is what we've probably all got used to using AI and chat GPT from day one. Then we move into level three.
Now, level three is where we connect. We can actually allow this skill to reach outside of Claude using something called connectors. Now, there could be some very simple explanations of this.
You could, I have a great one. It's a morning. inbox triage skill and it's able to go into my gmail it knows i've trained it step by step what to do in there where to file certain things away what to do it doesn't reply to my emails for me but it could actually reply to emails for me if i wanted it to this is more of a process of getting rid of all of the junk and stuff that doesn't need my attention and leading the key stuff that doesn't need my attention.
So we can actually train the skills to go and reach into our SaaS tools either to retrieve information. So again, we can upgrade our level two skill by linking it to the... YouTube API or connector getting it to go and automatically fetch my transcripts and actually write the blog post when we do that when we connect it up to either go into a tool and pull information or push information to a tool you could push information to We could push that blog post into a website or we could push it into Notion or a Word document for me to go and check and make the final edits.
Or it can actually drive a software tool as well. So it can actually click around and use these tools for us as well. That becomes a level three, a connect skill.
And again, I find people get to this level pretty quickly once they realize that they can build in the right links and connections in their skills. Where people don't often make the jump to is level four. And this is a chain.
or a team of skills working together. So you can actually build your skills to hand off one to another, either one, two, three, four, or to make decisions and go left and right, etc. Now, when we build today, what we're looking at is a set of SEO skills.
And there's a very defined process that an SEO department or an SEO specialist would actually go through step by step. They would run an audit. then they would write an SEO strategy, then they would start creating the website content, then they might actually publish that SEO content, and then they might write a report and a commentary, analyze, and then almost repeat that process.
So we could actually get the skills to go one for another. I could get my... seo audit skill to then feed into my strategy skill to give it the information the strategy needs to write the strategy once we have the strategy the strategy skill can then feed into the creator skill that's going to go and write a blog post for example and then you can get what are called chains of skills and it becomes like a complete production line that becomes a full workflow not just one skill individually And then we get onto level five, which is the highest level.
And this is where you build a manager skill, an orchestrator skill, which when you have lots of skills chained together or lots of them that can interact, you can build an orchestrator, a manager that sits on top, that knows what each skill does and how they interact with each other. And can actually, you could give the orchestrator, the manager, the line manager of these skills, my overall goal, or like say, hey, my website traffic is...
has gone down, can you help? And it would know which of its teams to go and invoke and how they link together and start working, which is where we get this sort of team, this whole department of little AI employees running in our business. So we will be getting to this level by the end of this course as well, which is super exciting.
But I think it's important to say that there are two types of skill and they can be across all levels, but the levels aren't a scoreboard. A level one skill isn't worse than a level five skill. They're just different.
You can get a lot of value out of a level one skill that just runs automatically every morning for your business, even more so than often a level five skill, which a lot of people over -engineer and they do it to prove that they've built this whiz -bang amazing system. but it's actually not that well constructed and it's just overcomplicated compared to if I just had one of those skills running perfectly would be more leverage for certain areas of my work and life.
So just know that just because you can build a level five management team of skills, it doesn't mean you actually have to. It's all about the pain and problem you're trying to solve in your business. for your work, that's the real goal here to free up more time in your life and more wealth in your life.
I mean, if AI is not doing that, then it's not really working for you. So a level one skill that frees up two hours a week of work for me is a massive, massive win versus a level five skill that kind of needs a lot of troubleshooting and managing just to get it working. So with that all said, let's jump into actually building our first skill.
We're going to go through the three main ways of building skills. And we're going to start with the easiest and simplest one. And this is taking a prompt and wrapping it up and making it fire on command.
And before we actually start working in this window, we need to just go into our settings here. We need to go into customize and we need to go to skills in the middle here because we need to actually make sure something is turned on in our account. We need to go into the search skills and plugins and I want you to type in creator.
Because when creator comes up, you should have this skill in your account, skill -creator by Anthropic. This should be on by default. If it's not on, go and find it and switch it on because this is actually a skill inside Lord that's going to help build for you.
It's designed by Anthropic and Claude to know the exact processes and requirements. You can see there's a ton of information in here. You can see all the reference files, the scripts, the graders, the analyzers, and just the general process of what it should actually do and some of the requirements, such as here, the three -level loading system, the data, the skill .md, and the bundled resources that we broke down earlier.
This skill knows all of that, and we can use this to actually build and package all of our skills forevermore. I'm not going to sit here. and teach you how to type this by hand because it's much quicker just to use AI to help you build.
So the first thing we need to do is we need to make sure our skill creator is turned on then we need to invoke it in our chat window here. So to do that you can hit forward slash and we can type in creator skill creator select it and we know it's definitely turned on. Equally, you could just say naturally in your conversation, and I'm going to use an app called WhisperFlow here that allows you to like talk and dictate to your computer.
Can we build a Claude skill? And just by saying build a Claude skill or create a Claude skill, it's actually going to make sure that that's invoked. So you could do it either way.
For the purposes of this, I'm just going to use this forward slash command here to get things working just so for an illustration. But often I'll just say, hey, I want to build a cloud skill and it will invoke the builder skill for us. Next, I'm going to tell it exactly what we want to do.
So I'm going to say, I'm going to give you a prompt. for an SEO audit skill, I want you to take this prompt and wrap it in a Claude skill so that I can fire it and invoke it at any time. Very simple.
I'm literally just telling it what I actually want it to do or how I want it to build this skill straight from off. Then in this document that I've linked below, you're going to find this way one wrapper prompt. You're going to scroll down.
It's going to say, hey, make sure the skill creator is turned on. Take this prompt and turn it into a Claude skill. I can run on command.
Everything's here for you to run. Then I'm going to copy this prompt. You can do the same if you want to build along with me, but you can see it's a really detailed prompt that I used to copy and paste for audits that actually now, instead of me having to go and find this prompt and edit it, et cetera, we're going to build it into a Claude skill.
But essentially you can see it's giving it a role at the top. here it's got some input it just needs the url that i want it to run on it's got the different steps that i want it to go through and then the output the exact output that i want it to give in detail so i'm going to take this prompt i'm going to copy it and i'm going to i'm literally just going to paste it into the claude chat here and then that's all we need to do we can send that message and claude is going to go and analyze everything and build our skill for us you'll be able to see in the chat here that it's understood the task it's got to go through.
It's going to go and view that file. It's actually reading the skill creator skill here that we discussed. So because we've invoked it here, it's reading the skill creator skill before building and working out the process that it needs to follow.
So what we're building here is a very simple, it's a level one skill. It's a pretty deterministic skill because level one, I'm just going to give it a URL and nothing more, no extra expertise. And it's going to go and do the job and give me a formatted output.
so it's a level one deterministic skill for us very simple and this is the easiest way to build them if you've got prompts that you're like i really like using this this is dialed i just want this ready to use on command in my claude account now it might take a few minutes to actually complete this build but what we get out the other end is on the right hand side here we get the breakdown of our skill and on the left it's got a little bit more information about what it's done it's called it the search visibility audit skill i mean we could have actually given it more direction of what we wanted it to call the skill but i quite like that it's got the description and how it actually runs.
It's actually looked in my account and made sure it's not triggering in the same process as some of the other skills I have running in there already, which is really useful. You can actually go and turn other skills off or delete them if you are running into old skills that you don't want to run. It didn't run a live test audit against the skill, so it might be important.
Sometimes Cloud will actually run a test of its skill for itself, but I prefer to actually test a lot of these personally so I can actually see the output and give it feedback. So once we have our skill built, we can also see on the right hand side, we can break down. Remember, we had the anatomy here.
So we've got the description and we can look at kind of explains it what it does. that this one is doing our SEO and GEO audit here. You can see the trigger phrases it's got running and how it would run.
And then we've got the step -by -step about how it actually works and importantly, the output that it's going to deliver. Now, this one doesn't actually have any reference files. It didn't need any reference files particularly.
We could certainly give it more templated structures, but because it was just a... prompt that we really liked and ran. We didn't really need any upgrades.
We didn't need any extra reference files for it to run. So in this case, we only have a description and the main sort of skill instruction is running. Now all we have to do is click save skill here and you'll see it saved that skill and it's ready to go.
If we go back into our skills area, you can click manage in the bottom right or remember to access your skills. You can go to customize and then click yours. We could search for the skill.
What was it called? The SEO visibility. And you'll see when you search for it here in your customized area, we'll see it come up and we can go and investigate and use and check the skill as it was built, which is pretty cool.
It's ready to run in our account, which means now we can test out our first skill build. We could actually say, hey, can you run an SEO audit on my website? HTTPS.
This is a website that I own that's actually not typed out at all, right? I'm just going to type it out here and you'll see I could invoke it. Remember, I could go forward slash search visibility audit, but actually because I've just said, hey, can you run an SEO audit?
It should automatically invoke this skill for me as well because that was one of the trigger phrases there. So what we can see straight away is we've built a skill. there by wrapping up a prompt and then you can see we're now testing it and it's invoking it you can see in the middle of my screen here reading the search visibility audit skill for this audit and it's going to go and do that job okay and here we go the skill has finished working for us and it's created our search visibility audit on the right hand side here in this nice artifact it's given us our nice verdict it's given actually a review of what it actually did and the score in there as well, where what's broken and what needs actually fixing on there.
We've got things like every page reads written by admin rather than having the actual author on there, which was probably me a lot of the time when I built this site. We've got our breakdown of different findings in this nice format and the evidence and citations. What else have we got?
We've got the fix list. So we've got literally step -by -step things that we actually need to go and fix. the long game of the strategy that we could be employing, and some new pages worth upgrading and building.
We've got 15 pages worth actually upgrading and building here, and some tips that need to be rewritten to get cited by AI Search. So this is incredible. This is super in -depth.
This is a super valuable report anyway. Previously, without a cloud skill like this, this might have taken me... days to actually compile a full in -depth report like this.
Now, because I've built my expertise into a prompt there, to be fair, now we can just run this skill on any site. So I can either work more quickly to do a lot more work for a lot less time, or instead of spending a whole day or two days on an audit, I can just run this skill, have that job done, get onto some other higher value work, or go walk my dog on the beach, hand over work to AI.
Or I could even say, hey, I'm going to... do this at low cost or free or just as a value add for a client now, because it honestly cost me nothing to actually run this really, except for a few tokens. And it was now super easy to just wrap that skill up in that prompt and I can run it anytime I want automatically, even set it on a schedule to audit a website once a month or every six months.
So we've built our first level one skill here, just by taking a prompt, giving it to the skill creator skill and wrapping it up. And now it pretty much just runs by me giving it a URL and it just does the job for me automatically next we're going to build our a level two skill actually which is going to need extra expertise and input from us when invoking the skill but also We're going to talk about probably the best way to build skills.
Now, the first one worked really well because I had a prompt that I'd spent a long -term dialing on my expertise rather than just going in and saying, hey, can you just build me a prompt that does an SEO audit? It wouldn't have much direction. It wouldn't be very good.
And when we talk about building the best skills, they're actually built in with either your expertise or some that you borrowed from other places. These are the best skills. You either want to bake in your expertise and processes of how you do things.
or if you're not actually sure, research and use other experts in the industry. But these actually take a little bit more time to build than just saying, hey, wrap this up. We actually need to run this basically from a cold start as if we have nothing.
And to do that, we're going to actually run the process. We're going to teach Claude the workflow that we want it to actually execute for us and then capture that process, okay? And we're going to rebuild the SEO blog writer skill.
can write SEO optimized content based on information you give it, not just making random things up and scraping other information from the website. It's actually going to be a useful SEO blog writer skill, which I don't really see many other people building this way with content that actually ranks and isn't just 100 % AI generated, if you will.
Now we're starting from a cold start. So I'm not going to start by saying, hey, can we build a skill? I'm actually going to work through the process.
So I'm just going to start by actually giving Claude my pain point and then the outcome of what we're trying to actually do here. And I am going to voice these prompts in, but I will put these prompts that you can then go copy paste in the main notes with this section as well.
So I want to take a transcript that I have and I want to turn it into an SEO optimized blog post. Before we get to work, I actually want to research and create the process or the exact way that we should approach this task before going and executing it to make sure we're delivering SEO content and GEO content to the highest possible best practice standards.
Now, I have a couple of ways that we're going to do this. One, I want you to research the best practices at the moment, the most up -to -date information and build me the... SEO, GEO, blog writing, standard operating procedure, the system that we can always follow and the template we should be following.
I'm also going to give you a transcript of my expertise and some of the extra ways that I like to build my SEO articles basically. So you can see here I've just voiced in what I want to do. goal I'm trying to achieve I don't want to build the skill or actually do the job yet I just want to research and outline the best practice and the process we should be following and I'm also going to because this is quite a long task and it's multi -step and there's a lot of research I'm actually going to invoke co -work mode and co -work mode is great because it allows Claude to actually take multiple steps and actually complete tasks for you and because i've got things like hey i want you to go off and research and create a report it's great to do this in co -work mode rather than chat which will just do one for one it'll you'll ask a question it'll give you an answer back maybe do a bit of research co -work's actually going to be able to do longer running tasks in our build here so that's a useful switch to turn on as well so the process here
And this is why this is one of the best ways to build skill is we're starting cold and we're building in expertise. We're not just letting Claude dictate what it should do. We're actually working back and forth to train it on our process.
So it might ask you a few questions in here in the primary goal of the SOP. Is it for a particular website? or is it platform agnostic?
I just want it works for any site. I just want it to work for any site in this scenario. How should the SOP be delivered?
It might offer you to actually deliver them in a Claude skill. I don't want to do this yet because I don't want to lock the process into a Claude skill until we've actually finished it and got it really defined because we will be working back and forth to actually make some improvements. So I'm just going to say mark down SOP and template docs so that we're not locking anything.
too aggressively before we've defined it. And it's just going to ask me for the transcript of my SEO process, essentially, because that's one of my areas of expertise. So I might as well use that.
The more you can use your own expertise and processes here, the better. So I've actually pasted in here two transcripts from previous content I made, which is how to write content so good you can't stop ranking number one and where to put keywords on your website. I used to talk a lot about SEO on my YouTube channel.
Honestly, I would also go into potentially some of my frameworks and SOPs I have saved in my Google Drive, any templates I wanted to follow. Or even if you don't have transcripts, you could just brain dump your process, even ask Lord, say, hey, can you quiz me? Can you ask me five questions about my process so that I can give you my brain dump on the process?
But essentially, because I've got the transcripts already on my processes from some of my teaching, I might as well use those because that is stuff based on proven tactics. and ways of working that actually run versus just trusting what other people are saying. I'm also going to get it to go and research some of the most up -to -date practices because some of those videos are like a year old or two years old now.
So I just want to make sure that some of this stuff is the most up -to -date based on the most recent. updates research expertise out there you'll see on the right hand side here as well one of the beauties of using claude co -work is it can track its progress you can see that it's actually mapped out all the steps it needs to do whereas claude chat would just give you an answer straight back and it would just do one little bit of work at a time CoWorks mapped out exactly what it's going to do.
It's going to research the best practices. It's going to research GEO best practices. It's going to research my articles and fold in my expertise layer to then write the SOP, the templates, the QA checklist that you did see in the skill that I showed you originally that we're rebuilding here.
And then it's going to verify everything. So this is a serious amount of work that it's actually going to cruise through for us here to build out this process. And I should say why we wait for this to build as well.
The skills you build here, When you build a Claude skill in any area of the application, I'm in the desktop app here, but anywhere you build a Claude skill, if you build it in Claude Chat or Claude Cowork, they are available across both and then they will actually work in Claude Code. On the other hand, if you are building skills in Claude Code, they won't translate back into your Claude Cowork and Claude Chat area.
So often I like to build in Claude Cowork because I know then I can build them everywhere and use them everywhere, wherever I'm working, particularly for this knowledge works. type of stuff rather than the actual coding and building work type stuff so you'll see here even though i'm in claude co -work mode if i go to that visibility search visibility audit skill that we built earlier, it would be invocable in Cloud Cowork, even though we actually built it in Cloud Chat.
So you don't need to worry too much about where you're building this stuff because they translate across both platforms. It might take a little while because we've given it a lot of tasks to do here. You can see mine has worked its way through all of these tasks and given me some output about, you know, it's received both transcripts here.
It took about 20 minutes to actually do this. You see I've gone on... A little chilly today, so I put a little cardigan on, made myself a cup of tea, and actually I've been reading a book sometimes.
Instead of scrolling social media or getting distracted by other tasks, I'd like to go and read a book. I've been reading Simon Sinek's Start With Why at the moment, while Claude does my work for me, which is nice sometimes. It's given me the headline findings and three...
places evidence corrected by you in terms of it did some of the research and then it relied on some of my expertise before building out gave me some sources that it had checked as well so i could make sure these are actual uh good quality sources i could have defined the sources if i knew them up front as well or some experts that i wanted to to follow but essentially we've got our sop now this thing is actually pretty beefy uh stage one stage two stage three like this thing goes super deep keyword fan out and research um you know this thing is insane about how to go and create an sop blog post this i think this goes a bit deeper actually uh sorry about the scrolling here it's actually doing keyword research for us as well And then it's got like, again, you can start to see the building blocks of what we're building here.
It's got the article template about how we want to template each article, the published checklist to make sure this is actually done, etc. And for some reason it produced them twice for me here. I don't know why it produced them twice.
But essentially it's built four documents here, the main SOP and then some supporting evidence and templates, etc. Now you might be tempted here to be like, great. turn this into a Claude skill.
But I don't know this is actually working quite right for me yet. So I would actually test this out. And to do that, I'm going to use this process now.
So I'm going to go and get a transcript and we're going to run this process in this chat. I'm going to use this transcript from one of my most recent videos, the three levels of Claude memory clearly explained. You could use all of this process or you could actually, you could find your own, brain dump some information into a transcript and give it as well.
However you want to generate a transcript is fine. I'm actually using a quick tool here, youtube -transcript -io just because it's super quick to actually grab transcripts and it doesn't use any of, we'll just grab that again. It doesn't use any tokens in Claude to actually go and do this.
You can scrape transcripts with AI tools, but this is also equally useful. So I'm just going to say now, I'm going to say, can we test out our SOP? Then I'm going to give you a transcript about clored memory.
And I want to write a blog post that targets the keyword clored memory. Okay, so you can see quick prompt here about let's test it out. This is the keyword I want to.
target and here's the transcript and then we can run this and we're going to see how all of this performs before we actually lock this process into a skill so we can see it's starting with stage one mine the transcript which is perfect it's going to go and get all the information for me okay so our sop has finished running this process it's given us some output on the left hand side here about some of the processes it went through it caught itself over optimizing on how often it put memory in some of the headings and stuff And then it's got some information about confirmation it wants before it ships.
So some gaps it couldn't fill because I didn't give it a site and some other quotes that I put in there. It just wants to confirm everything. And then on the right -hand side, we actually have the outputs.
Put it in a markdown file. I might actually say like, hey, I'd prefer you to output these in a Word document for me so that I could edit them. And then we can actually see it right.
One of the beautiful things here is it's actually pulled direct from my transcript. I like oranges. That's setting my cloud.
memory for months. So let's use my keyword early on. We've got the keyword in the title.
I'm not 100 % convinced by the title. I'd prefer it to be more on the nose for SEO purposes. What does Claude actually remember about you?
We could probably use AI memory earlier on in these subheadings. So it's not got it 100 % perfect, but on the whole, this is a pretty well -optimized, well -written article. pulled from my transcript and bolstered by some research, which is cool.
We've got some comparison tables and what it does and doesn't cover. Now, I think I'd like to actually just bake in a few more things. I'm not going to lock this in a skill yet because I'm not 100 % happy with the output it's actually given me.
So I'm going to give it some feedback about some edits I want to make to the article. Okay, I want... to just make some edits to what's going on here.
On the titles, I want them to be more on the nose. So I would be something like clawed memory, clearly explained brackets and how to set it up. Then I'd like to make sure in our first H2 that we have the keyword clawed memory in there.
And I'd like it also to be like in the further down H2, I want it to be how to set up level one clawed memory on purpose. So we're just getting a bit more keyword rich in there. The other thing I think we've missed off the bottom is I'd like a short FAQ section that is the most commonly asked questions.
The top five also asked questions about clawed memory would be great to have in there with just like short one or two sentence answers to each questions. Can we make those edits to the article, please? So I'm going to go and get it to actually.
Do the next round of edits on this to get it a bit more closer to what I think is a great SEO article versus it's just dropped the ball in a couple of places. So we're working back and forth until we get the output exactly how we want it. Okay, brilliant.
It's gone and spent another minute or two just doing those edits. We can see Claude Memory more in the titles there. The title, the main H1, the header of the page is more on the money.
And then on the right -hand side here, we can see we've got the FAQs coming in nicely. So I'm pretty happy with this. Now I'm happy with this process.
I'm like, great. Our SOP and everything has been worked through and we've got everything in there. Now I'm happy.
I've essentially trained Claude on how I want it to run this process each time. We're going to lock this into a skill. Now there's two options here.
You can go to the top of your screen if you're working in Claude co -work mode, click this down button here and click turn into skill. And that's just going to put a prompt in the box on the bottom left here, turn this into a skill. And we can learn from this that all we have to do is ask it to turn this into a skill.
I'm going to give it a bit more direction. I want you to create an SEO, blog writing skill that captures this process the way we've got the final output now and everything we've gone through in this task and chat it should be able to run on a transcript or a brain dump transcript a video transcript or even any other long form inputs i give it if the user hasn't given you any inputs or you need more information you should quiz the user before actually getting to work so that you have everything you need and quotes you can pull from the user so essentially just giving it a little bit of direction giving it a little bit of setup about how it should set up task as well before following this process out And so every time you complete a task in Claude, really, if this is something you're going to do again in the future, you can capture that process once you get the output right.
I find a lot of people think, oh, it took me so long to actually run that process. It would have been quicker if I just done it manually. That might be correct the first time you actually run a process in an AI tool.
But once you actually capture this and say, oh, I've just taught Claude how I like to do that job, capture that in a Claude skill. And then you can just run it on command rather than having to run the whole process again with multiple prompts and back and forth, etc. We can capture this moment of expertise and workflow at the moment that it hits perfectly for you.
And that's the real unlock you start to get from Claude's skills like this. Yes, the first time might take a long time, but the... From then on, we've captured the process to run.
Okay, and it's gone through now. It's gone and analyzed everything then in this process. And we've got the SEO blog writer skill proposed, turn a transcript, brain dump, video transcript, any long form input into a blog post in Elliot's voice.
You could make this agnostic to different people as well. We're going to build a voice skill later for you as well. So you can review all of this.
and the content included. But I'm pretty happy that it's going to have exactly what we want in here. We might give it a quick read through some of the corrections.
You can see some of the house rules we discovered in actually running the process. This is so important, actually, this house rules section, because it didn't know some of this stuff until we actually ran the process that it actually needed to do. So zero em dashes, title case H2s, numerals, on the nose titles, FAQs are standard.
So it's baked in all of that feedback and actually... running the process. A lot of people will just bake the Claude skill and then it will fall down because they haven't tested and refined the process of doing it before actually creating the skill.
So this is why this is so important to actually do this way. So I'm pretty happy with this now and I'm just going to click save. That's it.
We've now built from hardcore expertise. We've built our SEO blog writer skill. We can actually go and now go to our customize area.
We should be able to go to yours and then go SEO blog writer skill. You can see it's a brand new one. It's tagged up with what it does.
We can see something we have actually missed is we didn't give it the trigger keywords. So turn the transcript into a brain dump. We haven't actually put any trigger phrases in there.
which is an interesting miss that we got. And then we have full SEO blog writer skill baked in there for us. So I might actually go and just do one last thing because I'm not quite happy with it.
Now I've actually looked at it. I might go and say, I'm actually going to go and just, I'm going to click this try in chat button. I'm just going to say SEO blog writer.
Can we just make an edit to them? So we're going to edit a skill now and you can do this very conversationally. Can we just make it to this skill?
It doesn't have any trigger phrases. Can we just put in five core trigger phrases into the description, such as turn this transcript into a blog post, help me write a blog post. And then we should be able to just quickly, we could have done it in the previous chat as well, but I'm just going to show you, you can pull any Claude skill and actually go and edit them really, really easily.
Just if you've just missed something or you're not quite happy with it. You can conversationally edit these skills, which will happen a lot. I update mine a lot because things change.
You spot new improvements. Stuff just doesn't quite work for some reason. And you just need to go and update and just give it some more rules, some more information to actually start working with.
And by the way, when you're using Claude Cowork as well, you'll see on the right hand side, this doesn't show in Claude Chat, but in Claude Cowork, you actually see because you might be running multiple step workflows. You can see in the context on the right hand side here that you can see what skills have been activated.
and even click on them to actually have a closer look at that skill as well. So when you start stacking these, you might see multiple skills being invoked on your task board here on the right -hand side. Okay, here we go then.
It's actually gone and made the edits, turned this transcript. We can see the description in the middle here has now the trigger phrases that write an SEO article, write this up for my website, et cetera. It's gonna...
invoke the skill so i can click update on the right hand side here and boom it's updated the skill we're all good to go if we go and check the description now we've got all of that put in there which is beautiful so that's how you go from a cold start you don't have a prompt you don't have a process clearly defined to actually starting with grounding the the process in real expertise and research, bringing an SOP or a process for actually completing this, letting it do the work, give it feedback.
And once you're happy, once it's got that final perfect output, then we capture it and we can always just make some slight tweaks if it doesn't capture it perfectly. So that's the second way we're going to build a Claude skill. Next, we're going to jump into the third way to build a Claude skill.
And that's to show it rather than describing it. This is a feature called record a skill.
And essentially what we're going to do is we're going to literally record our screen within Claude and show it clip by click, step by step, how we do a task. Now, why would you do this as opposed to the other way? Well, sometimes you might not be able to complete a whole workflow in Claude.
That last one I did, I was able to work conversationally in the chat back and forth to get the output we want. Let's say, actually, I'm not quite sure how to describe it, or some of the job requires me to click around other tools around the internet. Because remember, Claude can actually use your computer for you.
You can use things like the Claude in Chrome extension, which I'll put a link in the notes as well and in the description for the Claude in Chrome extension, which allows Claude to actually use your web browser for you. Or you might actually have connectors that are set up, but you actually want to show Claude how you would use that connector.
So how do we do this? Well, next, we're going to build a reporting skill because this used to be a job that used to take me. hours and hours to do because I'd be clicking into things like Google Search Console, Google Analytics, even other SEO tools or manually checking results on a website search results.
And there was a lot of manual pulling things, downloading reports, etc. analysis that actually AI can do now. So to run this process, I'm literally going to screen share and show Claude and commentate exactly what I do.
It's going to record it and then lock that process down for me. So to activate this, you're going to click the plus button in the middle. First, you're going to select cowork mode here.
The second thing you're going to do is click this plus button in the middle. We're going to scroll down and we're going to find record a skill. And this is exactly as it sounds.
It's like creating a loom video or something with inside Claude. record a skill it's going to follow our screen clicks typing and voice are recorded and then sent to claude and turned into repeatable skill so it says you know don't put passwords or secrets or sensitive information in here because that's going to be captured by claude but Essentially, I'm going to start recording and then follow this process.
You can see my screen is glowing orange here and it's capturing what I'm saying. For the purpose of the tape, this is me just explaining to a viewer how to use Claude. So this task, we are going to show you the SEO reporting process of how I collect data, analyze it and write commentary.
compile SEO reports for clients. Now the first thing I will do is I'll open my Brave browser or my web browser and I will go to Google Search Console. In Google Search Console I will select the website I want to analyze.
This one we're going to do Courchevel VIP but we could do this for any website within my Google Search Console. Next I would click performance and I would select more and I would compare. and I would do the last 28 days year over year.
We do year over year so that the data isn't tainted by seasonality, et cetera, in most of our websites. Then what I would do is I would either scroll down and start reading the queries, looking for the pages that have been losing a lot of attention, the pages that have been gaining a lot of clicks, any changes in the data, looking for...
The good options and the bad options that have happened on the site, I would go through the different pages, see what's been performing well and what's been dropping off. And then I might even export the data and download it to a CSV to start analyzing and looking through the data or even giving that to Claude to analyze.
I would also go to Google Analytics and I would start looking at the same sort of information here, trying to understand the site's performance, what's up, what's down, what's stayed the same. I might also run some of my key search terms through a live Google search to just check performance directly. Once I have all this data, I would open up a Google Doc because I want to create a Word document.
And in my Word document, I would title it Website Name plus SEO Report as my H1. I would then have five bullet points with the good, the bad, the insights, opportunities, anything else. Notable.
And then I would write a one -pager explanation of all of this. I'm always trying to frame everything in a positive light. If there's something bad that's happened, we're reframing as an opportunity to regain.
We're also looking at the easiest, highest leverage things we can do and outlining what we're going to do for the next 30 days in our report. for the client. Then once I've written this document, I would be then going into my Gmail, creating an email to the client with the subject name month SEO report, month plus SEO report.
I'd write dear client name, and then I would give like a really short two lines about what's going on. And then I would say hey the rest of the report is attached below let me know if you have any questions and then i would send that email to the client okay so you see there i've just hit done it's actually outlined that i took 199 steps including all the clicks and commentaries and all the different things I did there.
It only seemed like a short process, but it's captured a whole lot there in that 291 second process. It's captured the whole transcript. So I've basically narrated my exact standard operating procedure for doing this.
What's cool is it's taken screenshots of the whole process here as well. So you can see it's taken a screenshot of every screen.
tracked every keystroke I've made even all the backspaces and mistakes and it's going to match that all to my commentary before creating this process for me so you can see the detail it goes into it's checked exactly what websites have been on and everything so it literally is like creating a loom video of a procedure that you're running or something you're doing and Claude being able to then take all that information and create the instructions to create a skill here.
You can see it's working its way through to suggest the skill it's going to build. Now, what's cool is, yes, we can use Claude in Chrome. It's like a genetic web browser to actually go and repeat some of those clicks that it's done for me.
So you'll see in my web browser that this Claude in Chrome, if I log in, this is an add -on you can get for. Google Chrome here that it allows Claude to actually use your web browser on your behalf. Now, it can either summarize a page, tell you what's on a page, or actually navigate the web for you.
I'll put a link in the description as well where you can find out more about how to use Claude in Chrome specifically. But just know that because I've done clicks around the web, the skill that Claude is made here might decide to go and use that Claude in Chrome feature for itself. It can drive it from the application here.
Or it might decide, hey, Elliot has a Gmail connector. I'll just use the Gmail connector to complete that task. So it is very clever about how it actually uses this.
It can see no Google search MCP is connected, so I'm going to use Claude in Chrome for that step. Further down, it actually says, hey, when we're drafting the client email, use the Gmail connector. So it's figuring out the most effective way to actually get this job done for me, not just doing exactly what I would do.
It's kind of mixing both. So we're happy with this. We should work pretty well.
We can click save skill for my SEO client report. And now we should have that ready to go. SEO client report.
So we've got our third skill built. That was really quick and easy to actually do. Got our third skill built.
We can actually run this SEO client report for, so we'll run it on Courchevel .vip again, which is the website that we ran that initial site visibility audit on here. You can see a ski website about. Korshevelsky Resort, basically.
And what's cool is it's actually read my memory there. It knows I own that website, so it's not going to have any problem if I say, you know, go and do something on this site or give me some more information because it knows it's my property, which is handy. And it's even actually asking me how in -depth do we want to go.
It can even say, decide to build a dashboard for me. I don't want the full dashboard at the moment, but actually that might be super useful for a client to visualize something. I'm just going to say, hey, do the report and...
email and then give me the last let's do last 28 days year on year you can start to see the power of these this recorder skill feature which goes and executes for you it's gone out and pulled the step by step on the right hand side here we can see the skill is invoked and now it's actually using claude and chrome web browser to go and run this process It's going to ask me if it can actually use that.
We should see in Claude and Chrome, we can see here actually, yeah, it's controlling my web browser. This is the actual tab that it's running. When Claude and Chrome is using your web browser, you'll see it's glowing orange.
So you can see. Now we've said, remember the first thing was go to Google Search Console. It's gone to Google Search Console.
The screen is glowing orange. You can see actually my hands are off this and that little orange cursor in the middle of the screen there, this one, is clicking around for me and collecting this information on my behalf. So it's automating this whole process because I showed it how to do the clicks once, and then it's going to just go and repeat every step if it needs to.
If it had a connector, it could go and just use the connector and do it sort of through the API, but it didn't. So it's doing the manual clicks that I did for it here as well. So we can just leave that to run.
Okay, check it out now. It has literally, all I said was SEO client report. It's going to run the whole process.
It's just finishing off writing the... report for us here it's actually run the skill and you can see on the right hand side it's used our gmail and google drive connectors because remember i wanted it to create a google doc and an email let's see if we go into my google docs here we've got the full seo report here the good the bad the key insights the opportunities and anything else notable and what we're going to do over the next 30 days beautiful the full commentary there we should also check it in my gmail draft dear elliot i was trying to write to me because i'm the website owner uh it's put in the full although it's put in the couple of lines we might touch this up and make it like a little bit more friendly um but the full report is here and then it's actually linked to my main google doc report Beautiful.
It's worked like an absolute treat. So we've gone there from zero process. I just clicked through.
I selected the recorder skill feature in Claude. You have to be running in Claude co -work for that to actually build what was a connected skill, a level three skill. Remember the levels of skills we had just a process that runs like a wrapped prompt with not much input.
We had level two, which needed. bit more expertise or input from me, either answering questions or a full transcript or a level three, which was the process we use to use recorder skill. And we've built it in with a connector as well.
So it's using connectors to actually go and complete a job there, which is just beautiful. Chef's kiss of skill building. So after ascending those three levels of Claude's skills, I just want to pause for a minute, take a break from the building to just talk about the six rules.
What takes a skill from being good to great? Because the next steps are actually going to get a little bit more tricky. We might start stitching, well, we're going to start stitching these skills together to work as a team and managers and stuff.
But I really want to give you some rules to make sure you're actually, the base you're building is really great. Now, rule number one is one skill or one job. The common structural mistake is that people try and get a skill to do too many things.
They try and build one SEO skill, which does everything from auditing to reporting to writing to whatever, or it just tries to cover multiple tasks in one go to give multiple outputs. If you're struggling and you're like, it's just not giving me the output I want. This is just not quite right.
Then my advice is always to split the job down and focus your skill on completing one thing really well. So if our SEO skills were struggling a little bit I might actually break it down and just say hey your job is not to be a full audit skill it's just to do the technical or it's just to do the content audit skill I do have some of my skills broken down to go to like more granular level but only if I'm struggling to get them to work so I'll start off by giving it one job and making sure it can complete that if it's still struggling to do that I might think how can I break this job down into even smaller tasks to get more consistent, high quality outputs.
So one skill equals one job, not trying to do everything at once. Now, rule two is, again, if they're not quite working properly, trying to keep that main file, that main skill .md file as tight as possible. Some people recommend about 500 lines.
There's no exact... hard math to it, but just know the longer and more in depth the skill goes, then the more likely it is to drift and start losing focus and run into problems. So again, if it's starting to drift and forget things and go wrong, think like, well, have I got a skill file, the main instructions area that's thousands of words long and trying to do multiple tasks.
If so, can we chunk that down or can we move some things into the reference files? For example, a template that's built into the main instructions. Let's move it out of the main instructions.
put it into a reference file for it to reference when it's running that particular of the task. So it's not trying to compute all of the instructions in one go. Rule three, this is a little bit more technical, but write code for the mechanical bits.
So I don't always rely on the LLM, the AI to do all the work. I like to get it to build the system to run some of the work. That could be Python scripts, that could be little bits of software, other bits of code.
The easiest way to describe this is I will never get clawed. to do maths directly. What I'll do is I'll get it to build the spreadsheet that does the maths.
So we get it to build the spreadsheet with the formulas in there to actually run the equations and put the output. Because you might have noticed that LLMs aren't the greatest at maths. So all it has to do is move data into a spreadsheet, the spreadsheet takes care of it.
The same can be said of converting files, like doing arithmetic, checking formats, renaming things in bulk, get it to actually ask it to Write the code or the scripts to actually do some of this stuff. If you're finding that the skill is taking up way too many tokens, we can use, remember, we can have these scripts as our reference files as well.
Rule number four, build from work you've done well. And this is what we've done through this process. The first example was a skill that I'd got dialed and I knew worked really well.
So it was easy for me to take that process and bake that into a skill. The second one. Again, proof -based creation.
I actually ran the process with Claude. I got it to a decent output. I then taught it the final tweaks that I wanted it.
And then I captured that process. So if you try and build a skill that you've never actually done properly for yourself, and you've never actually shown Claude how to do with the right instructions, and you try and just say, hey, make me a skill that writes LinkedIn posts, it's not going to be very good because it's got no direction.
It's had no expertise. It's just going to build something that looks good. you don't actually know performs very well.
And then you'll get into the problem of trying to like edit and upgrade them. And instead you might just want to start from scratch and be like, let me do good work and get a great output and then capture the process. To help do this as well, rule number five, three to five examples.
You could make three examples. So for example, to upgrade my blog writing skill, I might actually put in the reference files and I should do this. We haven't done in this process, but a great way to upgrade it would be to put three examples of what a perfect great blog post looks like.
Not for it to like pull the content from, but so it can look at what the A star standard is and compare its work to that. That's how you get away from these like flat, they look... good versions but missing something to a version that you'd actually ship it can actually use the other examples baked in there to model the example we could also use it when we were actually building the skill and showing it the the what we were trying to build we could have actually said hey here's three examples of high ranking blog posts we probably should have done that when we were building the blog writer skill in the chat there here's three examples of great We could have done the same for the recorder skill.
We should have actually said, hey, here's three examples of really great high quality reports that I want you to make sure you're hitting these marks. That would have just given it more direction and clear goal of what you're trying to hit with your final output. So that's a rule five that I probably should have followed a bit more in this video.
And then stop them fighting each other. Just be checking that your descriptions and your trigger words aren't fighting each other and you're trying to run multiple skills. to do the same job by mistake.
That's a little problem that some people run into. And one final little tip here as well is you can really test the output. If you want to see how good or not your skill is, run the skill or the job.
Tell Claude to write a blog post with the blog writing skill and then get it to write one from a transcript without it and compare the two to see. Is your skill actually better and actually doing a good job versus just cold AI? And then finally, before we move on to the next build, it's just three little tips here that all of your descriptions, you'll see this a lot when Claude is building.
They have to be under 1024 characters in that little description area of a skill. You might get it say, oh, I can't upload this skill or can't save the skill because my description is above 1024 characters. If that's the case, ask.
give Claude that error message and say, hey, you made a mistake because it does make that mistake. Just know there is a reserved word. You can't use the word Claude in the name of your skill.
That is blocked off by the system. So you can't name a skill something with Claude in it. And then if there is a colon or quote inside the description, it might break the file.
These are just some little things that you might run into errors along the way while you're building. But next. Let's jump into the next level of building a Claude skill.
Now we're actually going to rebuild a level three skill again where we're embedding connectors because I just want to show you again how you can go and use connectors, set up certain connectors and actually quickly bake them into a skill because we kind of did it on the fly with recorder skill. We let Claude work it out for itself.
I'm just going to show you once again how to do a level three skill with a connector because that's going to give Claude... hands it's going to allow claude to reach and pull in data real numbers from a real source without you you know you know exporting and downloading anything whether that's in this example keyword data there's no copy and pasting nothing goes stale it's always live and able to pull from them we're also going to be able to push the finished work so this is going to be a two -way skill that's also going to be able to push things into like we saw google drive gmail um in nice structured output where you know some of your team members might actually look in project management software for example okay and this obviously gets really powerful because now we're not just working in claude we're actually able to pull stuff and push stuff out and complete full jobs in software tools essentially so the first thing we need to do is we need to make sure our connectors are added there are multiple like hundreds or thousands of connectors now if you go into your customize area on the left hand side here you can click connectors you can see some of the ones i've already got set up here if we click yours you can see a huge list going on here now some might already be built in one of the great ones for this sort of
SEO or marketing work or sales work is Appify. This is great because it can actually scrape the web for you. So if you want to add connectors, you could actually go and click discover.
We could type in the one we're looking for. In this case, it would be Appify, which allows it to pull live web data. We could click this and we could click the connect button in the top right.
In Appify, you could create an account. and it has access to 60 ,000 different scrapers across the web, including SEO data, etc. We can click settings in the bottom left here, and then API integrations is going to give you an API key.
So when we copy that API key, we can go back into Claude, and in our configure area, when we're setting this up and connecting it, you put your API token in here, you copy paste that in, click save, and Apify will be set up. So that's how you're going to... basically set up connectors some of them are much easier you might even just be able to go into customize uh find one you like the look of so let's see if there's any other seo options in here while we're here sorry we need to select connectors um and let's say there are some other seo ones in here there's semrush semrush is an seo tool we could connect that to claude you can see continue connecting i've got a semrush account that i'm logged into and then we're connected to semrush as well So you can pick and choose which ones you want.
You can use the Appify one for this demo as well if you want, because it gives you $5 free credit every month to actually go and test some of this stuff out. So with the connector setup, we've got in our main document here, we've got another SEO prompt that we can actually copy and take that back into Claude and paste in here.
You can see it's a little bit funny in the way it's actually pasted in there, but I just want to break out a couple of things in here. We've got things like Notion. URL.
So it's going to know to actually connect to our Notion connector, which is another one here, but you could use any other project management tool. You could use Google Drive for Google Docs, et cetera. You can see I've got it as tools that you can use the Appify for information and data to start with.
It can also use, I've got some other connectors baked in here as well, data for SEO if it needs to, and also something called Firecrawl, which helps read web pages directly. But essentially I put that prompt in here. And we're going to do the same.
We're going to go for skill creator and just say, can you turn this prompt into a SEO strategy skill for me? So this is an SEO strategy skill. It's going to be able to use connectors as our level three skill.
What we're going to do eventually as well is we're going to link these all up so that our... Audit is able to then fire into our strategy skill, then into our blog skill, and then into our report skill, etc. And we're going to layer a voice copywriting skill over the top as well.
You can see the layers that we're building up in this department and why I wanted to walk you through this process as well. But you could see, basically, my point here was that it's really that easy to actually build connectors into skills. You just tell it what connector you want it to use.
We could actually go further and say, if we were building a very specific one, This is going to be a bit business agnostic and I can use it on any platform. But if we had something specific and I wanted it to point at a very specific Google Doc or spreadsheet or Notion database or Notion page, you can actually give Claude a direct link to a particular resource for it to be able to work with on a connector as well.
So it's just going to clarify a few questions there with the little also ask questions and then go and build the skill for us.
Right then, we've built our skill then here. We've got some feedback on the left and it actually says, this is what I love as well about turning a skill or a prompt into a skill is Claude will analyze it and it's probably got a memory of how we've been working so far today as well. And it's gone in the six places I went beyond your prompt, which are the ones worth arguing with.
So it's given us some more depth to our prompt. That's where prompts fall down. They can really only be so long because they just become unwieldy and unusable otherwise, whereas a skill can bake more into its process.
So it's gone and actually given us some upgrades on the left hand side here and marked out any possible failures. So again, we have this skill built. We should be pretty confident in it because we built it off a really in -depth prompt that I'd been testing and run.
So it's got all the steps and the output ready to go. So we can click save that, but you'll get this problem. Now I really wanted to trigger this problem and I'm happy it did because quite often when you're building, you'll get this Field description in skill .md must be at most 1 ,024 characters, as I said before.
So actually what I want to do is I'm going to take this error message in here and I'm just going to paste it in the chat because Claude has gone way too in -depth here. And then it's going to go and edit the skill file for us there nicely. So we'll click save skill and then we should be able to, what would be strategy.
seo six month seo strategy skill here we go we've got that build we should be able to check it out the description works sorry and for some reason didn't actually package the uh files properly in here the reference files so i've just gone and asked it to make sure you include the reference files and updated the seo skill there and you can see on the right hand side here now uh we've got all the assets the strategy of what a strategy should come out looking like in terms of the template we've got some forecasting scripts built in here some tool routing it's built all this logic in there for us which is super cool so now we have our strategy skill built out we've got our original audit Remember the first one we built, we've just built a strategy, which is the second in the process.
We've then got our blog writer, which is going to create the content and the pages for us. And then we've got our reporting skills. So we've got four skills here.
Now here's where we get a little more complex because we're going to level up to the fourth level here, which you can see the four skills. audit strategy, blog writer, reporter. We're going to make them all work together because at the moment they stand alone and we're like, okay, do a bit of auditing, do a bit of strategy, do a bit of blog writing, but we can stitch these together to work as a team.
So each one knows what the other does and what information it needs to pass along the way. So our audit skill is going to find what's broken and worth chasing. It's going to pass that information to our strategy skill, which is going to actually turn them into like a plan of how to address them.
which is going to then give individual options to our blog writer to create with us, which will need a bit more input from us. And then the blog writer can inform the reporting that watches how they're performing. So we're essentially building a nice production line.
It is a little bit dumb because it still requires just one, two, three, four, which by level five, we're then going to add the intelligence sort of manager over the top of these as well as adding some brand voice in there as well. But let's turn these into a chain. And we're going to do this really simply.
We're going to start off doing it one to one, and then we're going to build up the chain of these skills to hand off information. So I'm just going to start really simply. And again, I'll record all these prompts for you to use in the documentation and the guide to follow along with.
I have my, and I'm actually going to make sure my search visibility audit skill and my six month SEO strategy skill. Just going to actually make sure to name them directly to make sure that we're building correctly here. I want these skills to link together to work as a team.
So when I kick off a search visibility audit, I would give it a website and then I want the audit to go and do its job and then push its findings. It should link and push its findings to inform the SEO six -month strategy skill, which should run off the back of the search visibility audit when it requests it. And that's really...
It's quite simple as that. We need to start thinking in my mind which pushes to which. Now our search visibility audit could also push straight to our blog writer.
Or our report skill could also link back to our six -month SEO strategy if we're making updates. You could say every month I want the report skill to feed back to my six -month strategy to update our strategy. So they're not necessarily going in that nice defined order.
We are going to loop them back around to all into Mingle as well. So now this is a really interesting point it brings up, which is why we don't need to prompt too aggressively because it'll ask the questions that it needs information on. When the audit finishes, should the six -month strategy skill get triggered?
Now, in some cases, you might auto -chain and be like, yeah, this next process always happens. So don't even ask me, just actually keep going. But honestly, I might not always want a strategy written.
I might just be running an audit and then want to just be like, oh, hold on a minute. So I'm going to get it to do offer, then wait. So it's always just going to offer rather than auto -run, but you could get it to auto -run as well.
And I was going to ask a couple of questions just to fix anything that it missed or where it might fall down. before then actually going and updating both of these skills to intermingle. The search visibility audit is going to know where it's pushing to next.
And the six month SEO strategy knows that that could be an intake process for it as well. And now the only problem we'll face when we're actually linking all these sorts of skill is obviously they need historic data to work on. Particularly if I was to do, let's say we go further and we create the report skill and it's reporting on performance and then feeding back information to like our strategy skill to run updates it needs to have the underlying historical information of what's gone on so either you need to run this in a clored project with the project information always updated or you run it in co -work on a specific folder for that client website or your website where you're going to hold all of the outputs so if we're running in co -work on a folder you can see we can add a folder in here i'm just working in one that's just for this seo skill build Every time I run a visibility audit or a six -month strategy, a blog post, a report, the outputs are either going to be put in there or we're going to store them in somewhere like Notion.
So we have a database of all this ongoing work for it to refer back to. So we can keep a strategy updated. We can use these skills in and out independently as well as keeping them informed through this workflow.
And when we add our manager orchestrator skill on top. Okay, so we've got both files have been built and verified. And hey.
This is what I want to see, proposing them as a pair. So they know that they're a team, that they work together now. So starting to create this SEO whole department, our whole team of little AI employees that are going to operate this for us.
Okay, so we've got our finished updates here. It's going to let us just review them quickly. I just will check through to make sure that they're actually...
working here so we'll check search visibility audit obviously we need to test these as well we would go and test that these actually work i'm not going to do this live now because that's we've already seen them working and then we can see down at the bottom here it's helping you can see some of them handoff save you want me to run a six -month strategy off these findings so it's actually giving us a handoff format as well not just our audit it's actually giving us a handoff that we can use on our next skill so i'm going to update that skill and i'm going to review this one and the intake look for an audit handoff before anything else and it's going to know exactly what it should look for and how it should go awesome great now we've built those two together we've clipped them together like lego bricks we might also just actually go and put some instruction into the other skills as well here and just say my blog i also want to update my blog writing skill which should be able to feed off of my
SEO strategy so the SEO strategy will have action points in there and it should be able to action or the blog skill should be able to action the first blog article off of the strategy skill to get the process running we also have my SEO report skill which will run and it should be able to then invoke the SEO strategy to skill to review our current strategy and make any tweaks along the way based on the report, as well as potentially the blog skill to make any tweaks to a blog post we have, although that is probably rare.
It might also invoke the SEO audit skill. If it finds a particular problem that we need to investigate further, we might need to loop back to the SEO audit skill to be able to do a very. particular piece of auditing based on a problem that the report has found.
So we're just going to give it a little bit more instruction about how the blog writer skill and the SEO reporting skill might actually invoke based on some stuff it's found. So if it finds something really problematic in a piece of websites like chuntering downhill and it's not obvious why, it might say, hey, I'm going to offer to actually run the SEO.
audit skill, the first one, and push this information back to it to work in a team there. So it's actually designing a loop. You can see it runs in a loop, essentially.
We might get to the end of the six -month SEO strategy, file a report, and then run the audit skill again, just on a schedule, which would be a really nice way of working. So it's actually asking me some questions in here about how does this work. I can't run automatically.
It's flagged the blog writer needs more input. It's a level two skill, which needs a lot of input from me. So I'm going to say, hey, you need to stop and read the brief that you've got from the strategy and then tell me what you need from me.
The report can invoke three things, a strategy, a target audit or a blog fix. What should it be allowed to do on its own? I actually like, I don't want it to invoke automatically.
I just want it to recommend what it should do next based on the options. And should the monthly report grade performance against the six month strategy? Yeah, I think it should grade against the plan.
Absolutely. It should be able to reflect back on the plan and report how we're tracking against the laid out strategy. So again, we're making these smarter.
They're a bit dumb and they ran independently before. Now they're getting smart and learning how they should work together. Claude's going to be going through and proposing the next skill.
We can go through and obviously check that we're happy with it. So we should have our visibility audit update with the different modes. It's actually added a mode in here, which is interested the targeted investigation.
based off a particular problem that we're bringing to it from the report or the user, in fact. So we can go through, check all of these, obviously make sure you're happy with them, and then obviously run a test to make sure that they actually all run nicely. But it should present them to you one by one here just to start ticking off the list and make sure everything is running and linking together as you want them to.
But remember, because we built these skills out well in the first time with our expertise and we know we got the first run of the skill dialed, now that we're linking them together, they should work pretty well. Problem I often see people run into is that they try and build them all at once and they're like, build me a full suite of SEO skills or build me a full suite of...
operations skills or something or finance skills, and they don't take the time to build each one individually and get that perfectly dialed before starting to get them to work together. So they end up in just a complete mess. And again, if you're trying to capture too much stuff in one skill as well, if you're finding like, ah, they're starting to lose the plot a little bit, you need to think about going back and then breaking them down into smaller parts.
So actually, I might find that when I'm running this search visibility audit, We have full audit mode and we have targeted investigation. If I find that actually it's not quite working how I want it to, I might actually say, well, actually two modes, I might go and say, this isn't quite working right.
Let me go split these skills up into, I have a full audit skill and I have a targeted investigation skill. I'm not saying that two moded skills don't work. I'm just saying if it stops working, that is your best option to go and shrink them down into individual tasks.
So it's thrown up the last two for review, which were the new ones. There's SEO blog writer and the client report. The ones at the end of our flow.
It's nice. I like this. Put the do not use LinkedIn and do not use for newsletters to make sure governing principle.
But this one, I don't think it's changed. It hasn't changed a huge amount. It can push it into the report skill, but the report skill should be the one with the bigger one where it sits in the loop here.
So that's nice that it's got the loop information. We can update that skill as well for the sake of it now. And then we have our full set.
updated and it's even written down the full loop architecture which is really handy we've got the different skills how they actually work etc this is more documentation at this point but it actually is going to come really in handy when we move on to the level five skills which is our manager our orchestrator skills so so far we've gone from level one just wrapping a prompt up small inputs level two giving more expertise into the skill and the output level three connected level four multiple skills sort of linking together in a chain and now we're going to put a manager on top of them i just want to say where we are in the process of this video because We're going to do this.
We're going to build our manager skill. Then we're going to wrap everything up into what's called a plugin. So it's all neatly contained.
And that's going to be a nice breaking point. After that, we're going to go and do things and talk about how to create brand voice skills and anti -AI writing, slop skills, et cetera, to run on top of almost everything we do so that every output is coming out in the right voice. You can imagine in a process like this, be amazing to have a brand voice skill for my website running on top of all of the outputs being created.
Now, let's jump into our level five manager, or I call them orchestrator skills, because what we have at the moment, we have a production line. We have to remember where we are in the production line. It sort of runs from one end to the other.
It's a little bit hard to jump in or remember all the different things that these skills can do, or particularly if you're a new user to them, it's like, where do I even start? So we need to actually give them a line manager for them to report to and from me as well. so that we can have a little bit more flexibility and management of how they're working.
So our manager skill is going to do exactly this. It's going to know what every skill is, what it can do, where it sits in the process, and it's also going to be able to problem solve and pain solve. So I can go to my manager skill like, hey, my website traffic has dipped.
And it can then start suggesting and invoking skills to help get us out of that process. So a manager skill can help with our decision making. It can help us jump in and out of different processes as well.
And here we have the. prompt here for you it's actually four skills we bought at the moment because we haven't actually built our voice skill quite yet we don't really need to add that in here quite now we can easily add that on top of our orchestrator skill but i'm going to copy this prompt and you can see it knows i've got to slightly change the names of actually what we called them here as we built and it should know what each does.
It should take a goal in plain language, tell me its plan, run the skills report back and ask me anything. So we're going to copy this prompt and we're going to go back. We might as well run it inside the chat that we've actually just built this loop into.
And I'm just going to tweak this prompt a little bit. So we have, because we've been working with them in the chat here, I'm also just going to make sure we're naming the skill based on what it's actually ended up being called. If you don't like the names of the skills, of course, you can go and just get Claude to edit and change the name of the skills.
SEO client report. Pop that in there. Build me an orchestrator skill that manages them.
And we're going to run this process. So you can see our level five skill is the manager sitting on top of all of this process for us, which is really nice. And then we can start to see how some of this works once we've built out this orchestrator skill.
This fairly simple across a four skill process. I actually have a bigger set, which is about 15 SEO skills. And in that case, it becomes way more powerful to have an orchestrator and a manager skill when you're like, I've just got so many different little employees running around doing stuff in my cloud.
I need something to actually manage them. Or you might have them working across different departments. I think I've actually got in my account while that builds.
Let me show you another example of them. We go into my customize here. If I search for orchestrator, you can see actually I have my marketing orchestrator, the marketing strategy that routes you to the right skills.
When someone doesn't know where to start or has a vague marketing request or needs a multi -step workflow, ask clarifying questions, diagnose the situation and recommend a skill sequence. Triggers on help me with my marketing, where do I start, etc. So you can start to see how you can build these out.
Then in the contents of it, it knows when to use this skill. It's thinking of it as a fractional CMO in a box. So again, we're building an SEO department today.
And I could actually link my SEO department to this marketing orchestrator, which has some stuff already built into it. This is a bit of a different setup. Brand voice, which I'm going to show you how to build.
Keyword research, positioning angles, direct response copy, a newsletter writer, a content atomizer skill. So there's tons of stuff in here and it understands how all the skill dependencies work one upon another. basically it's even mapped everything out here for us it's a really good example of an op of an orchestrator skill and here we go we got the proposed skill come out i love it it's called seo department told you we're building a whole seo department here take plain language seo go for a site and work out how to improve the seo or which skills to invoke we could actually see some of the content in here the school this rule This skill lives or dies by.
If you run the same skills in the same order every time you failed, you are then a chain with extra steps. A chain does not need a manager. So it's got all the specificities about when and how to run each skill, how it should work as well.
how they all route to each other and making sure, you know, suppress gates that you've already answered. Don't keep pushing back on the same things. It's got its reporting process and some particular ways that someone might invoke this skill.
What are some anti -AI patterns in there? So we can save our orchestrator now and the SEO department is up. It's up and running.
So cool. so we've built our whole seo department now we can test it before showing you how to wrap and file this in a plugin basically but essentially i could say hey seo department you can see here it's ready to go or i could use it natural language i could say hey uh can you help me improve the seo traffic for And we're going to put in Courchevel .vip, which is the site we've been sort of working on all along.
HTTPS, let's get that right. We'll use the same folder that we've been building in all along, and we'll see how this operates now. Now, instead of me thinking, do I need to audit?
Do I need keyword research? Do I need to write blogs, et cetera? We've got our SEO department skill to actually start figuring out what the next steps are.
And if you're running it on top of files that already exist, of course, it can start looking at like, oh, I've got a strategy. I've got a report here, like what are we meant to be doing next, etc. You can see it's starting to read my cloud memory, searching through the project, reading project info to get a landscape of where we are actually in this project, which starts to make sense now.
Before we were like... oh, did we have an SEO strategy? Where in the SEO strategy are we?
Now it can remember, it's using memory to remember where we are in a project, in a strategy, what's been done, what we might need to do. It knows that it's a six month SEO strategy. So it would know when we last ran the strategy skill to be like, well, that was five months ago.
Maybe we should update the strategy or the report, et cetera, et cetera. Now it's actually going to. work with me and be like, well, what are we actually doing here?
You can see the SEO department skill running on the right. It's going to start, what is the binding constraint? How much access do you have?
Can you connect and fix it? What are we actually working on here? And then it's going to give us a plan.
So it's really interesting as well. It knows that Courchevel's revenue happens December to April. It's currently September.
So it's actually being proactive in the feedback and we're in a really critical window. So anything that needs to be indexed and ranking by December has six to eight weeks to ship. That's a genuine dependency.
We need to be urgent. So we need to be clever about what we're doing. And this is the strategy we're going to run.
So it is going to run the full audit and then hit a decision point and telling me why it's not running some of the other SEO skills we built. and where we're starting from. So I'm actually just going to say, hey, can you just run the audit and strategy in one shot for me?
See if we can get the output. That's going to take quite a while. So I might actually let the orchestrator go and actually run its process and run the audit and the strategy straight off the bat for me, because we can go and do some other stuff to help improve this as well.
It might fire some questions our way as we go. You can see here on the right hand side, I've only ever invoked SEO department. It's gone and invoked search visibility audit to start our audit.
Super cool. We've got our level five SEO orchestrator, our SEO manager of our whole department running for us now. While our SEO department gets to work for us, I just want to talk about plugins because plugins are the last extra secret area of Claude's skills.
We've gone through the five different levels up to that full team of orchestrated managers and workings. Now we're talking about plugins, which in my mind, the easiest way to describe it is a filing system. Because at the moment in our Claude account, if we go into our customize area and we go into skills and we click yours, it's just a long list of skills.
Yeah, we've got the SEO skills that we've just created today, but there's honestly, this is my account as well, there's a mess of just so many different skills in here that we really need to start sorting out. We also have connectors, which again are in an independent list. But the third tab along here is...
plugins now a plugin is essentially a filing system for all of your skills and your connectors and ways of working so for example i've got this one here it's my relentless content plugin that i built it's got a short description and again it's a chain of skills that atomize ideate write publish and convert it's got the plugin has got a sort of contents area which is filled with information about all the different skills and connectors etc in here so you can see all the different skills that are actually packaged into this file and then the main overall information about what this does and how it might actually run It's got a readme file about like what this actually does.
So it's got the outline of the pipeline, the full map of all the skills. So you might be thinking, well, Elliot, we just built an orchestrator skill, but it's still a bit chaotic in where they actually sit in Claude. This just brings it all together nicely under one hood.
We've also got skills in here as well that we can actually see what's in here. And we would have connectors if we had connectors built to actually run on some of these skills, which I'm going to show you how to set. a plugin up.
So when you come into a plugin area, you'll just have... seo department and then when we go back into our main area of claude you should see here as well to access them we can click plus we can go to plugins and we can see our different plugins and we can say oh let's go to our relentless content plugin and just invoke that skill as well it's all nicely filed away essentially rather than just being loosey -goosey scattered around your claude account and they also make them really easy to share if i wanted to share all of these skills nicely wrapped up i could just put them in a plugin and send the whole plugin to someone and just send them their whole SEO department in a box rather than lots of individuals.
And that might mean they miss or drop one or one gets deleted and it just disappears and then doesn't work properly. So I think of them as a nice, your plugins are a nice filing system that keeps everything nicely together. It doesn't change how any of the skills work or your ability to actually fire them.
You can still run them and they make them easy basically to hand over to someone else. So how do we actually go and build this? It's actually super easy.
All we've got to do is just ask and say, can we turn my four SEO skills plus my SEO department skill into a plugin with all of the skills included with their reference files, as well as the connectors required to run the SEO department, call it the SEO department plugin. And then I might just actually list out the skills just to make sure we are actually nicely packaged up.
What do we have? Search visibility was the other one we wanted in there that we can actually run. I mean, it would go and find the right ones anyway, because we've just built them today.
But I just like to do a double sure job that we're actually selecting the right ones here. And we're just simply asking in natural language. You'll see a lot today.
It's just about communication, what you like, what you don't like. Can you just turn this into a plugin for me? And Claude will get to work.
So over here on our testing, our orchestrator and our SEO strategy and chaining and everything, you can see our What has it done? It has completed so much on the left -hand side here, our audit handoff.
So it's actually created the handoff file for handing off with all the different pages it's checked, the trust signals, everything that the audit has picked up has now been fed into the SEO strategy skill, which is getting to work to actually create an action plan for us. Now over. back sorry to jump around back and forth but we're actually building the plugin here what you'll see is really interesting is actually making sure the connectors so all the connectors that it specified during the build that we made has picked them out which connections should the plugins declare is going to declare all of them should the plugin be written specifically or or generic enough to hand to someone else.
I'm just going to give it as a shareable template here. So essentially, if I was to give this plugin to someone else and they would upload it, it would actually know that all of these skills need these connectors. And either if it's got them, it would be able to fire them or tell the user to make sure they are connected in their account and set up.
So a new install of this plugin would go and tell them to go and connect these connectors to make this work. Again, that's another one of the benefits here. If I just give you a skill.
it doesn't really know what connectors are needed straight off the bat it might say hey do you have this and you might not actually install them whereas we'll bring up front of the start about what the processes are we run and what connectors we need to actually make them run as well It's all going to be built into the instructions and the overarching architecture and scaffolding of the plugin here.
Okay, so it actually took just a couple minutes to finish writing this. It's again got us three things it's changed, not copied, some name spacings in there, genericized for sharing. So since you picked the template, Elliot references became the operator.
It just pulled out some of the real specificity in my build and just used like example .com and things. And it's named a couple of the connectors that need to be used in there. One thing to decide once installed, all five skills exist twice on your account.
And as a plugin skill, the bare SEO department becomes ambiguous, worth removing. Okay, makes sense. I need to remove just the naked skills in the account.
It's got a bit of a build there. And then it's got the, you can see now. You can see the depth that we've got in.
We've got the main plugin area. We've got each of the skills with their references, with their different assets in here, the MCP, the connector details, and a readme of how this all works. Like this is a full SEO department in a box now.
All I have to do is click save plugin and it should then hook that up. I can go to manage and we've got my SEO department plugin. We've got.
the contents just broken down we've got the skills that are included in here with all of their files and information and the contents and connectors they need to run and we also have the connectors as well so if i gave someone this plugin they would come in here and they'd be like oh i need to connect all of these connectors to make this actually work just straight away outlined as a nice filing system so there we go our seo department plugin is built and ready to rock and roll with our five skill in -depth setup that we built today you'll see as well on my we were running our uh practicing our orchestrator to run our seo visibility audit and our our SEO ports and our strategy and stuff, which you can see it's actually working and pulling all of this information for me.
Super nice. One thing that it's actually realized is I need to top up my, she uses data for SEO. I need to top up my data for SEO to get some more data in there to make the strategy fully data informed, which is.
super, super simple to do. I'm not going to do that right now because we're talking about just the build, but you can see exactly how we went, built all the skills up, link them all together, put an operator on top of it or an orchestration on top of it, and then just told it to build it into a nice plugin for me to keep things neat and tidy and nicely kept together.
So I just want to take us in a little bit of a different direction. Now we're stepping a little bit away from the SEO skill build that we've been doing because that's complete now. We can say, okay, done that.
I want to teach you how to build a voice skill. And your voice skill is something that allows Claude to learn how you write and interact and talk and apply that to everything at Outpost. You think about, go back to the SEO blog writer skill, or even just the report skill.
If it knows how I like to write and talk, it can apply that voice to all of my work, as well as getting rid of some of those annoying AI patterns and AI slot, basically. And to be honest, my voice skill, although I don't use it directly to write all of my newsletters and LinkedIn posts, For all the reports, general outputs, tidying up a transcript, putting some final touches through it, it will actually run it through my voice skill to tidy things up and improve and write in my voice.
And it's actually much easier than you think to build. We can take a prompt here that's actually going to analyze. This is my analysis, voice analysis prompt to help extract how you write and construct.
So you can run this in several different ways. We'll go and start a new task here. You can run this.
prompt. I'll just paste it in here. You can run this prompt by copy and pasting writing.
So I'm actually going to build this for the, let's say the Courchevel .vip website that we've sort of been building with today. I'm doing our analysis on and stuff because this has got tons of articles that I've written myself in the brand voice for this website. So what you can do is you could go and say, find some of your best performing articles and you could literally just go and copy paste all the writing on there take that and paste it into your prompt in here's my writing the other option you could do you could have a transcript as well transcripts work really well for this because that's you talking super naturally or we could go and say instead of my writing you could give it specific web pages or i want you to work out how how i actually write we'll build that writes so we can build a skill that writes in my voice I'm actually going to tweak this because I actually want to do it not for my voice.
I already have that set up. I want to do it for Courchevel .VIP's brand voice. So I'm just going to tweak the intro and just, you know, you can tweak prompts if they're not quite for what you're doing.
I want you to help build a voice profile for my brand Courchevel dot VIP. You can find the website at Courchevel dot VIP.
And I want you to go and pull the top articles from there for our analysis here. I just tidy that up because it's HTTPS. I want to help build a brand voice profile.
And then it's going to go through. You can see. So given it where it's actually going to.
pull that information from. Before you analyze, make sure that they're not, you know, weird, badly written, etc. How to extract it, vocabulary, structure, what I do that most people don't, and then give me anything evidenced and inferred.
So we can run that. You can either paste the files in there, set co -work to run on top of a folder of structures, or just point it at a website to go and crawl and pull all of the best content from a website, for example. And this is stage one.
This is analyzing, okay? we're not building anything yet we're just trying to analyze our voice profile from as much content as possible the more the better you could if you're building a personal voice profile you could be pulling in LinkedIn posts, email newsletters, general emails you've replied to customers, to your LinkedIn, your other social media posts, your YouTube transcripts, if you're me, for example.
Whatever you've got that is written or naturally voiced by you is going to be best here. If you've got stuff that's already got AI writing in it, then that's not going to be ideal because then we're not really detecting any new patterns. So it's going to be unhelpful.
It needs to be human written stuff. You might even give it some of your WhatsApp messages or your email replies. Okay, check it out now.
It's built me my brand voice profile. It's actually done five pages, which is plenty. It excluded something because it didn't appear to be my writing, apparently, which is great.
I think I might have actually used AI for that one. So that's fair enough. But it's cool that it managed to distinguish.
my writing versus other people's writing on the site, and then pulled out the sentence mechanics that is evidenced in there, the vocabulary that we use, the structure of the sentences, all of this sort of stuff is actually pulled out for us to build this report as well. It just has five questions before it actually goes and builds anything next.
Correct, the top and tail are mine, so it was right about that.
Mine, but I was written to a partner brief, switches between I and we. deliberate for i i for experience we for the brand is a is a decision probably unconsciously made on the site but i know it exists should the profile cover the whole site or just only the editorial articles um let's only say editorial rather than any just bog standard business listings that we have on there that aren't particularly creatively written.
And once we've had all of that confirmed, again, the more information you give it, the better. We can actually use the next prompt, which is the build prompt. So I'm going to copy this.
This profile is right now with my corrections. You might go through it and give it some more corrections. Turn it into a Claude skill that takes any draft I give it and rewrites it.
So it sounds like me. The skill should do these things, should be named, let's call it VIP brand voice. Before starting, I'm also going to give you my AI slop and banned words list.
I'm just going to tweak this prompt again. Ask for this next before starting to bake them as references into the skill. I'm just going to copy this build prompt now and we'll just wrap that nice and tidy for everyone.
Go back to Claude and I'm going to paste my build prompt in here. to give it the outline of actually what we're going to do and when you're ready it's going to ask for the next uh bit so i got my anti -ai slop right like anti -ai writing essentially which is built up we analyzed and built this up over months and months and months of all the new things that ai comes out with um you know it does that rule of three where it does like boom boom boom between uh full stops you know it has m dashes it's like In a XYZ world, all these sort of AI tells, it's got all of that in there and sentence structures.
We've also got a banned word list as well. So what you're going to do is you're going to copy this and take that and paste it into Claude. And then I'm just going to go back as well.
I'm going to grab the add the banned word list, which is all those words that we don't want. written it's also got banned phrases in there as well not just x but y in today's bloody blah world it's worth noting that all of this these horrible things you see it right um and this you know furthermore no one writes furthermore so i'm going to take that and paste that in there as well because it's going to bake those in as our reference files for it to reference and check things off now what's interesting about it did ask me a couple questions when writing this but what's interesting obviously it's done all the stuff we've learned so far it's operated the skill creator it's wrote up the skill what's interesting now is the way we structured the prompts as well it's actually running test cases so it's actually seeing how well the skill works and does it adhere to the rules we gave it to make sure yes we've got all the rules written down but the final output
Does it actually stay to our strict rules or not? And then it's evaluating. So something that actually runs in your Claude account and the skill creator has, it's able to actually run evals and evaluations and tests your skills.
So when you're building as well, and I hadn't mentioned this earlier because it goes super deep, but when you're building your skills, you can ask Claude to actually test them for you and evaluate them. And it's actually going to check that it... does what it says on the tin like it follows the process that you've given it and give you a review of that test you can see it's actually running six agents right now automatically include co -work to after it's packaged the skill to actually then say, hey, I'm going to run one with the skill on some test content.
I'm going to run one without. I'm going to run a second one with the skill. I'm going to run a second one without.
And the same for this as well. So it's running three tests on a baseline of the skill, of using the skill versus not using the skill. and comparing the output and rating it against the criteria in the skill to give us our feedback.
So you can see the process that Claude is working through on the right hand side here, which is super interesting that a lot of people don't know it can actually do. And so this is going to help test and it's also going to help it feedback and make edits and update to the skill before we even get to testing it. So it's getting rid of some of the low hanging fruit that's not quite working properly.
So then when it comes back to us. we can run a test on it just for that more higher level. As I said at the start, these voice, this is a non -deterministic skill.
So it's a bit more art. It doesn't have a structured templated output every time. It's a bit more of an art than a science to feel back and forth.
And you'll probably constantly be updating your voice skill to be like, I don't really like the way you phrase this all the time. Like stop doing that or use this pattern or stop using this pattern as your brand evolves and upgrades over time. or your personal brand voice as well.
You can build them for either, you can build them for your company brand voice, or you can build them as a personal brand voice. I actually have a personal copywriter brand voice for some of the marketing work, to be honest. And also when we think about the context of how useful a brand voice skill can be, if you have a team of people that are working or a marketing department, it's easy as one person to stay in control of this stuff but across across a company and every output in the company you want to make sure is in line with your brand voice then we can make sure even everything's being human written and people on keyboards etc for emails and anything we can make sure we're applying our company brand voice to everything that goes out making sure we're also catching any AI slot that's being generated in the company that's really obvious we can also do it for personal brands so anyone who's building a personal brand with a team we can easily get our ghostwriters or copywriters or marketing experts or sales team to actually apply our personal brand voice over the
top of it so you don't necessarily have to do these huge edits to everything and rewrite them in your way or vibe because your ghostwriter has this extra tool this lever to pull in their company so here we go we've got our brand voice here which we can see the skill file. We've got the main set of instructions on the right -hand side here, of course.
Hopefully that's less than a thousand characters. It's got then the step -by -step process of how your brand voice should work. The one rule that outranks you, change how it's written, never change what it says.
So don't go and completely change the argument or rewrite everything. We're not fact -checking easier. We're improving the text, basically, in brand voice, not just rewriting things to be completely different or restating things.
Before you write, so before it does anything, it's going to check the voice profile. It's going to check the banned words, anti -AI slop, and reference examples. It's going to pick the mode first.
So it's got different modes it can run in. An editorial. So for internal guides and opinion pieces that it's going to run on, brand recommendation for when we're talking about other brands, and then a partner brief if we've got a partner that's advertising on the website, for example.
Then got its how to rewrite exactly like key things that I want it to rewrite and look for. It's got the hard rules, things it should never do that are top of mind. No em dashes, of course.
No formal connectives, no paragraphs longer than five lines. I might even chop that down to two lines, to be honest. And then references the banned words and AI slop list, frequency of words and certain phrases in there, like never use hidden gem more than once in an article or per thousand words, and also report back what you changed.
Then we've got the voice profile that we did. That was that first analysis that we did. British season air idioms, for example, grammar, British English, etc.
You can see how deep this is. Sound and smell before sight. So we really viscerally describe things, not just tell them what they look like, but actually what they sound, what they smell, using all the senses in our writing.
Points the reader at the staff, not the tourists. deflates the luxury he is selling on a site. Probably don't want these deflations in there on a site that's called .vip and it's got some of the vibe in there and everything like that.
So I'm not actually perfectly happy with this skill. It's got examples of like a flat AI written version by like exact examples of my writing in there. It's got those banned words and AI slots built in there.
So we can see it's not perfect. I'm not actually going to save the skill yet because reading through, I'm like, I don't want that bit in there. So I'm just going to say, hey, can we remove this section from our voice profile?
I don't mean to deflate the luxury, to be honest with you. So I'm going to get it to remove that section as well and just tidy things up before we even think about testing it. We've got our brand voice review.
So this is the eval that I was talking about. Remember I was talking about it will go through and test and it will run with the skill here, run this through my brand voice and then it's given the output of what comes out versus also a benchmark of how it's actually performing. The outputs we can scroll through and see the like difference between without a skill and with a skill.
So you can go through and see the difference for yourself. And then we've also got the benchmark about like. With the skill, it passes 97 % of the time based on the rules, how long it takes.
Without the skill, it is much quicker, like 28 .9 seconds. With the skill, it's a lot longer there, 126 .5 seconds. The token burn is much bigger with the skill, of course, because we've got extra work going on in there.
It's just got rid of my eval. So you can see, again, we've got... broken down by each evaluation here on the pass rate with the skill was good, 50 % without, the time it took, etc.
And then we've got what it's actually doing when we're running the skill. It passed all of these checks. When we ran without the skill, you can see no sentence longer than 25 words.
It failed that check. No em dashes rewritten in the copy. It failed that check.
So you can go through and have a look at where it's falling down. Sometimes no sentence longer than 25 words seem to be the main problem.
Otherwise, it looks like it's performing really well from a data point of view. And then we've removed that and put a new rule in luxury is the product and don't undercut it because that was something that I was unaware I was falling into that trap when trying to write more authentically. But we can save that skill now.
We've got our brand voice skill essentially ready to rock and roll. So we can actually test it out. Let's go and just jump into a new chat mode here because I've got here this blog post.
five reasons to ski in Courchevel. You can see now, where's Claude gone? We could say, we could post that in there and say, can you use my VIP brand voice to bring this article up to our brand voice, please?
Now we could also run, obviously, the SEO would you redo's that we built on here, but we're not going to do that now. I just want to show you literally the brand voice running on top of this. article, this example that I would use as a test, because what I would do now is I would go and use it a bit and I would note down some things I didn't like.
I would note down, hey, it does this. I don't like that. You keep doing this.
Go and make 10 or 20 notes and then come back to Claude and say, hey, these are all the things I spotted in my brand voice skill. Can we go and update it to make sure it's behaving like this and not like this? That could be specific words.
It could be patterns of writing. It could be all sorts of things that you're just like, oh, I don't like the way it does that. Because again, this is an art more than a science that you need to probably be working back and forth as you use it.
But again, you can see using the voice skill and getting to work on that piece of content. Okay, so it's gone into its editorial mode. Remember how different modes that it ran there?
It realized, hey, you have an article, we just need to... to be in editorial mode for this article. It's given me through what it changed.
Rewritten your opening pattern is read a question first, pivot well, credential drops, rewritten from the original to that. And we've got all the changes it's made in there. Hard rules I enforced, remove the four M dashes, the semicolons, exclamation marks were too many, flagged for some calls in there.
So it's actually given me back some things that I need to actually check on. But essentially our articles come back and it is rewritten in our brand voice. It's beautiful.
You see, it's not as... as longer paragraphs. We've got some of the way that I'm framing my questions and just a bit more flow in the way I'd write in there.
Is it? 100 % amazing, perfect as if I sat down and wrote this whole thing myself? Probably not.
I would probably go and give something like this another clean pass over to give it some extra stuff and some extra story from me because it was just a blank article I gave it. I think that's the one thing that's really going to be missing now is that original story from me, which would either come from a transcript or me sitting and doing some work to add some stuff in.
Maybe I'd even ask Claude to interview me about each bit to get some personal story and some flow back in there direct from me. but you know but be back in time for last lift home is the sort of thing we would be writing in there and that's essentially how your voice skill works you know so let's dig in look at what actually makes it worth your week love that brilliant we've come a long way we've come a long way and now we've built our voice skill We're really coming to the end of this course.
Now, there's a couple of areas that I want to take you through before we get right to the end here. One is what skills should you be building for yourself? It's a good question.
There's so many different skills you could be building and a lot of people aren't really sure where to start. Yes, we built that first SEO department, your brand voice skill. Next, where do you go?
Well, I always think start with the pain. What tasks do you actually hate doing? What do you not like doing in your work, life, business that makes you go, slows you down on a Monday morning or, you know, leaves you feeling drained, that's a great place to start.
So I've actually got this prompt here that you can use to help you work out which skills are actually worth building for your work, not just the impressive fancy ones like a LinkedIn writer or something. It's going to interview you here and it's going to go through the process of interviewing you, honestly, pulling some things out and then giving you a report of what you should actually build and how to go about building them.
So that's going to be tailored to you. If you take this prompt and run it in Claude, that'll take you through that process. I've also just whipped up 101 skill ideas, kind of based on a lot of the skills that you saw in my account.
And I also ran an analysis across the internet. I was like, look, what are the biggest pains people have in their business that could be solved with Claude Skills? Go and look in Reddit, forums, social media to see what are people moaning about that we could actually build Claude Skills to help them.
cash flow narrator, for example, helping people understand their cash flow for a month, a quote builder, an invoice generator. I have an invoice skill in my account where I just give it information on the job I did. It might even know the job I did and it just...
pulls out a branded, correct, perfectly templated invoice for me. Super simple, but super powerful. There's so many different options in here to spark your ideas for what you should be building, essentially.
So this document, again, you can get the link below, which is in my AI recipes here. Click the top one there. or it might not always be top, but complete flawed skills course guide.
It's going to give you everything that we've gone through in this video today, including everything we just built that you need. It's got the three ways of building skills. Remember just wrapping a prompt, building a new workflow, using recorder skill.
We've gone up the five levels, one, two, three, four, five different levels. We've talked about the two different types of skill, a deterministic and a non -deterministic skill. We've built an orchestrator, a manager on top of them, and we've built a brand voice skill as well.
So really now it's up to you is what are you going to build next? Go and use that prompt that I just gave you in the documentation. here and start building for yourself.
Everything's here, ready for you to go. This is the number one Claude skill that pretty much underpins everything I do. It links to all other skills and outputs I create.
And the weird thing is I don't really see anyone else talking about this, showing this, building this skill that gives you a unique advantage over everyone else using Claude. And I'm going to show it to you today and then walk you through step by step. how to build it.
Now, you can also get everything I talk about in this video. There's a link in the description where you get my AI recipe vault. You can go to build your brand print skill.
This is what we're talking today, a brand print skill that I've not seen anyone else use. And in here, we've got step -by -step recipes, including all of the prompts I'm going to use in this video. So you can get that in the link below.
But first, I want to show you how it works so we know what we're building towards. Without creating this brand print skill, you're going to get these generic outputs from Claude. We've all seen these before.
They're just boring and they look like you've just printed this straight out of AI, which no one wants to see anymore. Whereas when we actually build the brand print skill, what we get are beautifully branded outputs across everything you do in Claude. You can see this is a Word document.
It's got my logo. It's got all my brand colors on in there. You might have seen some of my...
teaching dashboards in previous YouTube videos. My brand skill builds all of that as well. It can run across bulk producing invoices in the right template.
It can even create my GEO audit mapping with all of the right colors in my brand, as well as even building actual websites and apps that all carry my logo, my brand colors, even my font and feel for everything. The brand print skill pretty much links to... every single output I make in Claude.
And so let me show you exactly how we're going to make this. Now, to start off, I want you to use the Claude desktop app because it's just going to give us way more power. And I want you to actually select the co -work setting in the middle here because this is going to allow Claude to actually run more autonomously and extract and build this skill, which is a three -step process.
The next thing we need to do is we need to collate our brand assets. That means logos, fonts, your brand guidelines, imagery, any other assets you have. I like to put them in one folder on my desktop to allow Claude to access them.
So you can see here, I'm going to new project or folder. I'm going to go and add a folder here. I don't want to create a whole project because this is a one -time job that we're actually going to do.
And then I'm going to go and select my brand assets folder on my desktop here and open that and allow Claude to access it. Next, I need to go and get my initial prompt. So step one, get all your assets in one place in one folder.
Step two, we need to run our brand audit. We can take this prompt here, which is in the AI recipe vault link I told you about in the description. You're a brand systems analyst.
I want you to audit my brand assets and produce a brand specification precise enough that another AI could apply my brand. It's actually going to go through all of the assets and extract everything we need in here to build our skill. So we're going to take that prompt and we're going to place it in here.
And actually it says my assets are in the folder attached. And I'm going to run that. Now, what's interesting while we let that work, if I show you my actual skill, which is this Elliot brand print skill, what you'll start to see is actually it's extracted all of this information that I've just given it.
And also, it's got reference files. So it's also including all of the assets, all of the font files, all of the actual logo files and a reference to my brand guidelines. So it's super powerful what we're doing here.
But the first step is running this audit. Now, what you'll see on the right -hand side here is the power that's going on here. It's listing the assets in there.
It's extracting the color palettes, the roles, the fonts, and actually using the brand guidelines to map all of that typography hierarchy and the font file coverage, cataloging all the different variants and the way they should be used so it's not just throwing random colors and fonts and logos together, which is the real key here, which is why we need to run this step.
If you wait a few minutes, you're going to get this output. You're going to get your brand audit, and you're going to get an inventory of everything that's found in there, what they do. You can see all the fonts, logos, type come out.
any flags that it needs that it's not sure on, the different colors that it's pulled from here. And you can see some of them are inferred. Like we need to maybe go and check these to make sure they're 100 % correct.
But you can see it's pulled out those greens and those inks and cream colors that I was using on my brand. We've got all the safe pairings because I got brand guidelines about what goes with what. It's actually listing out all of that information as well as the typography, the Thunderbolt LC font, host grotesque light font I use, as well as...
everything that's in there. It's got some missing things that we actually need to go and clarify. So at the bottom, we need to actually go and answer all of these questions to actually confirm some of this information.
Otherwise, it's just going to be a little bit off and it's going to be a bit frustrating. So go through and answer all of these questions. Now, once you've gone through and answered those questions and corrected the output, it's time to build the skill, which we've got another super important prompt here.
I'll just wrap it up there nicely so we can see it. We've got the next skill. The order is correct.
Now, build me a Claude skill called brand print that applies this brand to any output I ask for. You can see it's actually going to structure how the skill should be. So it's got the main overarching instructions of how this works, the main prompt here, the different assets that it's actually got, and any references.
If you have some references of like Word documents. PowerPoint presentations, et cetera. Really good if you put your PowerPoint presentations in there, can pull those structure out from your brand assets as well.
And then it's going to go and build the skill with all these rules, et cetera, in there. So I'm going to copy this prompt and I'm going to go back to my chat. You'll see you should have your full brand specification V2 here, which is super helpful anyway to have in your business.
But I'm going to take that prompt. paste it in and we're going to run that. This is going to take all of this analysis and audit and things it's pulled out, all these files and build it into that Claude skill I showed you a second ago.
Now it takes a few minutes to actually run this exercise and build the skill for you but once it's done you'll see you should get this little brand print skill built. You can see when we open it up on the right hand side it's got all of my fonts in there, it's got all of my logo icons, it's got references and it's got exactly how all of this should operate and how everything works so all we have to do is click save skill we can save the skill and start testing it and using it which is what we're going to do next so if i actually go back out i'm going to go into my second brain here this is pretty much where i do all of my work in claude it's got all of my context all the information about my business what i do everything underneath ready to rock and roll.
So this makes life super easy when I say something like, can you create a branded invoice for the King of England for joining my AI mentorship program? If I just run that, because obviously my second brain knows all about my business and blah, blah, blah, I don't have to give it all my address and everything or details about me.
It should go and find the address for the King of England, et cetera, if it's thinking cleverly. and build me my branded output. And I could do this for, as I said, web pages, Word documents, PDFs, spreadsheets, PowerPoints, anything I'm putting out.
And here we go. Here it comes out. My logo, my colors, invoice, it's got all the billing details on there, even has the nice invoice number that's coming out, which is some of the other settings I set up.
But mainly what I want you to see is I just said, hey, create me an invoice, create me a branded invoice, and it goes and auto applies my brand every time. Now, the other thing I want to say at this point is Claude Design. A lot of people will be like, well, why don't I just use Claude Design earlier?
I can give it all my brand. system in there and just have it work there well this is actually cloud design slightly detached like it doesn't link in i'm not working in there every day through my work and creating outputs i might move in here for very particular like slides For example, I gave a presentation at AI for manufacturing.
I gave a keynote speak. I wanted to create actual specific slides around that, not just fast outputs. So I'm using Claude Design very intentionally when I have a serious design task that I need to focus on.
But for everything else, I'm just using my brand print skill to get fast outputs when I'm working on all the boring stuff or even YouTube videos for my business. That's what I'm referring to. I built 43 different clawed skills for marketing and if they all disappeared tomorrow, there's five that I've rebuilt immediately that do the highest value work.
They run this YouTube channel, help me grow my email list and have even been reviving my dead LinkedIn. I've gone from posts getting 500 odd impressions and no sort of comments to getting 7 ,000 impressions and plenty of comments and interaction engagement on my posts. And so we're going to start with this first skill.
And I might as well use it on this actually dead LinkedIn post that... didn't perform very well before I actually started using this first skill, which I call my director of psychology. Now, if you've studied anything about marketing and content, you'll know that psychology is an important part.
You'll have heard about hooks, curiosity loops, and the zyganic effect. And honestly, I went deep on this for probably hundreds of hours and ended up with information overwhelm. And I never really translated any of this amazing information into actually implementing it in my content because I was just overwhelmed.
And so what I did was I took the 15 main psychological principles that I wanted to use in my marketing and started applying them to my work through the use of Claude. And the amazing thing was I actually saw it working.
As I showed you, I started going from these crappy numbers to actually these great numbers, even as just a test on LinkedIn. And now I apply it across everything I do. because I've baked it into this director of psychology skill.
So all of those principles are used and overlaid on my work. Now it doesn't write the content for me and produce the scripts for me, etc. I produce them and then I work with this skill to actually get our output dialed and introduce these psychological improvements to keep retention through my content.
Now what you'll get with this skill is actually some key changes. It's still working here as you can see. You'll get some critical feedback about where you're losing people, where you're waffling, where you're not really actually drilling home what you should be doing, and the five changes or the key changes you need to actually make.
I need to change my opening sentence, my hook. I need to make my count and my numbers work harder. Move some of the best lines.
It finds some of the best lines that are hidden and moves them up and just tells me what to delete because it's just fluff and not adding anything. While this runs its full teardown, you can actually get... all of these skills I'm talking about in this video today, including this first one in my AI recipe vault, free link in the description, find the five clawed marketing skills, open this up and you can scroll down and you can actually right click, download these skills to use for yourself.
Back over here, our final teardown is actually done. And I actually love this because it gives me some interesting information about my post or my script or whatever it is in terms of word length, word count, the readability level to make sure it's not just complete unintelligible corporate speak.
Then we've got actually the first tab down, what's going wrong? Where is the bad stuff that we need to delete or rewrite? What's not working in this post?
I love this one. The only bit that the person can actually act on, and it's the thinnest thing here, it's kind of tagged onto the end. You've made the whole argument delivered halfway.
And we're not really delivering anything interesting through this post. Now it actually goes for the rewrite and the re -edit. And not rewrite, re -edit.
It gives us the initial input. It's cut that initial line. It's telling us why it's doing something.
Plus, if you only do one thing, it gives you that one big change you can make. Now, I don't always use the visual output. Sometimes working just in the chat back and forth works really, really well.
But I use the teardown as well. if I'm really struggling to visualize how to reorganize a post that I've written. Now, skill number two has helped me engineer some of the most viral videos and posts I've had on the internet.
You can see here, this one, actually, it was responsible for 348 ,000 views and some decent revenue off this channel. It was also then a one -two punch because the trend ended in another follow -up video with another over 100K views. because it managed to pair my niche, AI, with something in popular culture to jump on a trend that no one else was spotting.
And this is a skill called trend jack and when you run the trend jack skill it's going to ask you you know what mode like what channel are we looking for do we want to go extra depth etc but what it's actually doing it's not just finding news like anyone can do deep research on news it's actually using something i like to call the play call and it's helping you find a topic and a shape and an angle here that is unique to anyone else so anyone can talk about a piece of news or a topic but we want to give it a particular angle and map that back to our content and this is exactly what the trend jack skill does it has a first run setup as well so if it's the first time you've ever run it it's going to help you edit and improve the skill for your Niche, for example.
Now, what levels this up as well? If you can pair it with a connector like Appify or something that helps it scrape even more of the web, it's going to give you even more detail. But even on its own with deep research and web search, it's going to do a really great job.
Let that run for as long as it takes. It might take a few minutes because it's going deep. It's not just surface level.
And it's going to give you your four opportunities ranked on the left hand side here, which is really nice. But I really value on the right hand side here, this full report that I get. full trend brief for the day we've got the pulse just a quick update on what's going on across my industry called claude co -work went to all paid plans on mobile and web which is a nice little upgrade for a lot of people this one as well that some people might miss claude can now send gmail they can send emails from gmail all little pieces of content that are perfect for me it also gives me a little pulse across all of the other channels that i might be uh might be looking at and gives me some outstanding like what are the outliers here you can see this video here actually is massive outlier in the industry which is an interesting angle rather than just you know your standard sort of tutorial walkthroughs it's actually using ai and actually testing what happens when you let them unleashed which i really love that angle
Plus then we get our TikTok breakdown, our Instagram breakdown. This thing goes on and on before we get to the real key stuff, the video opportunities rank. And as you can see here, number one, recast the marketing skills video is a constraint experiment.
So I could take this sort of video and repackage it, re -angle it and say, hey. In my next video, I let my five top -clawed marketing skills actually run unattended for a week. This is what happened.
Now, the first two skills we've talked about, they help increase quality. They help improve ideation. The third one is more about volume.
You see some of these big creators like Alex Hormozy, Gary Vee, they're pumping out. dozens of clips across their channels every single day and they preach that you need to be doing more, which is fine for those of you that have time or the funds to have a whole marketing team. But what if you're short on time and you don't have a big budget to hire other people?
Well, this is where my Clipper Army skill really takes on a new level. You can give it a long form video. In my case, sometimes I get my phone and when I'm on a podcast, I have it filming right here or I just do long pieces to camera.
I can give it that video and then It goes through and starts clipping out the best pieces of content. You can see here, for example.
It takes one year of focus. You pick one thing and do so much work on it that you can't not succeed. And it doesn't just clip randomly.
It actually goes through with some really clear rules. Never cut mid -word. Keep it chronological.
Don't reorder some of my sentences. Never touch the source file. I don't want it out.
editing the actual main file. I want it pulling out clips. Now I've given it loads of editing rules, but the real...
big thing the hot thing about this skill is it's step two is finding the hot moments it's looking through your video to find the strongest lines and the strongest moments that stand alone that open on something important that resolves a point that strikes tension has a contrarian take is a story or there's a lift in delivery and the tone that we're doing it pulls them out and then runs the tight edit that you just saw to deliver them for me straight into my folders So from here, all I have to do is publish the clip.
Maybe I'll add captions within the actual TikTok or Instagram app or whatever it is. But these are ready to go. 15 new clips.
You can see here, it's actually running the process for us now. And it's depositing the clips into my folder here. So it's up to 16 now.
13 at the beginning. So it does take a little while to actually run. But to be honest, I've been running this process at the moment and it's not like it's tapping out my usage at the moment.
It's not used burn through all my usage because this skill is really well defined. I'm not just telling Claude to go and edit the files. It actually has a strict process that it's following.
So that's how you're going to generate more volume in your marketing. Now, one thing that people tend to miss is they post on social media, they post their content, but then they don't actually capture that attention. Whereas this next skill is going to help you do what I've done and actually build an email list that's 29 ,000, approaching 30 ,000 subscribers, which is an absolute dream.
I can't believe I've done that. Even off a YouTube channel that itself still only has 43 ,000 subscribers. So my conversion rate to my email list is incredible.
That's really all down to my lead magnet skill. You can see in here though, it's going to help with lead magnet ideation and creation. Now, As you'll see in this video, I use something called the AI Recipe Vault to actually give people free things and they can also sign up to my email newsletter in the process.
That's how this whole process works. But I wouldn't have come up with this idea without working with a skill like the lead magnet. Now, the real key to making this work is to run it on some sort of context for your business.
If you just run it in a blank chat, it's not going to work very well. I'm actually running this on top of my deep. context and it's got information about what I do, my ideal customer profile, some of my hits in the past, some of my stories to actually build tailored ideas.
for my newsletter. And what we get out is not just a list of PDFs that we can write. No one wants a PDF that they can just read through anymore.
They want something more interactive, more useful, something they can actually do. It's either going to be some sort of calculator, a question diagnostic, or even something they can implement like the non -technical founders prompt vault here. I know prompt vaults go really well.
I have my mega prompt chest, which people absolutely love. Well, we've got the five -day build. The 10 -day automation sprint.
This is actually quite interesting here, I think. 10 days, 10 working Claude workflow automations. I can actually guide you through in an email series, a video series or something, essentially a sort of free build challenge where we build one automation a day.
Like some of the stuff that I have running here. I mean, I'm sure people would love to see my... guest radar build for example which searches for great podcasts and writes outreach pitches etc showing people how to build this sort of stuff would probably go down really really well let me know in the comments if you actually want something like that i can certainly build the this 10 day automation sprint where we walk through one automation build a day for your business.
And in fact, we actually had some risk notes at the bottom. It was like, it might be too good to give away. Maybe you should actually charge for this stuff.
But hey, that's a bridge we can cross later because I want to get onto my final skill for the day. Now we've improved the... quality with psychological triggers.
We've improved topic selection and trends. We've increased volume. We've generated leads to our email.
What's next? This final one is how are we going to take these email newsletter subscribers, potentially turn them into paying customers or build a sense of community around your brand because it's called email sequences. And this is something I'm missing.
If you signed up for my email newsletter, you'll know you get my free AI recipe vault, for example. And then you'll get a welcome email about me. And then it doesn't really do anything else.
I don't really nurture or onboard people or give them more information about me or what they can expect. This has got everything built into it to help us. So I'm going to say email sequences.
Can you help me build out the rest of my welcome email series for people who have signed up to my AI recipe vault? So we're going to run that and it's going to start to walk us through it. When you actually...
break down into this skill. You'll see it's got different sequence types it can run in here. It's got the welcome sequence, which is what we're going to do now.
Nurture, conversion, launch. If you're launching a new product or service, re -engagement. I've got a lot of cold subscribers on my email list.
Maybe I need to actually start thinking about how I can do a re -engagement to see if these people actually want to still receive emails from me or not. And post -purchase. So this is a really deep skill.
You'll see here as well. What's the lead magnet? Well, we should have just built that in the last step.
So that should be an easy. For me, I actually run this on top of my folder structure, which is my second brain. It has a connector into Kit as well, my email software.
So it can pull all of this information it needs to actually start outlining my welcome series. So it's going to ask you some questions through this, like what are you trying to do? How many emails?
Let's go with two more. And even for me, it could actually put them straight into ConvertKit. But we're just going to run them as Markdown here as well, because I actually want to outline and actually write a lot of these myself.
What's cool is it's actually used... my email connector. And by the way, you can use like the MailChimp connector, et cetera, if you use a different email service to actually go into ConvertKit or Kit as it's now called and look at my welcome email sequence to actually analyze what is in there at the moment and then be able to build from that.
I don't even have to copy and paste anything in, which is super powerful because that's where connectors actually start automating some of this work for you and this analysis and this output. I'm actually going to do my next video is going to be my top marketing connectors. And one of them is going to be kit.
So keep an eye out for that video. But it's going to build out this file and this sequence for us to start working with.
The Hook

The bait, then the rug-pull.

The course opens on a credential (450 skills built, 3,000 students taught) and a promise: by the end you will have a working SEO department of skills that hand work to each other under a manager. The real lesson underneath the build is about sequencing. Every level gets earned by first proving the single skill below it works.

Frameworks

Named ideas worth stealing.

10:20model

Anatomy of a skill

  1. Description (what it does and trigger phrases)
  2. SKILL.md (decisions, order, what good looks like, what to never do)
  3. Reference files (templates, checklists, examples, scripts)

Three parts. The description decides when the skill fires, the main file holds the process, and references load only at the step that needs them.

Steal forany skill or agent instruction file
18:18concept

Two types of skill

  1. Deterministic: known output shape, fails loudly
  2. Non-deterministic: judgment, taste or voice, fails quietly

Classify the skill before building. Deterministic skills are faster to get right; non-deterministic skills need ongoing tuning.

Steal forscoping any AI automation
21:10list

The five levels

  1. Run: wrapped prompt, no input
  2. Ask: needs your input or expertise
  3. Connect: reaches outside tools via connectors
  4. Chain: skills hand off to each other
  5. Manage: an orchestrator routes goals to skills

A way to describe complexity, not a ladder you must climb. Climb only as far as the pain justifies.

Steal forplanning an automation roadmap
26:57list

Three ways to build a skill

  1. Wrap a proven prompt
  2. Run the task with Claude until it is right, then capture it
  3. Record your screen while narrating the process

Wrapping is fastest when the prompt is already dialed. The run-then-capture route produces the best skills because the house rules emerge from real corrections.

Steal forturning any SOP into an AI workflow
1:06:57list

Six rules for building

  1. One skill, one job
  2. Keep the main file tight (around 500 lines)
  3. Write code for the mechanical bits
  4. Build from work you have done well
  5. Show it three to five examples of good
  6. Stop skills fighting each other

The checklist for moving a skill from average to reliable. Most failures trace back to scope creep or a bloated main file.

Steal forauditing an existing skill library
1:21:38model

SEO department loop

  1. Search visibility audit
  2. Six-month SEO strategy
  3. SEO blog writer
  4. SEO client report
  5. Report feeds back into strategy or a targeted audit

Each skill knows its intake and handoff, and the report loops back so the strategy stays current. An orchestrator sits on top.

Steal forany recurring client service
CTA Breakdown

How they asked for the click.

VERBAL ASK
03:07link
“This guide has all the prompts and steps that I'm using in this video. You can grab it below, there's a link in the description where you can get it for free. It's inside something called my AI recipe vault.”

Early, low-pressure lead magnet ask tied directly to following along, repeated at the wrap-up and inside both bonus segments.

Storyboard

Visual structure at a glance.

open
hookopen00:00
what a skill is
promisewhat a skill is03:48
five levels
valuefive levels21:06
first skill saved
valuefirst skill saved32:56
six rules
valuesix rules1:08:28
strategy skill
valuestrategy skill1:19:33
chained pair
valuechained pair1:26:25
voice evals
valuevoice evals1:56:49
trend jack
valuetrend jack2:23:25
Frame Gallery

Visual moments.

One-click upgrade to your Google

Get more breakdowns in your search results

Add Modern Creator as a preferred source and Google shows you more of our breakdowns in Search, Top Stories, and AI Overviews. It only changes what you see, and you can undo it in your Google settings anytime.

Add to Preferred SourcesOpens your Google source preferences with us pre-loaded. Tick the box and you're done.
Watch next

More from this channel + related breakdowns.