Claude's new "Skills" feature transforms AI interactions from repetitive prompting into building a personalized, reusable AI operating system, enabling consistent, high-quality outputs by encoding specific workflows and brand standards.
Mind Map
Clique para expandir
Clique para explorar o mapa mental interativo completo
Claude just got even more powerful with
the recent Opus 4.6 update. And if
you're still starting from scratch with
every conversation, reexplaining
everything, pasting your formatting
rules in, pasting your brand guidelines
in, and then doing the same thing all
over again tomorrow, then you're leaving
serious productivity on the table. And
here's the thing, even after all that
effort, the outputs still aren't
consistent. Today, I'm going to show you
how to go from this super long,
exhausting prompt to this, all while
maintaining consistency and quality.
We're not just prompting anymore. We're
building a personal AI operating system.
And the feature that makes this possible
is called claude skills. And by the end
of this video, you'll know what claude
skills are, why they're such a big deal,
and you'll know how to build your own
skills, turning any workflow you're
already doing into a portable, reusable
system that works anywhere inside of
So, what actually is a Claude skill?
Here's the simplest way to think about
it. A skill is like an instruction
manual that tells Claude how you want a
specific task done, what steps to
follow, what tools to use, what
standards to meet, so it executes the
same way every single time
automatically. Think of it like a
playbook. A coach doesn't reexlain every
play before every game. The playbook
exists, the team knows it, and they just
run the right play when the moment calls
for it. That's exactly what skills do
for Claude. Now, technically, a skill is
a folder, and inside that folder is a
required file called skill.md. That's
where your instructions live. And as an
option, you can include scripts,
reference documents, and assets like
templates. Before skills existed, you
had two options. Either you repeated the
same detailed instructions in every new
chat, which is slow and inconsistent, or
you used a clawed projects with custom
instructions baked in. And projects are
great, but they have two limitations
that start to hurt as your workflow
grows. First, they're not portable. So
the instructions that you put inside a
project only lives inside that specific
project. So when you start a new chat in
a different project, you're starting
without that context. The second thing
is that they're not stackable. So you
might have one project for copywriting
and another for data analysis, but you
can't directly combine them into a
single shared workspace. They operate
side by side, but not as one unified
system. Skills solve both problems. You
take the instructions for how you want
something done, package it into a
folder, and then upload it into Claude.
Now, once activated, that skill becomes
portable across your account. You can
use it in regular chats, inside
projects, in cloud code, and in API
workflows you set up instead of being
locked to just one project. Now, there's
three categories of skills. You have
official skills built by Anthropic,
things like document creation, theme
styling, internal communications. Then
you have custom skills that you build
yourself. And you have community skills
shared by other users. But be careful
with these. I'll talk more about
security later. All right. So to get
started with actually using cloud
skills, the first thing we need to do is
we need to go to settings and then under
capabilities then you're going to see
something called code execution and file
creation. You need to toggle this
setting on. Once this is toggled on,
you're going to scroll down lower on the
page and you're going to see skills just
below memory. Now when you click on
example skills here, you're actually
going to see a list of anthropic created
skills and you can toggle on the skills
that you actually want. But here's a
quick tip. I recommend only having a
couple of these that you're actually
planning on using toggled on at one time
because otherwise Claude might actually
get confused and call a skill that you
don't want inside your chat. So, just be
mindful of that. Now, here's another
quick tip that's really important.
Skills are supposed to trigger
automatically when they're contextually
relevant, but honestly, they don't
always based on my experience. So, I
recommend going into your settings under
general and then under your profile and
adding a line that's telling Claude to
always consider relevant active skills
when responding. That one sentence makes
a huge difference in how consistently
the skills activate. Okay, so now that
you have the foundation, let's put this
into action with our first use case. One
of the fastest ways to see skills in
action is to take an official skill that
already works and extend it with your
own standards. No building from scratch,
no complex setup, just adding your brand
on top of what's already there. All
right, here's the scenario. Claude has a
built-in skill called theme factory, and
it applies pre-built visual themes to
anything Claude creates, like landing
pages, documents, or web components.
It's got about 10 themes built in, and
they look decent, but they're generic.
They don't look like your company. So,
let's fix that. So, let's say we have a
company called AuraNC Digital, a tech
forward marketing agency. I've got three
things ready when it comes to the look
of the brand. I have the company logo, a
brand color palette with hex codes, and
our font pairings. And that's all we
need to get started. Now, before we
actually create our first skill, I want
to make sure that under settings and
under skills, we have our skill creator
skill toggled on. Otherwise, this is not
going to work. So, just make sure you do
that. Now, I'm going to create a new
chat. And then in that chat, I'm going
to upload the word document that has our
logo, colors, fonts, etc. And then I'm
going to give Claude this prompt. Read
the theme factory skill. Then create a
new custom skill called Aura Sync theme
that extends it with Orura Synync
Digital's brand standards. And then I'm
going to give it the brand standards in
the in the word document. And then
basically say you know what the look of
this should actually include dark
background accent colors etc. And then I
say use the skill creator skill to
ensure proper formatting. Now watch
what's happening. Claude first reads the
theme factory skill to understand the
existing theme structure. Then it reads
the skill creator skill to make sure
that it's properly formatted and then it
analyzes our brand, the fonts, the
colors, the logo and builds a new skill
that layers the brand on top of the
existing theme system. And after it's
done working, here is what we actually
get. The skill.md file. Now, here's a
quick thing that we want to pay
attention to here is the description
field in the skill file. This is one of
the most important lines in your whole
skill because this is what Claude reads
when it decides when to trigger the
skill. So, you want to make sure it
includes what the skill does. And
specific phrases might be something like
Orura sync branding or use our brand
colors or apply our company theme. The
more specific your triggers, the more
reliably it's going to fire. All right.
So, now I'm going to download the zip
file. Then I'm going to go to settings
and under capabilities where it has all
my skills, I'm going to click on the
plus sign. And then I'm going to upload
the zip file as a skill under the skills
section and I'm going to toggle it on.
Awesome. So now we have our skill
created. Let's test it out. So inside a
new chat, I'm going to give Claude a
quick brief about our company and then
I'm going to ask it to build a landing
page for this company. I'm also going to
add a few more details about Aura Sync
so that it knows what type of
information to actually put on the
landing page. I'm not going to say
anything about styling because our skill
has all of that information. All right.
So, after working for about a minute or
so, let's see what it came up with. Wow,
I actually think that looks really good.
It has that dark background that I was
going for, the electric blue accents on
the buttons and some of the text. And it
looks very much on brand. The only weird
thing is that the logo kind of didn't
come out uh exactly how I wanted it to.
I put it on a transparent background and
it didn't quite get that right, but that
would be an easy fix. But this looks
like pretty close to what I was going
for. Notice that I didn't mention the
name of the skill anywhere in the
prompt. Claude triggered it
automatically because the task matched
the description of the skill. And here's
the thing, this same theme now applies
to everything I create for this company.
Watch. I'm going to ask Claude to draft
a one-page executive summary about
Orsync's Q1 performance. And when I do
that, here's what it came up with. You
can see that the report has the same
colors, the same fonts, that same logo.
So that one skill is applied everywhere
automatically. And because it's a skill
and not a project, I can close that
conversation and open up a completely
empty conversation. And the Orura Sync
theme is still there. It's accountwide.
So my brand is now part of my Claude
profile. And this approach works for any
official skill. You could extend the
brand guideline skill with your own
design system. The point is you don't
have to build from scratch. Start with
what already works and make it yours. So
you just saw how easy it is to take what
Claude already does well and customize
it to your brand. But skills are a layer
that sits on top of Claude's core
features, projects, artifacts,
dashboards, and if you haven't locked in
that foundation yet, skills won't land
the way they should. If you're looking
to become better at using Claude and you
want a road map to get you up to speed
quickly, then I suggest you take a look
at this free resource from HubSpot
called the complete guide to Claude AI.
This guide covers the entire cloud
foundation, setting up projects,
building artifacts, and interactive
dashboards, designing real workflows, so
that when you start adding skills on
top, everything else clicks into place.
Inside, you'll find project templates
that you can copy directly, like a full
content marketing setup with exact
commands and document lists, an
interactive marketing performance
dashboard, and more. It even includes
best practices and guidance on how to
implement Claude across your entire
team. My favorite section is the one on
using Claude as an executive assistant.
It gives you step-by-step instructions
on setting up automated morning
briefings, a content optimization
system, meeting follow-up, and task
tracking across projects. It's super
practical and helps save hours every
week. Download this guide using the link
in the description, and thanks to
HubSpot for sponsoring this video. All
right, so before we go deeper with our
next use case, here's a quick filter.
Not every workflow needs to be a skill.
So, when you're deciding whether or not
to create a skill, ask yourself three
questions. Number one is, how repeatable
is the task? If you only do it once,
just stick with a regular prompt. But if
you're doing the same thing weekly with
the same format, the same rules, create
a skill. The second question is, does
consistency matter? If the output needs
to hit a specific standard every time,
like a brand guardian skill that scores
content against your tone of voice, for
example, that's a skill. And number
three is, could somebody else run it? If
you could hand this to a new team member
and say just ask Claude and the
instructions are clear enough, it's
skill ready. And if you have two out of
three of those, build the skill. Now,
extending skills is the quick win. But
the real power comes when you build
skills from scratch that encode your own
workflows. And specifically, when you
encode what's already working so you can
repeat it on demand. Here's the
scenario. You have a piece of content
that performed really well. A YouTube
video with great retention, a blog post
that ranked, an email sequence that
converted. You know it worked, but you
probably can't explain exactly why in a
way that's repeatable. That's what we're
going to fix. I'm going to paste the
hooks from my three best performing
YouTube videos. These are the openings
that grabbed people. You know, the first
30 to 60 seconds that determines whether
or not someone stays or clicks away. And
I'm going to ask Claude to find the
patterns. So, I'm just giving it this
prompt right here. Not going to read out
the prompt. And after Claude thinks for
a bit, here's what it comes up with. So,
Claude identifies that there's a
consistent structure across all three
hooks. So there's an anchor where I meet
the viewer exactly where they are,
naming the tools or the situation
they're already using. Then there's a
diagnosis, so I validate what they're
already experiencing and surface the
real problems that they haven't
identified yet. Then there's a
credibility signal, so I share my own
experience and I build trust with that
person. And then there's a reframe,
which is the key move. I disrupt their
assumption about what the problem
actually is. And finally, a promise. I
stack multiple specific outcomes so that
they know exactly what they're going to
be getting from the video. Now, here's
the thing. I knew the hooks worked, but
I couldn't have written that five-part
sequence down if you asked me. It was
more of intuition, but that can't be
replicated. But now, Claude gave me a
framework to follow. Now, I'm going to
ask it to take this analysis and package
it as a reusable Claude skill called the
hook generator. This skill should accept
any topic as input and produce three
hook variations following this exact
structural pattern. All right. So after
running for a moment, here is the skill
that generated on the right hand side.
So you can see there's some really
detailed instructions here, including
when the skill gets triggered, the five
element framework that it broke down
when it was analyzing my hooks, etc. So
now on the top right hand corner of the
screen, I'm going to click on copy to
your skills, that button there, and now
it's going to be part of my skills
within my capabilities under my
settings. Okay, so now let's actually
test this hook generator. I'm going to
start a brand new chat and I'm going to
pick the most boring title I can think
of and I'm purposely not going to give
it a lot of instructions. I'm just going
to give it basically one sentence. Okay.
Generate three hooks for a video called
five tips for better time management. So
now the skill is going to do the heavy
lifting because the prompt is so basic.
All right. So let's see what it came up
with. Wow. So look at these. Each one of
these follows the exact same five
element structure. the anchor,
diagnosis, credibility, reframe, and
promise, but with completely different
angles. The first hook enters through
the productivity tool trap. So, you've
got the apps, you've got the systems,
you're still not getting to what
matters. And the reframe is time
management isn't about time, it's about
energy management. Pretty good. The
second hook is all about being
overwhelmed and being really busy. So,
your schedule's packed, you're
exhausted, and the reframe is that the
real skill isn't doing more, it's being
ruthless about doing less. I like that.
And the third hook enters through the
plans falling apart angle. So you plan
your week perfectly on Sunday and by
Tuesday it's fiction. And the reframe
here is stop building rigid plans for a
chaotic world. Build systems that absorb
the chaos. I think that's really good.
So those are three completely different
angles built on the same structure as
what worked for my top performing
videos. And each one of these sounded
like something you'd actually want to
watch because the structure underneath
is proven. This is the real unlock.
You're not just saving time, you're
taking the patterns from your best work
and actually making it explicit and
clear. You're training your AI on your
own success formula. And this method
works for any repeatable structure.
High-converting email sequences, reverse
engineer the framework and skill it
sales call scripts that close, reverse
engineer the flow and skill it. Add copy
that outperforms, reverse engineer the
hooks and angles and create a skill.
Report formats that your executives
love, reverse engineer the layout and
create a skill. Your best past work
becomes the template for all your future
work. That's the real power of building
skills from scratch. Now, let's combine
everything. This is where multiple
skills work together with Claude's
built-in capabilities and connectors,
and it starts to feel like a workflow
engine. Now, for our third use case,
here's the situation. I have a CSV file
with 50 leads, company names, industry,
employee count, revenue, engagement
scores, all these different data points.
I want Claude to analyze them, score
every single one against my ideal
customer profile, and then build a
presentation that I can bring to my next
Friday sales meeting. And because I'm
going to be doing this analysis over and
over again, I'm going to create a skill.
So, I'm going to give it this prompt
with scoring rules for our ideal
customer profile criteria. And this
skill is going to contain which
industries I prioritize, which company
size is my sweet spot, how I weigh the
engagement scores, which source channels
are signaling high intent, and what
automatically disqualifies a lead. And
all of that logic is going to be baked
into the skill so I never have to
explain it again. All right, so Claude
works for a minute or so, and here's the
skill that it comes up with on the
right. You can see this is super
detailed here, and it has everything
that we need to know about scoring our
leads against our ICP criteria. So
again, I'm going to go to the top right
hand corner of the screen and I'm going
to click on copy to your skills, that
button. And now our skill is added to
our capabilities within our settings.
All right. And now we're going to test
this out. So let's create a brand new
chat. And I'm going to upload my CSV
file with all my leads. And I'm going to
give it this prompt. Score these leads
against our ideal customer profile and
give me the full breakdown with their
tier assignments, key reasons, and
recommended actions for each lead. Then
summarize the overall pipeline. All
right. Now, here's what it came up with
when I gave it that prompt. All right.
Now, watch what's happening here. Claude
is actually reading the lead scorer
skill to understand my criteria. It
processed all 50 leads through the
scoring engine. And then it delivers a
full spreadsheet with two tabs in it.
Every lead scored with points,
breakdowns, and recommended actions in
one sheet and then a pipeline summary in
the other. We've got 25 hot leads, five
warm, five cold, 15 disqualified. And
each one of these has the key reason
here. So it actually provides the reason
for the score and the recommended action
that we should take for each of the
leads. So these are really actionable
insights that we can walk into our
meeting with wellprepared. Now here's
where this gets even more powerful. I
also have Gamma connected as a
connector. That's an AI presentation
tool. If you want to set this up for
yourself, you go to settings, then
connectors, and you'll find Gamma in
there. Now once it's connected, Claude
can actually send data directly to it.
So, I'm going to take these results and
turn them into a polished deck with one
more prompt. So, I'm going to say, "Now
that you've scored the leads against our
ICP, create a presentation with these
results in Gamma." So, Claude takes all
the scoring data and sends it to Gamma
through the connector. And in this demo,
it actually even picks a dark theme here
with cyan and teal accents that closely
match our OruraNC palette. And the way
it's coming up with that is it's reading
the styling skill that we created for
the Ourync brand within our first use
case. So, it's using that as a reference
point so that it feels on brand right
out of the gate. Pretty amazing. So,
after working for a couple minutes,
here's what it came up with. We have
slides with a scoring methodology. It
came up with 10 different slides. It has
a pipeline summary of the 50 leads and
the distribution of that. It has a slide
with our action plan on it for the sales
team and the key patterns and insights
from all this information. That's a
presentation I can open, edit if I
needed to, and actually export it as a
PDF or a PowerPoint and bring it to my
sales meeting. And that entire deck was
generated from one prompt. Pretty
amazing, right? Now, this is the key
concept of this example. Don't build one
massive skill that does everything.
Build small, focused skills that each do
one thing well, and let Claude
orchestrate them with your connectors.
The lead scorer skill handled the
analysis logic. Gamma handled the
presentation and it even got the style
inspiration from the first skill that we
created in this video. Three
capabilities working together from two
simple prompts and this scales to
whatever your business needs. You can
pull data from notion through the notion
connector, run it through a custom
analysis skill and output a formatted
report. The combinations are as specific
as your workflows. Now, if you were
doing this inside a project, you
wouldn't need to actually repeat the
workflow details in the project
instructions. Just tell Claude which
skills to use for which task. For
example, you could say, "For lead
analysis, use the lead scorer skill. For
presentations, send to Gamma." And then
just let Claude handle the rest. Now,
before you go building a dozen skills
tonight, here's some guardrails. I
touched on this at the beginning of the
video, but there are community skills
available on GitHub created by other
people. But downloading a public skill
from GitHub is like running code from a
stranger. So before activating any
community skill, open up the skill.md
file and read it. Look for hidden
instructions, references to external
endpoints, anything doing more than the
skill claims. Prompt injection is a real
risk. So audit before you activate. I
personally recommend just sticking with
anthropic skills or skills that you
create on your own, just like we did in
this video, where possible. The second
thing to keep in mind is something I
mentioned at the beginning of the video,
which is to have only a few skills
toggled on at one time. Here's another
reason why Claude uses something called
progressive disclosure. The description
field of every active skill sits in
Claude's system prompt at all times. The
full instructions only load when
triggered. But more active skills means
more context consumed before Claude even
starts your task. So just keep that in
mind. The next tip is to keep things
organized by naming your skills in a
consistent way. So start each custom
skill with your company name, for
example, or initials so that they stay
grouped together and then use short
hyphen style names like brand guideline
review instead of spaces. Now, here's a
quick debugging tip. If a skill isn't
triggering properly, you can ask Claude,
"When would you use the brand guardian
skill, for example?" It'll quote the
description back to you, and if what it
reads doesn't match how you're actually
using the skill, then you'll know
exactly what you need to fix. And my
last tip is that skills are static. So
they don't evolve with conversations. So
you need to set reminders regularly to
actually go in whether it's every
quarter or every month to actually make
sure that the skills are still valid.
Remember to review and update these
regularly. Skills give Claude your
methods. Connectors give Claude your
tools. Combine both and you're not just
automating tasks, you're building agents
that execute your business strategy
across your entire tool stack. So give
this a try this week. Use one of the
techniques we covered here for your own
task and let me know how it goes in the
comments. If you enjoy this video, then
please give it a thumbs up. It really
helps the channel. And if you want to
learn more about how to use AI to level
up your work and your life, then click
Clique em qualquer texto ou marcação de tempo para ir diretamente àquele momento do vídeo
Compartilhar:
A maioria das transcrições fica pronta em menos de 5 segundos
Cópia com um cliqueMais de 125 idiomasPesquisar no conteúdoIr para marcações de tempo
Cole a URL do YouTube
Insira o link de qualquer vídeo do YouTube para obter a transcrição completa
Formulário de extração de transcrição
A maioria das transcrições fica pronta em menos de 5 segundos
Instale nossa extensão para Chrome
Obtenha transcrições na hora sem sair do YouTube. Instale nossa extensão para Chrome e acesse com um clique a transcrição de qualquer vídeo direto na página de reprodução.
