So most people use Clawd in the most basic way that you can imagine.
They open up a chat, they type in a prompt, they get an answer,
and then what do they do? They repeat it. And that's basically it. They never actually go deeper, but Claude is actually capable of so much more than that, and most people have no idea.
With Claude skills, you can catch bugs before you even see them. You can keep your sessions clean for hours and you can make Claude behave exactly the way that you needed to for a specific situation.
And the best part is it gets smarter every time you use it. There are now thousands of Claude skills and I have tested more than 250
of them. Most are broken, outdated, or just system plumps
with a fancy name. But buried inside that mess are nine skills that represent a completely different way of using Claude. So I'm splitting them into three categories for today's video. Essential Claude skills that you can use right now, Claude code skills for building, and also one co work pattern that ties everything
together. This is gonna be a fun one. Don't forget to check out the three score community down in the description below. But right now, let's get into it. So we are starting off with category number one and that is the essential Claude skills. So these work in Claude desktop. There's no terminal, no code needed. Just upload a zip file through customize and you are set. So let's get into skill number one and that is skill creator.
This is our first skill and it's basically something that sounds pretty funny, but it actually solves most of your problems. This is one that is built for beginners. But ironically,
it's one of the most overlooked skills that you will find anywhere.
Not because it's hard to find, I mean, it's actually pre installed, but most people just never think to actually use it first. So you don't need to download anything, just open up Claude desktop and then go to any tab in Claude and then just type in this prompt. I want to create a skill using slash
skill dash creator.
Just type that in. And here's the problem that most people actually run into. They have a workflow that they just repeat about three, four, five times a week. I mean, it's the same instructions, the same format, the same corrections, and every time they start a new chat,
they explain it all over again from scratch. Skill Creator actually lets you turn that into a reusable skill in just a few minutes. You describe what you want the skill to do, and then Claude actually interviews you with a few questions just to basically, like, nail down all of the details, and then it builds the full skill dot m d file for you, and there's no markdown editing. It's just a pure conversation.
But here's the part that nobody actually shows. After it builds the skill, it automatically generates test cases with the skill active and also without the skill. So you can actually see the output side by side. So if the skill doesn't actually improve the result, then you know before you ever even commit to using it. That step is the difference between a skill that works and a skill that you think works.
I mean, most people skip it, so I'm telling you don't. Now we get on to the second skill and that is prompt master.
So this one is on GitHub. All you have to do is basically just go and search for prompt master by n dash I dash d dash h dash I dash n
dash j dash s.
And then what you do is you download the repo as a zip file, and then you go over to Claude, you open up the sidebar, and then you click customize and then skills, and then upload a skill, and you are done. So here's the problem. Now most people plant Claude with messy brain dumps. It's always long. It's unstructured,
and it's basically just full of vague instructions.
And for simple tasks, that is fine,
but for anything that's complex,
the the output quality drops pretty fast and it's noticeable.
So prompt master
actually takes whatever you throw at it and it turns it into a structured optimized prompt according to the best practices. It detects which AI tool the prompt is for, it extracts your intent across nine dimensions, and it asks a maximum of three clarifying questions
if something critical is missing from all of this, and it delivers one clean prompt that you can simply just copy and you can use.
It works with over 30 tools Claude, ChatGPT,
Cursor, Midjourney, Stable Diffusion, you name it, all of it is there. But the real power is using it inside Claude itself.
You write your messy brain dump, you add, use the prompt master skill on this one and then Claude actually rewrites it before processing. One extra step but
dramatically
better outputs. Now here's a quick pro tip, you can actually add this to your general instructions inside Claude desktop settings so it auto enhances on every complex prompt. You never have to think about it ever again. Now that takes us perfectly into skill number three and that is the fact checker.
So multiple versions of this exist. The easiest one is to grab from Daymaid's Claw Code Skills repo on GitHub and all you do is just download, zip, upload through, customize, and then it's basically the same process that we discussed before. The AI generates confident sounding text. So sometimes it is wrong and if you're putting a name on it like a LinkedIn post, a script, or a client deliverable,
then wrong is basically a huge problem. So this skill runs a systematic fact verification pass on every or any text that you give it. So it reads every factual claim and it cross references against external sources using web search and it gives you a report like what's confirmed, what's unverifiable,
and what
what's flat out false.
So I use some three things, anything AI generated that goes out publicly, so my own video outlines before I film and other people's content when I want to check if what they are claiming holds up. Now here's another pro tip for you, Once you have it installed, just add a step to your writing skills that runs the fact checker automatically before giving you the final output.
You stop the problem before it even reaches you. Now we go on to skill number four and that is the humanizer. Grab this from Blader's humanizer repo on GitHub, download it as a zip and upload through customize and takes about thirty seconds,
and this one is pretty straightforward.
It removes
the signs of AI generated writing from any text that you give it, and you should be running this on anything AI generated that other people are going to read over. It's based on the Wikipedia's comprehensive signs of AI writing guide and it detects 25 specific patterns, inflated symbolism,
promotional
language,
m dash overuse,
and I know you know what I'm talking about, and also the rule of three AI vocabulary words like leverage
and streamline,
all those vague attributions
and the filler phrases,
all of those things that make the AI text feel like an AI text.
But here's what makes this one better than just telling Claude to make it sound more human.
If you give it a sample
of your own writing, then it actually analyzes your sentence rhythm, your word choices, your quirks,
and then applies those to the rewrite instead of producing generic clean output. I run this on LinkedIn posts, client emails, onboarding docs, community guides,
anything that goes out with my name on it. And if you use writing skills like LinkedIn writer
or a newsletter skill,
add a humanizer as a final step so that it runs automatically before you see the output. That's only gonna give you the best results.
Now we are moving on to category number two and that is the Claude code skills. So those four work in any Claude chat.
But if you use Claude code, then the next four skills operate at a completely different level. For skill number five, I have a powerful combo of playwright and superpowers.
This combines two skills. Playwright is an official Anthropic skill, so you can find it in the Anthropic skills repo on GitHub,
and Superpowers is from Obera's
GitHub repo. So you can install both through the plug in marketplace in the code tab, and you'll need Playwright installed
on your machine. Super important.
Everyone shows Claude writing code,
but nobody actually shows Claude testing the code that it actually just allowed. Claude bolds you a web app, and it looks right, but did it test the sign up flow?
Does the button work on mobile? You don't know. By default,
you are the q and a department.
Playwright handles the testing side. Once active, Claude navigates your local app like a real user. It clicks through flows, it fills out forms, it captures screenshots at every step, and it reports back exactly what broke.
But superpowers takes it even further. It forces Claude to plan before it codes,
write tests before it ships, and it even reviews its own work before you ever see it. So instead of Claude building something
and testing it after,
it's building with quality gates baked into every step. Now the moment that actually sold me on this was that Claude built a simple app. It planned the architecture first, it wrote tests alongside the code, and then it then played right to verify everything end to end. And it found a button that was technically there but visually hidden on screens under 400 pixels wide. That's the kind of bug that reaches your users if nobody
catches it first.
Now we have to go to skill number six and that is Septum
Agents Pack.
So this is going to take you to the next level. Most people using Claude Co do everything with one agent in one context window. By default,
you are the QA department.
That's like hiding one person to be your architect, your lawyer, your CFO, your marketer,
and your QA tester
all at once.
This skill drops a full name team in your project in just a single move. 10 specialized sub agents
each with a name and a role. Atlas handles the planning, Luca handles the architecture,
Canon handles the brand, Amber handles the marketing, and Telly handles the finance, Nova handles the design, Ward handles the legal side, and Meta handles the customer experience. And then on top of that Juno handles the research, PIP handles the coordination,
so you genuinely have an entire team.
In practice, you are building a new feature.
You ask Claude to use Atlas to plan it out and then Ward to check for the legal issues and then Tally to estimate the costs. That's three perspectives. That's three areas of expertise
in just one project.
You never have to re explain context before each agent reads from the same project files. Now the original Septum Agents pack costs about $49,
but I built my own free version that does the exact same thing, and you can actually grab it in the free school community. The link is down in the description below. Now for skill number seven, and that is the view, and this has to be one of the most underrated skills.
Claude writes code, but it doesn't really view its own work unless you tell it to. You type in slash review after any bold and then Clawd actually checks for bugs, edges, cases,
security issues, and design problems all for you. The stuff a careful
human reviewer would catch and you can actually use it as your last step before merging anything. So it runs locally, it costs nothing extra, and it catches things that Claude missed the first time around. But did you know that you can actually do a security review directly
in code? All you have to do is just type in slash security dash review and you can see a review of the pending changes
on your current branch. Now let's discuss skill number eight and that is context and compact.
Now every tool under Claude dumps raw data into your context window. So after about thirty minutes of real work, half your window is noise and when it fills up, then Claude auto compacts and it forgets what it was doing.
So slash context shows you what's eating your window up right now and slash compact lets you compress it on your own terms instead of letting Claude decide randomly. So the habit that you're going for here is you wanna run context every twenty minutes and then when you hit 60,
you run compact with a focus like compact focus on auth module
and then your sessions run longer and then Claude stops forgetting and you stop wasting prompts at explaining things that you really don't need to. So that was category number two and that was basically just the code skills. Now we are getting into category number three, and that is the co work pattern. Okay. And let's start off with skill number nine, and that is self improving skills.
So we are wrapping up our list, and we have
our final learning dot m d pattern.
So this is the one that I tell you to implement today because it's so important and that's basically if you only if you only had to take away one thing from this video.
Now there's no install needed. This is just a pattern that you apply to any skill that you already have and you just create a file called learnings dot m d alongside your existing skill file and then you add in one line to your skill that says before running the learnings dot m d. And here's why. You build a skill and it works okay, but it makes the same mistakes every time. You correct it and then the next run and it's just the same mistakes. The learnings dot MD pattern fixes this for you. So after every run, Claude logs what worked, what didn't, and what you corrected. They did specific scope to that skill. So the next time the skill runs, it divides those notes first and the skill actually compounds.
So I run a writing skill on day one, and then the output is decent but generic. You corrected and then the intro was too long, the headlines
needs a number,
the client hates passive voice,
those corrections go into learnings.md.
And by then five,
the skill has internalized
all of that. The learnings file from one of my content skills says something like headlines
with numbers
consistently outperformed,
intro paragraphs over 80 words flagged as too long by client, avoid the word leverage.
Client has specifically rejected this three times.
And that's not a prompt.
That's institutional
memory.
That single change turns any static skill into a system that learns your preferences
over time.
And here's the thing that nobody says out loud about Claude skills.
Installing a skill does not make you better at using Claude.
A skill is just a tool. A tool that you never improve is just clutter.
The one pattern that separates every skill on this list from everything else that you've installed is the learnings file.
Not because it's the most impressive skill,
but because it's the only one that gets better the more you use it. Every correction that you make, every preference that you log, every mistake that Claude repeats and you catch, that all goes in and it compounds over time. Now that's the difference between a calculator
and a full on computer.
So that is all nine skills and every install link is all down in the description below in the free school community. Go and check it out and I will catch you on the next one.