⚡ Humanizer Content Transformer Engine

Humanizer transforms dense, AI-generated technical documentation into clean, conversational developer blog posts. It strips away robotic fluff and corporate jargon while keeping all your code blocks, command lines, and links completely intact.

---

🛠️ Installation & Setup

1. Skill Installation Options

Option A: Skills CLI Installation (Recommended)

npx skills add blader/humanizer --global

Option B: PowerShell Direct Skill Download

Invoke-WebRequest -Uri "https://raw.githubusercontent.com/blader/humanizer/main/SKILL.md" -OutFile "SKILL.md"

Option C: Claude Code Plugin Installation

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

---

2. Model Download & Registration Options

Option A: Noema 2B GGUF Model (Recommended)

Run this single PowerShell command to install dependencies, create the Modelfile, and register noema2b in Ollama:

pip install urllib3 ; echo "FROM hf.co/NoemaAI-labs/Noema-2B-GGUF`nPARAMETER temperature 0.7`nPARAMETER presence_penalty 1.5" > Modelfile ; ollama create noema2b -f Modelfile

Option B: Llama 3.2 3B Model

Alternatively, pull and use llama3.2:3b via Ollama:

ollama pull llama3.2:3b

---

3. Run Command

Execute the main Python engine to convert your input document:

python main.py

The transformed, human-readable blog post or developer conversation will be created inside outputs/outputs.md along with exact recorded generation time.

---

💻 Tech Stack

• Core Logic: Python 3.12 (Native AST Markdown Parser)
• Primary AI Backend: Ollama (noema2b:latest / llama3.2:3b)
• Input Document: Markdown (inputs/input_doc.md)
• Output Result: Markdown (outputs/outputs.md)

---

📁 Repository Structure

humanizer/
├── inputs/
│   └── input_doc.md
├── Modelfile
├── main.py
└── README.md

---

💡 5 Real-World Use Cases

1. Open-Source Release Notes: Clean up AI-drafted CHANGELOGs so developers get direct updates without corporate filler.
2. Technical Developer Blogs: Turn dry architecture specifications into engaging tutorials for engineering teams.
3. Repository READMEs: Strip robotic phrasing from project landing pages to boost maintainer credibility.
4. API Quickstarts: Rewrite formal endpoint guides into beginner-friendly walkthroughs.