Tutorialthe whole build, step by step

5 Claude Code skills for beginners: Humanizer, Skill Creator, Grill Me, Caveman, Marketing Skills

Humanizer, Skill Creator, Grill Me, Caveman and Marketing Skills in Claude Code: the exact install commands, a free first test, and when to use each one.

By Eric Snyder, founder 14 min readChecked on Oct 31, 2026
Save this guidereceiptsgroup.com/guides/five-beginner-claude-skills
SetupFive install commands, once Node.js and Claude Code are on your computer
Running costAll five skills are free; Claude Code needs a paid Claude plan (Pro is $20 a month billed monthly, checked 2026-10-31)
You needA Mac, Windows or Linux computer, Node.js 22.20 or later, and Claude Code
First testA made-up paragraph through Humanizer: nothing gets posted or sent
In this guide
Start here
  1. Start here: paste this into Claude Code
The manual way
  1. How the pieces connect
  2. Which one, when
  3. Before you start: Node.js and Claude Code
  4. 1. Humanizer: strip the AI tells out of your writing
  5. 2. Skill Creator: turn a job you repeat into your own skill
  6. 3. Grill Me: get your plan questioned before anything gets built
  7. 4. Caveman: shorter answers, so your limit lasts longer
  8. 5. Marketing Skills: 53 skills for copy, SEO, ads and email
  9. Check they're all there
  10. First test: a made-up paragraph through Humanizer (nothing gets sent)
  11. Real use: prompts for real jobs
  12. Keep them updated (and remove one)
  13. What it costs
  14. When it breaks
  15. Sources, checked Oct 31, 2026

Here's the goal: five skills in Claude Code, installed in about five commands, and you know which one to grab for which job. A skill is just an instruction pack for Claude: a folder with a file called SKILL.md that teaches it one job. All five here are free and open source.

I checked each one at its source on 2026-10-31: who made it, the exact install command, what it actually does, and where the claims are thinner than the hype. Caveman, for one, publishes the numbers where it barely helps, and I'd rather you see those before you install it. Below: a prompt that walks you through all of it, then the manual way, one skill at a time.

Checked on Oct 31, 2026

Start herepart 1

Start here: paste this into Claude Code

If you don't have Claude Code yet, do the first two steps under “Before you start” below (Node.js and Claude Code). Then make a folder for your marketing work, start Claude in it, and paste the prompt. It installs all five, runs a first test that sends nothing anywhere, and hands you a cheat sheet.

bashMake the folder and start Claude in it
mkdir -p ~/marketing
cd ~/marketing
claude
PromptThe setup prompt (copy all of it)
Hi Claude. Please be my patient setup helper. I run a business and I don't code: one step at a time, tell me exactly what to type or click, and wait for me before the next step.

Goal: install five free skills for you, and teach me when to use each one: Humanizer (GitHub repo blader/humanizer), Skill Creator (anthropics/skills), Grill Me (mattpocock/skills), Caveman (JuliusBrussee/caveman) and Marketing Skills (coreyhaines31/marketingskills). Follow this guide; it's the source of truth for every command:
https://receiptsgroup.com/guides/five-beginner-claude-skills

I started you inside a folder called marketing in my home folder.

Steps:
1. Check my Node.js version with: node --version. It has to be 22.20 or later. If it's older or missing, send me to nodejs.org to download the LTS installer, and wait until I've done it.
2. Install the first four skills for every folder on my computer. One at a time: show me the command, explain each part in plain English, and run it only after I say yes.
npx --yes skills add blader/humanizer -g -a claude-code -y
npx --yes skills add anthropics/skills --skill skill-creator -g -a claude-code -y
npx --yes skills add mattpocock/skills --skill grill-me --skill grilling -g -a claude-code -y
npx --yes skills add JuliusBrussee/caveman --skill caveman -g -a claude-code -y
3. Install Marketing Skills in this marketing folder only, not everywhere, because it's 53 skills. Show me the command and run it after my yes:
npx --yes skills add coreyhaines31/marketingskills --skill '*' -a claude-code -y
4. Check they're all there with: npx skills ls -g, then npx skills ls. Then tell me to type /skills so I can see them myself. If one is missing, tell me to type /reload-skills.
5. First test, nothing leaves this computer: run /humanizer on the made-up paragraph in the guide's "First test" section. Show me the rewrite and the list of what it changed and why.
6. Give me a cheat sheet: one line per skill saying when I'd use it and exactly what to type to start it.

Rules:
- Don't turn Caveman on during this setup. I need full sentences while I'm learning.
- Never install, update or remove a skill without showing me the exact command and getting my yes.
- If a skill wants a key, token or password, stop and tell me. Never ask me to paste one into this chat.

House rules for this setup:
- If you use a technical word, explain it in plain English the first time.
- Ask me before you assume anything about my business, my accounts or my setup.
- Stop and check with me before anything that costs money or spends credits.
- Stop and check with me before anything that sends, posts or publishes to real people.
- Stop and check with me before you delete or overwrite anything.
The manual wayparts 2 to 15

How the pieces connect

This is the manual way: every step and every command. Claude follows it too.

The five don't plug into each other, but they line up nicely on one real job, like a new service page:

  1. 1
    Plan itGrill Me (/grill-me)→ a plan with the holes found before anything gets built
  2. 2
    Draft itMarketing Skills (/product-marketing once, then /copywriting, /seo-audit, /emails ...)→ a first draft that knows your business
  3. 3
    Clean it upHumanizer (/humanizer)→ copy that reads like you wrote it, same facts
  4. 4
    Save the repeatSkill Creator (/skill-creator)→ your own skill, so next time it's one command

Caveman sits off to the side: turn it on with /caveman for a long working session when you want shorter answers, and off with “stop caveman”.

Words you'll see

  • Skill: a folder with a SKILL.md file: instructions that teach Claude one job.
  • Slash command: typing / and a skill's name in Claude Code (like /humanizer) to run that skill on purpose. Most skills also kick in on their own when what you ask fits them.
  • Terminal: the window where you type commands (Terminal on a Mac, PowerShell on Windows).
  • Node.js and npx: Node.js runs JavaScript programs on your computer; npx comes with it and downloads and runs a tool in one go.
  • Skills CLI: the free command-line tool that installs, lists, updates and removes skills. You run it as npx skills.
  • Global (-g) vs project: global means every folder on your computer (~/.claude/skills; the ~ is your home folder). Without -g, the skill goes in .claude/skills inside the folder you're in, and only works there.
  • Tokens and limits: tokens are the chunks of text Claude reads and writes. Longer answers use more of them, and your plan's usage limit runs out faster.

Which one, when

From each skill's own README and SKILL.md, checked 2026-10-31.
SkillGrab it whenHow it starts
Grill MeBefore you build or buy anything: a new page, a new tool, a new process. It asks the questions you skipped.Only when you type /grill-me
Marketing SkillsWriting copy, checking SEO, ads, emails, pricing pages. Run /product-marketing first so the rest know your business.When your ask fits one, or by name (/copywriting, /seo-audit, /emails)
HumanizerBefore anything AI-written goes out with your name on it./humanizer, then paste the text
Skill CreatorThe second time you catch yourself explaining the same job to Claude./skill-creator, or “make a skill for ...”
CavemanLong working sessions where you know what you're doing and keep hitting your limit. Not while you're learning./caveman; “stop caveman” or “normal mode” ends it

Before you start: Node.js and Claude Code

  1. Install Node.js (22.20 or later)

    Wherenodejs.org/en/download

    The Skills CLI needs Node.js 22.20 or later. Download the LTS version (the long-term support one) and run the installer. Then open a new terminal window and check the version.

    bashCheck Node.js
    node --version
  2. Install Claude Code and log in

    Skip this if claude --version already prints a version. Claude Code needs a paid plan (Pro or higher); the free Claude plan doesn't include it. The first time you run claude, it opens your browser to log in.

    bashMac, Linux or WSL
    curl -fsSL https://claude.ai/install.sh | bash
    # open a NEW terminal window, then:
    claude --version
    Windows PowerShell
    irm https://claude.ai/install.ps1 | iex
    # open a NEW PowerShell window, then:
    claude --version

1. Humanizer: strip the AI tells out of your writing

Made by blader, MIT license. It's built on Wikipedia's Signs of AI writing, the field guide Wikipedia's editors use to catch undisclosed AI text. It checks for 26 patterns, strongest first: “it's not just X, it's Y”, one-line closers like “Let that sink in.”, deep-sounding sayings, staged run-ups, stock AI words like “testament” and “delve”, and dashes everywhere.

Two things I like about it. It doesn't make anything up: if a sentence needs a name, a number or a date it doesn't have, it asks you instead of inventing one. And it's upfront that it edits for readers, not to sneak past AI detectors; its README says detectors still flag most of its output.

  1. Install it

    This is the command from Humanizer's own README for Claude Code through the Skills CLI.

    bashInstall Humanizer (every folder)
    npx skills add blader/humanizer --global --agent claude-code
  2. Use it

    Type /humanizer, then paste your text. You get its first rewrite, a short note on anything that still sounds off, and the final version. To make it sound like you, give it two or three paragraphs you wrote yourself first. Point it at a file and it changes the writing only, leaving code, data and links alone.

    PromptMatch your voice
    /humanizer
    
    Here's a sample of my writing for voice matching:
    [paste 2-3 paragraphs you wrote yourself]
    
    Now rewrite this text:
    [paste the AI text]

