How to Install the Humanizer Skill Globally
Run npx skills add blader/humanizer --global to install the Humanizer skill globally, making the /humanizer command available across all agents on your machine.
The Humanizer skill from the blader/humanizer repository provides 35 text rewriting patterns to humanize AI-generated content. Installing it globally ensures the skill persists across all your agents and projects, eliminating the need to reinstall per workspace. This guide covers the three installation methods supported by the source code, from the recommended CLI approach to manual setup for Claude Desktop.
Install Globally Using the Skills CLI
The Skills CLI provides the recommended path for global installation. This method registers the skill in the global skills store rather than your current project's local skills/ folder.
Run the following command in your terminal:
npx skills add blader/humanizer --global
The command pulls the skill definition from the GitHub repository and stores the SKILL.md file in the global directory used by the Skills CLI. Once installed, you can invoke the skill anywhere using the /humanizer command.
Restrict to Specific Agents
If you maintain multiple agents and want to control which ones access the Humanizer skill, pass the --agent flag:
# Install for a specific agent only
npx skills add blader/humanizer --agent my-agent
# Install for all agents explicitly
npx skills add blader/humanizer --agent '*'
After installation, reload your agents to ensure they pick up the new skill registration.
Install via Claude Code Marketplace
For Claude Code version 2.1.142 and above, you can install the skill through the built-in marketplace interface. This method handles registration automatically without requiring manual file placement.
Execute these commands within Claude Code:
/plugin marketplace add blader/humanizer
/plugin install humanizer@humanizer
This registers the skill under the /humanizer:humanizer command namespace. According to the README.md in the repository, this approach validates the skill metadata immediately upon installation.
Manual Installation for Claude Desktop
If you use Claude Desktop or cannot access the Skills CLI, perform a manual installation by placing the source file directly in your agent's skill directory.
Follow these steps:
- Download the
blader/humanizerrepository as a ZIP file and extract it - Locate the
SKILL.mdfile—this contains the actual skill definition and 35 rewriting patterns - Copy the file to your agent's skill directory:
cp SKILL.md ~/.claude/skills/humanizer/
- Restart Claude Desktop or reload the agent to activate the skill
This method bypasses the CLI tooling but requires you to manually update the file when the repository releases new versions.
How Global Installation Works
The installation process ultimately performs the same core action across all three methods: placing the SKILL.md file where the agent loader expects it.
Skill Validation and Loading
When you run the install command, the agent loader reads the SKILL.md metadata to verify compatibility. Specifically, it checks the metadata.version field to ensure the skill matches your agent's API requirements. The loader then indexes the skill's 35 rewriting patterns, making them available for execution whenever you invoke /humanizer.
Key source files involved in this process include:
SKILL.md– The actual skill definition containing the 35 rewriting patterns and metadataREADME.md– User-facing documentation specifying the global installation commands.claude-plugin/plugin.json– Describes the Claude plugin configuration and points the loader toSKILL.md.claude-plugin/marketplace.json– Enables discovery and installation via the Claude marketplace
Summary
- Run
npx skills add blader/humanizer --globalfor the fastest, CLI-based installation across all agents - Use
--agent <name>to restrict the skill to specific agents rather than making it truly global - Claude Code 2.1.142+ users can run
/plugin install humanizer@humanizerfor integrated marketplace installation - Claude Desktop users must manually copy
SKILL.mdto~/.claude/skills/humanizer/if CLI access is unavailable - All methods place the
SKILL.mdsource file in the agent's load path and validate themetadata.versionfield before activation
Frequently Asked Questions
What is the fastest way to install the Humanizer skill globally?
Run npx skills add blader/humanizer --global in your terminal. This single command downloads the skill from the blader/humanizer repository and registers it in the global skills store, immediately making the /humanizer command available to all supported agents on your machine.
Can I restrict the Humanizer skill to specific agents after global installation?
Yes. Append the --agent flag followed by the agent name when running the install command. For example, npx skills add blader/humanizer --agent claude-code installs the skill only for Claude Code, leaving other agents unaffected. Use --agent '*' to explicitly target all agents if you change your configuration later.
Why does the installation require the SKILL.md file specifically?
The SKILL.md file serves as the source of truth for the skill. It contains the 35 rewriting patterns, command definitions, and metadata including the version number. The agent loader parses this file to validate compatibility and index the available commands. Without this file in the expected directory, the agent cannot recognize or execute the /humanizer command.
How do I verify that the global installation worked correctly?
Open any supported agent and type /humanizer followed by a text rewriting request. If the skill responds with humanized output, the installation succeeded. If the agent reports "command not found," check that SKILL.md exists in your global skills directory and that your agent version meets the requirements specified in the skill's metadata.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →