Home›Articles›Humanizer tutorial: install blader/humanizer and edit text step by step

Articles

Humanizer tutorial: install blader/humanizer and edit text step by step

Published October 16, 2026

On this page

Humanizer, maintained by blader on GitHub, is an open-source editing skill for AI assistants. It asks an assistant to make prose less formulaic while preserving its meaning. You need an assistant that supports skills to use it; opening the GitHub page alone does not give you a text editor.

The project explicitly says that passing AI detectors is not its goal. Use it to review wording and readability, with no promised Turnitin score. The walkthrough below starts with Claude’s website; the command-line alternatives come afterwards.

What Humanizer changes

Its editing instructions look for repetitive sentence structures, inflated claims, stock expressions and chat-style filler. They also ask the assistant to preserve supported facts and check its own rewrite. These are editing rules, not a test of who wrote a passage.

Choose one short paragraph for your first attempt. Comparing a small revision makes it easier to see whether an important qualification disappeared or a phrase became too informal.

Step 1: check that your Claude account can use skills

Sign in to Claude on a computer. Look for Customize → Skills. In Settings → Capabilities, enable Code execution and file creation if it is disabled. Anthropic says skills need this environment.

If your organisation has disabled custom skills, ask its administrator about access. Menu names may differ between versions; use Anthropic’s linked help page if your screen differs.

Step 2: download the project and prepare a skill folder

  1. Open the blader/humanizer GitHub repository linked under Sources.
  2. Choose Code → Download ZIP, then extract the downloaded archive.
  3. Create a new folder named humanizer. Copy SKILL.md and LICENSE from the extracted project into it. Keep the SKILL.md filename and its contents intact. This is the simple text-editing skill; the repository’s developer and test files are not needed for this walkthrough.

Step 3: compress that folder into a ZIP

Compress the humanizer folder itself into humanizer.zip. Open the ZIP to check its structure: it should contain a humanizer folder with SKILL.md directly inside, without an extra humanizer-main folder around it. The folder name matches the name declared in the skill.

humanizer.zip
└── humanizer/
    ├── SKILL.md
    └── LICENSE

Step 4: upload and enable Humanizer

A ZIP-structure error usually calls for checking Step 3. If uploading is unavailable, check your account’s capabilities and organisation policy before trying another archive.

  1. Return to Claude’s Customize → Skills page.
  2. Click +, choose Create skill, then Upload a skill.
  3. Select humanizer.zip and finish the upload. Turn on Humanizer in the skills list.

Step 5: start a chat and request one small edit

Open a new conversation. The website route uses a plain-language request: explicitly name the installed Humanizer skill, replace the brackets and paste one or two paragraphs. The prompt below is our suggested starting point.

Use the installed Humanizer skill to edit this text.
Audience: [who will read it]
Tone and language: [for example, clear academic English]
Preserve the argument, names, numbers and citations.
Do not add facts, experiences or sources. Flag missing information.
Return a revised version and explain the important changes.

Text:
[paste one or two paragraphs]

Step 6: supply your own writing sample if needed

If the first edit sounds unlike you, provide two or three paragraphs you wrote yourself. Ask the assistant to use them as a style reference and identify the separate passage to edit. Humanizer’s documented voice-matching approach uses the sample’s rhythm and wording.

For a practical prompt, add: ‘Use Sample A only as a style reference. Edit Text B. Do not copy facts or personal experiences from A into B.’ This makes your intended boundary explicit.

Step 7: compare the revision with your original

Read the two versions side by side. Check every number, quotation and citation, then check the strength of the claims. A sentence saying ‘may help’ should not quietly become ‘proves’. Keep subject-specific terms when they carry the correct meaning.

Here is an editorial illustration, not a recorded Humanizer result: ‘The booking page represents a significant advancement in the student experience’ can become ‘Students can book a room on the new page.’ The concrete sentence only works if that function is already established in the source text.

Step 8: save the version you actually accept

Keep your original draft and the accepted revision as separate files. For coursework, check whether your instructor permits AI editing and requires a declaration. Record what you used the tool for and keep your research notes.

Readable wording does not establish original authorship or repair an unsupported argument. If a passage still needs evidence, return to the research rather than accept a more confident sentence.

Alternative: install the Claude Code plugin

If you already use Claude Code, the project documents these two commands inside the Claude Code conversation, one at a time. The plugin route requires Claude Code 2.1.142 or later. After installation, its invocation is /humanizer:humanizer followed by your editing request.

/plugin marketplace add blader/humanizer
/plugin install humanizer@humanizer

Alternative: install a skill for Claude Code or Codex

For this route you need the chosen agent and a compatible Node.js/npm environment already installed. Open your computer’s terminal, choose just one installation command below, then follow the installer’s prompts. For Claude Code, use the first command; for Codex, use the second.

The --global flag selects your user-level installation. Omit it for a project-only installation. The listing command checks global skills. In a compatible agent, ask it to use the installed Humanizer skill; the project also documents /humanizer for skill invocation. Plugin installations use the different name shown above.

npx skills add blader/humanizer --global --agent claude-code
npx skills add blader/humanizer --global --agent codex

npx skills list --global

If it does not work, check the route you chose

The skill has an MIT licence. Your chosen assistant’s subscription, usage limits and data handling still apply. This article introduces the external GitHub project; it does not describe an integration with TurnCheckHK’s own editing service. Sources were checked on 16 October 2026.

  • Claude website: confirm the skill is enabled and explicitly name Humanizer in your request.
  • ZIP rejected: check the humanizer folder name and the SKILL.md file directly inside it.
  • Terminal reports npx missing or a Node version error: fix the local Node.js/npm setup using the current Skills CLI requirements.
  • Agent cannot find it: check that you installed for that agent and the intended global or project scope.
  • Results change a fact or sound unnatural: reject that edit, explain the exact issue and revise a shorter passage.

Official sources and further reading

Updated 16 October 2026. TurnCheckHK editorial guidance; not a Turnitin or university policy statement. Check the linked official guidance and your assignment instructions.

Check it yourself, before you submit

Choose the report you need and check current submission requirements. Use the result to review your work; your course rules and final assessment remain authoritative.