2. Skill Creator: turn a job you repeat into your own skill

Made by Anthropic (the company behind Claude), Apache 2.0 license. Its job, in its own words: create new skills, improve existing ones, and test how well they work. You tell it the job, it drafts the SKILL.md, writes a few test prompts, runs them, shows you the results and rewrites the skill from your feedback.

The testing part runs small Python scripts and takes a while. If you just want the skill written, say so: its own instructions tell it to skip the formal tests when you'd rather just work through it together.

  1. Install it

    From Anthropic's skills repo, just this one skill.

    bashInstall Skill Creator (every folder)
    npx skills add anthropics/skills --skill skill-creator -g -a claude-code
  2. Or the plugin way

    Claude Code's own docs install it as a plugin instead (a plugin is a bundle Claude Code installs from a marketplace). Type this inside Claude Code. Pick one way, not both. As a plugin, its slash command gets the plugin's name in front; asking for skill-creator by name works either way.

    Inside Claude Code
    /plugin install skill-creator@claude-plugins-official
  3. Use it

    Tell it the job and where it should live: ~/.claude/skills for every folder, or .claude/skills for this project only.

    PromptMake a skill from a job you repeat
    /skill-creator
    I keep asking you to <the job, e.g. turn my inspection notes into a short homeowner summary>. Make it a skill in ~/.claude/skills. Ask me how I do it, one question at a time, then show me the SKILL.md before you save it. Skip the formal tests for now; we'll try it on one real job together.

3. Grill Me: get your plan questioned before anything gets built

Made by Matt Pocock, MIT license. He calls it one of his most popular skills, and it's for non-code plans too. You tell it what you want to do, and it interviews you in rounds: numbered questions, each with its own recommended answer (so “yes” takes the recommendation), until every decision in your plan is settled. It won't act on the plan until you confirm you're on the same page.

One thing most install videos miss: grill-me is a two-line skill that hands off to a second skill called grilling, which holds the actual questioning. You need both, which is why the command names both.

  1. Install it (both parts)

    bashInstall Grill Me + grilling (every folder)
    npx skills add mattpocock/skills --skill grill-me --skill grilling -g -a claude-code
  2. Or the whole set as a plugin

    Matt's README installs every one of his skills (27 listed in his README, most of them for software work) as a plugin that updates itself. If you go this way, skip the command above: his README warns that installing both ways gives you every skill twice. His /setup-matt-pocock-skills step is for his engineering skills, not Grill Me.

    bashHis Claude Code install (terminal)
    claude plugin install mattpocock-skills@claude-plugins-official
  3. Use it

    It only starts when you type /grill-me: Claude won't fire it on its own. Answer each round; say “yes” to take its recommendations.

    PromptGrill a plan
    /grill-me
    I want to <the plan, e.g. add a financing page to my website before spring>. Grill me until the plan makes sense. Don't build or change anything.

4. Caveman: shorter answers, so your limit lasts longer

Made by Julius Brussee, Apache 2.0 license. The joke in the video is “me read file, me fix bug”. The real skill is less cartoon than that: its rules say answer first, cut the greeting and the recap, short sentences, and no “me think” theater. It never drops words like not, never or only, keeps numbers and commands exactly as they are, and switches back to full sentences for security warnings and anything you can't undo. Once on, it stays on for the whole session until you say “stop caveman” or “normal mode”.

  1. Install the skill only

    This is the “skill alone” route from Caveman's README, narrowed to the one caveman skill (the repo holds many others).

    bashInstall Caveman (every folder)
    npx skills add JuliusBrussee/caveman --skill caveman -g -a claude-code
  2. Skip the full install for now

    Caveman's headline install (npx @caveman-ai/cli@latest) goes a lot further: it sets up every coding app it finds on your computer, sends usage stats by default, and one of its features (Auto, which picks the model for you) needs an account. That's a bigger decision than a beginner needs to make. The skill alone runs on your computer and sends nothing.

  3. Turn it on and off

    Inside Claude Code
    /caveman
    ...
    stop caveman

Example (made up). Normal: “Sure! I'd be happy to help. The reason your contact form isn't sending emails is most likely that the email setting was left blank when the form was set up.” Caveman: “Form email not sending. Email setting blank. Fill it in, then send a test.”

5. Marketing Skills: 53 skills for copy, SEO, ads and email

Made by Corey Haines, MIT license. On 2026-10-31 the repo had 53 skill folders: copywriting, SEO audits, ads and ad creative, emails, landing pages (cro), pricing, referrals, schema, cold email and more. The one to run first is product-marketing: it interviews you about your business, customers and how you talk, and saves it as .agents/product-marketing.md in your folder. Every other skill reads that file first, so you stop explaining your business every time.

Fifty-three skills is a lot to load everywhere, so I'd put them in one marketing folder only (no -g). Claude Code loads a short description of every skill into each conversation, and when there are too many it starts cutting descriptions, which makes it worse at picking the right one.

  1. Install them in your marketing folder

    Run this from inside ~/marketing. --skill '*' means all of them; -a claude-code makes sure they land where Claude Code reads them (its README warns they can end up in a folder Claude Code doesn't read otherwise).

    bashInstall all Marketing Skills (this folder only)
    cd ~/marketing
    npx skills add coreyhaines31/marketingskills --skill '*' -a claude-code
    bashJust see the list first (installs nothing)
    npx skills add coreyhaines31/marketingskills --list
  2. Set up your business once

    Start claude in ~/marketing and run this. With no website code in the folder, pick “start from scratch” and it walks through it with you, one section at a time.

    PromptInside Claude Code
    /product-marketing
    Start from scratch. Ask me one section at a time about my business, my services, my customers and how I talk. Use only what I tell you.
  3. Use them

    Ask for the job in plain English and Claude picks the skill that fits, or call one by name: /copywriting, /seo-audit, /emails, /ads, /cro. Some skills point to paid tools for data; the README lists four sponsored partners and says they don't change what the core skills recommend. You don't need any of them to start.

Check they're all there

bashIn your terminal
npx skills ls -g      # the four global ones
cd ~/marketing
npx skills ls         # the Marketing Skills in this folder

Then start claude in ~/marketing and type /skills: you should see all five. Claude Code picks up new skills without a restart. The one exception: if ~/.claude/skills didn't exist when your session started, type /reload-skills once.

First test: a made-up paragraph through Humanizer (nothing gets sent)

This runs on your Claude plan with nothing posted, sent or published. Paste it into Claude Code:

PromptPrompt: first test
/humanizer

Example (made up): In today's fast-paced world, your roof is more than just a roof. It's a testament to your home's resilience. At Example Roofing Co., we don't just install roofs; we deliver peace of mind, quality, and excellence. Our team is passionate about elevating every homeowner's experience. Let that sink in.

Good: it should flag the “more than just a roof” and “don't just install roofs” lines, the “testament” and “passionate about elevating” filler, the “peace of mind, quality, and excellence” list of three and the “Let that sink in.” closer, and the rewrite is shorter and plain. It may ask you for a real fact to put in place of the fluff (how long you've been in business, what you actually install). That's it refusing to make one up. Bad: Claude rewrites it without listing what it changed. Then the skill isn't loading: type /skills and check humanizer is there.

Then try /grill-me on something small you're actually planning. It costs you a few minutes of answering questions, and it's the quickest way to see what it does.

Real use: prompts for real jobs

Prompt1. A service page, start to finish
/grill-me
I want a new page on my website for <the service>. Grill me on who it's for, what it should get them to do, and what proof I actually have. Don't write anything yet.

(after the grilling)
/copywriting
Write the page from what we just settled. Use only facts I gave you: no made-up reviews, numbers or guarantees, and no promises about Google rankings. Then run /humanizer on it and show me both versions.
Prompt2. An SEO check of your homepage
/seo-audit
Check <your homepage URL>. Tell me the five fixes that matter most, in plain English, each with who would do it (me, or my web person). Don't change anything, and don't promise rankings.
Prompt3. Follow-up emails after an estimate
/emails
Draft three short follow-up emails for a homeowner who got an estimate but hasn't decided. Sound like me (see .agents/product-marketing.md). No pressure tactics, no fake deadlines. Show me the drafts only; don't send anything.
Prompt4. Make it a skill once it works
/skill-creator
Turn what we just did for the follow-up emails into a skill called estimate-follow-up in ~/.claude/skills. Show me the SKILL.md before you save it.
Prompt5. A long working session
/caveman
We're going through my whole services list today. Keep answers short until I say stop caveman.

Keep them updated (and remove one)

Skills installed with the Skills CLI don't update themselves. Check now and then:

