# How to Install Humanizer Using the Skills CLI: Complete Setup Guide > Install Humanizer with the Skills CLI. Follow our guide to set up blader/humanizer globally or locally using npx skills add blader/humanizer. - Repository: [Siqi Chen/humanizer](https://github.com/blader/humanizer) - Tags: how-to-guide - Published: 2026-09-09 --- **You can install Humanizer globally or locally using `npx skills add blader/humanizer`, with optional flags like `--global` or `--agent ` to control scope and target agents.** The **Skills CLI** (`npx skills`) is the official package manager for Markdown-based skills in the AI ecosystem. According to the `blader/humanizer` source code, Humanizer is delivered as a pure Markdown skill defined in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md), making installation lightweight and portable across different AI platforms without requiring any build steps or compiled binaries. ## Understanding the Skills CLI Installation Process The Skills CLI handles the entire installation lifecycle for Humanizer. When you invoke `npx skills add blader/humanizer`, the CLI fetches the repository from GitHub, copies the skill definition into the appropriate directory, and updates the agent's manifest to register the `/humanizer` slash command. The core skill definition lives in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) at the repository root, which contains YAML metadata including the current version (3.0.0) and the full transformation prompt. Because Humanizer is pure Markdown, the CLI simply copies this file into the skills directory rather than compiling code or installing dependencies. ## Step-by-Step Installation Methods Humanizer supports three installation scopes depending on your workflow needs. ### Global Installation (System-Wide) For a workstation-wide setup that makes Humanizer available to every project on your machine, use the `--global` flag: ```bash npx skills add blader/humanizer --global ``` This command installs the skill in the global Skills registry, as documented in [`README.md`](https://github.com/blader/humanizer/blob/main/README.md) lines 9-13. After installation, reload your agents to recognize the new skill. ### Local Installation (Project-Specific) To restrict Humanizer to a single project directory, omit the `--global` flag: ```bash npx skills add blader/humanizer ``` This registers the skill only for the current folder, creating a local dependency that travels with your project repository. ### Agent-Specific Installation You can further control which AI agents receive the skill by specifying the `--agent` flag: ```bash npx skills add blader/humanizer --agent claude ``` Use `--agent '*'` to install across all supported agents simultaneously. After running any installation command, you must reload the target agents so they pick up the new skill from the updated manifest. ## Alternative Installation via Claude Code Marketplace Claude Code users can install Humanizer through the built-in marketplace interface without using the CLI directly: ```bash /plugin marketplace add blader/humanizer /plugin install humanizer@humanizer ``` This method leverages the [`.claude-plugin/plugin.json`](https://github.com/blader/humanizer/blob/main/.claude-plugin/plugin.json) file, which describes the Claude plugin entry point pointing to [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md). The marketplace approach is ideal for users who prefer GUI-based workflows over command-line installation. ## How the Skills CLI Works Under the Hood The Skills CLI installation process is straightforward because Humanizer contains no compiled components. The tool performs the following operations based on the repository structure: - **Fetches metadata**: Reads [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) to extract version 3.0.0 and prompt definitions - ** Validates package**: Optionally runs [`scripts/validate-package.py`](https://github.com/blader/humanizer/blob/main/scripts/validate-package.py) to check metadata consistency and pattern tables before installation - **Copies files**: Places [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) into the appropriate skill directory - **Updates manifests**: Modifies agent configuration files to register the `/humanizer` slash command - **Configures agents**: Uses [`agents/openai.yaml`](https://github.com/blader/humanizer/blob/main/agents/openai.yaml) to supply display names and default prompts for OpenAI-compatible agents Because the behavior is defined entirely by the prompt in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md), there is no build step, dependency resolution, or binary compilation required. This design makes the skill installation nearly instantaneous and compatible across different AI platforms including Claude, GPT, and other agents that understand the Skills format. ## Summary - **Install globally** with `npx skills add blader/humanizer --global` to use Humanizer across all projects on your machine - **Install locally** by omitting `--global` to restrict the skill to a specific project directory - **Target specific agents** using the `--agent` flag or install for all agents with `--agent '*'` - **No build required** because Humanizer is pure Markdown stored in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) and processed by the Skills CLI - **Reload agents** after installation to activate the `/humanizer` slash command - **Alternative path** exists for Claude Code users via `/plugin marketplace add blader/humanizer` ## Frequently Asked Questions ### What is the difference between global and local installation? Global installation places Humanizer in the system-wide Skills registry, making it available to every project and agent on your machine without requiring reinstallation. Local installation restricts the skill to the current directory only, which is useful for maintaining specific versions per project or avoiding conflicts between different agent configurations. ### Why doesn't Humanizer require a build step? Humanizer is implemented as a **Markdown-based skill** where the transformation logic resides entirely in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) as a structured prompt. The Skills CLI simply copies this file into the appropriate directory and updates agent manifests, unlike traditional packages that require compilation, dependency installation, or binary linking. This architecture keeps the installation lightweight and portable. ### How do I verify that Humanizer is installed correctly? After installing with `npx skills add blader/humanizer`, reload your agent and type `/humanizer` to verify the slash command appears in your interface. You can also check the local or global skills directory (depending on your installation mode) to confirm that [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) has been copied into the `blader/humanizer` folder structure. ### Can I use Humanizer with agents other than Claude? Yes. The repository includes [`agents/openai.yaml`](https://github.com/blader/humanizer/blob/main/agents/openai.yaml), which supplies the display name and default prompt for OpenAI-compatible agents. When installing, use `npx skills add blader/humanizer --agent '*'` to register the skill across all supported agents, or specify individual agent names to target specific platforms like GPT-4, Claude, or custom agent implementations that understand the Skills format.