Installation Options for Humanizer: 5 Ways to Add the Skill to Your Agent

Humanizer can be installed via the Skills CLI (globally or locally), through Claude Code's marketplace plugin, manually in Claude Desktop, or by directly copying the SKILL.md file to your agent's skill folder.

The blader/humanizer repository provides multiple installation paths to accommodate different agent platforms and workflow preferences. Whether you need system-wide access across all projects or a project-specific setup, understanding these installation options for Humanizer ensures you can integrate the skill efficiently into your existing infrastructure.

Skills CLI Installation Methods

The Skills CLI provides the most flexible installation options, supporting both global system access and localized project configurations.

Global Installation

For a single, system-wide copy that works across every project on your machine, use the global flag. This places the skill in the global Skills cache, making it available to every agent regardless of project location.

npx skills add blader/humanizer --global

According to the repository source code, this method is ideal when you want consistent access to the /humanizer command without reinstalling per project.

Local Project Installation

When you lack permissions to modify the global cache or need project-specific isolation, omit the --global flag. This installs Humanizer only in the current project's skills/ folder.

npx skills add blader/humanizer

This approach keeps dependencies contained and version-controlled within your repository.

Agent-Specific Installation

To restrict the skill to particular agents while excluding others, append the --agent flag with a specific agent name or wildcard.

# Install for OpenAI agents only

npx skills add blader/humanizer --agent openai

# Install for all available agents

npx skills add blader/humanizer --agent '*'

After installation, you must reload the agents' skills to recognize the new capability. The repository's agents/openai.yaml file demonstrates how different agent configurations load the skill prompt.

Claude-Specific Installation Options

Humanizer provides dedicated integration paths for Claude environments through the .claude-plugin/plugin.json descriptor file.

Claude Code Marketplace Plugin

For Claude Code version 2.1.142 and above, use the built-in marketplace commands to fetch the repository automatically.

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

This method reads the plugin descriptor in .claude-plugin/plugin.json to handle dependencies automatically.

Claude Desktop Manual Installation

When working in Claude Desktop environments that don't use the marketplace, download the repository as a ZIP file and upload it through the Claude Desktop UI. The interface will place the SKILL.md file in the appropriate directory structure.

Manual Installation Method

The most low-level approach involves directly copying the SKILL.md file into your agent's skill folder. This works for any agent capable of reading plain Markdown skill files, regardless of platform support.

# Example path for Claude Desktop on macOS

cp SKILL.md ~/.claude/plugins/humanizer/SKILL.md

The repository's README.md contains detailed path specifications for various operating systems in its Installation section.

Using the Skill After Installation

Once installed through any method, invoke the skill using the /humanizer command or natural language prompts:

/humanizer
[paste your text here]

# Alternative natural language usage

Please humanize this text: [your text]

For Claude Code plugin installations, use the namespaced command /humanizer:humanizer instead.

Summary

• Global CLI install (--global) provides system-wide access for all projects and agents.
• Local CLI install restricts the skill to the current project's skills/ folder.
• Agent targeting (--agent) allows selective installation for specific AI agents like OpenAI or Claude.
• Claude marketplace integration works for Claude Code 2.1.142+ using /plugin commands.
• Manual file copy of SKILL.md works universally but requires knowledge of your agent's plugin directory structure.

Frequently Asked Questions

What is the difference between global and local installation?

Global installation places the skill in a system-wide cache accessible to all projects, while local installation confines it to the current project's skills/ folder. Choose global for consistent cross-project availability, or local when working in restricted environments or requiring project-specific versioning.

Which file does the agent actually load?

The agent loads SKILL.md, which contains the actual skill prompt and instructions. All installation methods ultimately place this file in a location discoverable by the agent, whether through the Skills CLI, Claude's marketplace, or manual copying.

Can I use Humanizer with agents other than Claude?

Yes. The repository includes agents/openai.yaml, demonstrating OpenAI-compatible agent configuration. Any agent that supports Markdown-based skill files or the Skills CLI framework can load Humanizer, though specific plugin commands like /plugin marketplace are Claude-specific.

How do I verify the installation was successful?

After installation, restart your agent or reload its skills, then type /humanizer (or /humanizer:humanizer for Claude plugin installs). If the skill is properly loaded, the agent will recognize the command and await your text input for humanization.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}