bashCheck, update, remove
npx skills check                    # anything to update?
npx skills update -g                # update your global skills
cd ~/marketing && npx skills update -p   # update the Marketing Skills
npx skills remove --global caveman  # take one off (any skill name works)

The Skills CLI sends anonymous usage data by default. Set either of these to 1 to switch it off:

DISABLE_TELEMETRY

Turns off the Skills CLI's anonymous usage data

Where: Your terminal, before npx skills (e.g. in your shell profile)
DO_NOT_TRACK

Does the same thing; either one works

Where: Your terminal, before npx skills

What it costs

Checked 2026-10-31 on claude.com/pricing and each repo. Prices change: check before you buy.
PiecePlan or licensePrice
HumanizerOpen source (MIT, blader/humanizer)Free
Skill CreatorOpen source (Apache 2.0, anthropics/skills)Free
Grill Me + grillingOpen source (MIT, mattpocock/skills)Free
Caveman skillOpen source (Apache 2.0, JuliusBrussee/caveman)Free
Marketing SkillsOpen source (MIT, coreyhaines31/marketingskills)Free
Skills CLI and Node.jsOpen sourceFree
Claude CodeClaude Pro (the free Claude plan doesn't include Claude Code)$20 a month billed monthly, or $200 a year billed up front
Claude CodeClaude Max$100 a month
Claude CodeClaude Ultra$200 a month

The real cost is your plan's usage limit. Every skill runs on it, and a long Grill Me session or a Skill Creator test run uses a good chunk. That's where Caveman earns its spot. And watch one thing: the skills are free, but a skill can point Claude at a paid tool (an SEO data service, an ad account). If one asks for a key or an account, stop and read why before you go on.

When it breaks

npx: command not found or node: command not found
Node.js isn't installed, or your terminal was open before you installed it. Install the LTS from nodejs.org and open a new terminal window.
A skill doesn't show up in /skills
It was installed without -a claude-code (so it landed where Claude Code doesn't look), or for one project in a different folder. Run npx skills ls -g and npx skills ls, then reinstall with -a claude-code. If ~/.claude/skills didn't exist when the session started, type /reload-skills.
/grill-me runs but doesn't really grill you
The grilling skill is missing; grill-me only hands off to it. Install both: npx skills add mattpocock/skills --skill grill-me --skill grilling -g -a claude-code.
Claude never uses Grill Me on its own
That's on purpose: it's set to run only when you type /grill-me.
Every skill shows up twice
You installed the same set two ways (the plugin and the Skills CLI). Keep one: npx skills remove --global <name> takes off the CLI copy.
Plugin skills have long names like /humanizer:humanizer
Normal for plugins: their skills get the plugin's name in front. The Skills CLI installs in this guide give you the short names.
The marketing skills keep asking about your business
Run /product-marketing once and start claude in the same folder each time; the other skills read .agents/product-marketing.md from there.
Claude picks the wrong skill, or ignores one you installed
Too many skills can crowd each other out: Claude Code trims descriptions to fit. Keep the 53 marketing skills in one folder (no -g), run /doctor to see what the skill list costs, or call the skill by name.
Caveman's answers are too short to follow
Say “stop caveman” or “normal mode”. Turn it back on with /caveman when you're doing work you already know.
Caveman turned on when you didn't ask
Its description wakes it on phrases like “be brief” or “less tokens”. Say “stop caveman”; it confirms in one line.
Humanizer's rewrite still gets flagged by an AI detector
That's not what it's for: its README says it edits for readers and detectors still flag most of its output.
Humanizer asks you for a detail instead of finishing
Working as designed: it won't invent names, numbers or dates. Give it the real fact, or tell it to cut the sentence.
Skill Creator wants to run tests or Python scripts
That's its testing loop. Tell it to skip the formal tests and just write the skill with you.
Claude Code asks permission before running npx
Normal: Claude Code asks before it runs most commands. Read it and say yes only if it's the command you expected.
Claude says you hit your usage limit
Wait for the reset shown, or look at a bigger plan. For long sessions, /caveman stretches it a bit.

That's the five

Five free skills, five commands, and now you know which one to grab: Grill Me before you build, Marketing Skills to draft, Humanizer before it goes out, Skill Creator once you've done it twice, and Caveman when your limit's running low.

Checked on Oct 31, 2026 against

Every claim about a third-party tool in this guide (plans, prices, menu paths, commands, limits) was checked against these official pages on Oct 31, 2026. These screens change often: if something looks different, trust the page over this guide.

Rather skip the setup?

Want help setting this up?

Receipts Group builds these systems. Thirty minutes with Eric tells you which piece is worth building first, or that none of them are. The guides stay free either way.

Keep going

more free guides