The Claude Code
Skills Blueprint

Think of it as a set of permanent instructions baked into Claude's behaviour for that project. You write the rules once. Claude follows them every time.

Skills can tell Claude how to write, how to review code, which patterns to follow, which words to avoid, how to handle specific tasks — anything you'd normally have to type out as a prompt, you can make permanent with a skill file.

One skill file. Zero repeated prompting.

• 1

  You create a skill file

  A plain markdown file at .claude/skills/your-skill.md with instructions written in plain English.

• 2

  Claude loads it automatically

  Every time you open Claude Code in that project, it reads every skill file in the .claude/skills/ folder.

• 3

  Claude applies it silently

  No manual prompting. The skill runs in the background on every output — writing, code, emails, anything.

• 4

  You get better output every time

  The skill's rules apply consistently. Your defaults are now better. Permanently.

• 1

  Open your project folder

  Navigate to the root of any project where you use Claude Code. This is where the skill will live.

• 2

  Create the skills folder

  Run this in your terminal: mkdir -p .claude/skills — this creates the folder Claude looks for automatically.

• 3

  Create the skill file

  Create a new file: .claude/skills/humanizer.md — open it in any text editor.

• 4

  Paste the skill content

  Copy the full skill file from Section 04 below and paste it into the file. Save it.

• 5

  Open Claude Code

  Start a new Claude Code session in that project. The skill loads automatically. No configuration needed.

• 6

  Activate it

  Type: "Activate the humanizer skill for this conversation." Claude confirms and applies it to every output from that point on.

This is the complete skill. Copy everything below and paste it into your .claude/skills/humanizer.md file. That's all you need to do.

---
name: humanizer
version: 2.2.0
description: |
  Remove signs of AI-generated writing from text.
  Use when editing or reviewing text to make it sound
  more natural and human-written. Detects and fixes:
  inflated symbolism, promotional language, superficial
  analyses, vague attributions, em dash overuse, rule
  of three, AI vocabulary words, negative parallelisms,
  and excessive conjunctive phrases.
allowed-tools:
  - Read
  - Write
  - Edit
---

# Humanizer: Remove AI Writing Patterns

You are a writing editor. When this skill is active,
silently scan every output before delivering it.
Identify AI patterns. Rewrite them. Preserve meaning.
Add soul. Then run the final audit below.

## WORDS TO KILL ON SIGHT

delve, tapestry, pivotal, underscore, leverage,
utilize, vibrant, nestled, groundbreaking, testament,
crucial, foster, garner, intricate, landscape (abstract),
showcase, align with, enhance, Additionally, enduring,
highlight (verb), interplay, valuable, revolutionary,
in today's landscape, cutting-edge, game-changer,
genuinely, straightforward, key (as adjective)

## STRUCTURAL PATTERNS TO REMOVE

→ Em dash overuse — replace with commas or full stops
→ Rule of three padding → say it once, clearly
→ Emoji headers → remove entirely
→ Bold colon bullet lists → rewrite as prose
→ Generic positive endings → end with a specific fact
→ Vague attributions (experts say) → name source or cut
→ Excessive hedging → say what you mean directly
→ Sycophantic openers (Great question!) → cut entirely
→ Not only...but... constructions → simplify
→ Copula avoidance (serves as / stands as) → use "is"
→ Knowledge cutoff disclaimers → remove
→ False ranges (from X to Y) → rewrite directly

## HOW TO ADD SOUL

Have opinions. Don't just report — react.
Vary sentence length. Short. Then longer ones.
Use "I" when it fits. First person is honest.
Be specific about feelings, not vague.
Acknowledge complexity and mixed feelings.
Let some mess in. Perfect structure feels algorithmic.

## FINAL AUDIT — ALWAYS RUN THIS LAST

Before delivering any output, ask yourself:
"What makes this obviously AI-generated?"
Answer briefly. Then fix what remains.
Only then deliver the final version.

These are the most common signs of AI-generated writing. The humanizer kills all of them automatically.

Here's what the difference looks like in practice:

The Humanizer is one skill. These three GitHub repositories contain hundreds more — built by official engineering teams at the biggest companies in tech.

• Awesome Agent Skills — VoltAgent

  383+ skills from Anthropic, Google, Vercel, Stripe, Cloudflare, Microsoft, Hugging Face, Trail of Bits, and the community. The most comprehensive collection available.

  ★ 8,200 github.com →

• Claude Code Templates — aitmpl.com

  Ready-to-use skills, agents, commands, hooks, and MCP server configs. Install any component with a single npx command.

  ★ Free aitmpl.com →

• Claude Skills Vault — georgekhananaev

  17 curated skills for senior full-stack workflows — code review, architecture, testing, Next.js, FastAPI, and document handling.

  ★ 5 github.com →