# What Is the Current Version of the Humanizer Skill? A Complete Guide

> Discover the current version of the Humanizer skill, 2.11.2. This guide provides a complete look at the blader/humanizer repository and its latest updates.

- Repository: [Siqi Chen/humanizer](https://github.com/blader/humanizer)
- Tags: getting-started
- Published: 2026-09-05

---

**The current version of the Humanizer skill is 2.11.2**, as defined in the `metadata.version` field of the [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) file in the blader/humanizer repository.

The Humanizer skill transforms AI-generated text into natural, human-readable content. Understanding the **current version of the Humanizer skill** is essential for compatibility checks, debugging, and ensuring you are using the latest pattern definitions. This guide explains where the version 2.11.2 is defined and how to access it across different contexts.

## Where to Find the Humanizer Skill Version

The version identifier resides in specific metadata files that serve as the single source of truth for the entire package.

### Checking SKILL.md for the Source of Truth

In [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) at the repository root, the version is explicitly declared within the metadata block. According to the blader/humanizer source code, line 10 contains the authoritative version string:

```yaml
metadata:
  version: "2.11.2"

```

This YAML frontmatter serves as the primary reference for all other files in the repository. The `metadata.version` field follows semantic versioning standards, making it easy to track major, minor, and patch releases.

### Cross-Referencing Other Files

While [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) contains the canonical version, other files reference this number for consistency:

- [`.claude-plugin/plugin.json`](https://github.com/blader/humanizer/blob/main/.claude-plugin/plugin.json) – The Claude plugin manifest mirrors the version for integration purposes.
- [`README.md`](https://github.com/blader/humanizer/blob/main/README.md) – Documentation files display the version for user reference.
- [`scripts/validate-package.py`](https://github.com/blader/humanizer/blob/main/scripts/validate-package.py) – This validation script ensures version consistency across all package files.

## How to Access the Humanizer Skill Version Programmatically

Developers often need to extract the version number for automated workflows, CI/CD pipelines, or plugin development.

### Node.js YAML Parsing

To read the **current version of the Humanizer skill** using Node.js, parse the YAML frontmatter from [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md):

```javascript
const fs = require('fs');
const yaml = require('js-yaml');

const skill = yaml.load(fs.readFileSync('SKILL.md', 'utf8'));
console.log('Humanizer version:', skill.metadata.version); // → 2.11.2

```

This approach loads the entire skill metadata object, allowing you to access additional configuration values alongside the version string.

### Shell Script Extraction

For bash-based automation or deployment scripts, extract the version using grep and awk:

```bash
VERSION=$(grep -E '^  version:' SKILL.md | awk '{print $2}' | tr -d '"')
echo "Humanizer skill version: $VERSION"  # → Humanizer skill version: 2.11.2

```

This command specifically targets the indented version field within the YAML metadata block, stripping quotes to return a clean string.

### Plugin Manifest Configuration

When developing Claude plugins that depend on the Humanizer skill, reference the version in your [`plugin.json`](https://github.com/blader/humanizer/blob/main/plugin.json):

```json
{
  "name": "humanizer",
  "version": "2.11.2",
  "description": "Rewrite AI‑sounding text so it reads naturally..."
}

```

Keeping this manifest synchronized with [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) ensures compatibility with the Claude plugin ecosystem.

## Version Validation in the Repository

The blader/humanizer repository includes automated safeguards to prevent version drift. The [`scripts/validate-package.py`](https://github.com/blader/humanizer/blob/main/scripts/validate-package.py) file contains validation logic that checks consistency of metadata—including the version number—across all package files. This ensures that [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md), [`README.md`](https://github.com/blader/humanizer/blob/main/README.md), and [`.claude-plugin/plugin.json`](https://github.com/blader/humanizer/blob/main/.claude-plugin/plugin.json) all reference the same version 2.11.2.

## Summary

- The **current version of the Humanizer skill is 2.11.2**, defined in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) at line 10 within the `metadata.version` field.
- Access the version programmatically using Node.js YAML parsers, shell scripts with grep/awk, or direct file reading.
- Key repository files including [`.claude-plugin/plugin.json`](https://github.com/blader/humanizer/blob/main/.claude-plugin/plugin.json) and [`README.md`](https://github.com/blader/humanizer/blob/main/README.md) mirror this version for different contexts.
- The [`scripts/validate-package.py`](https://github.com/blader/humanizer/blob/main/scripts/validate-package.py) validator ensures version consistency across the entire codebase.

## Frequently Asked Questions

### What is the current version of the Humanizer skill?

The current version is **2.11.2**. This semantic version is defined in the `metadata.version` field of [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) in the blader/humanizer repository, representing the latest stable release of the text humanization patterns and configurations.

### Where is the Humanizer skill version defined?

The canonical version definition lives in [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) at the repository root. Specifically, line 10 contains the `metadata.version` field within the YAML frontmatter. This file serves as the single source of truth, while other files like [`.claude-plugin/plugin.json`](https://github.com/blader/humanizer/blob/main/.claude-plugin/plugin.json) and [`README.md`](https://github.com/blader/humanizer/blob/main/README.md) reference this value.

### How can I verify the Humanizer skill version locally?

You can verify the version by reading the `metadata.version` field from [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md) using any YAML parser, or by running a shell command like `grep -E '^  version:' SKILL.md | awk '{print $2}' | tr -d '"'`. The repository also includes [`scripts/validate-package.py`](https://github.com/blader/humanizer/blob/main/scripts/validate-package.py) to programmatically check consistency across all files.

### Is the version number consistent across all repository files?

Yes, the version number is synchronized across files. The [`scripts/validate-package.py`](https://github.com/blader/humanizer/blob/main/scripts/validate-package.py) validation script ensures that [`SKILL.md`](https://github.com/blader/humanizer/blob/main/SKILL.md), [`.claude-plugin/plugin.json`](https://github.com/blader/humanizer/blob/main/.claude-plugin/plugin.json), and documentation files all reference the same version 2.11.2, preventing configuration drift between the skill definition and its integrations.