Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
{
"name": "humanizer-dev",
"description": "Development marketplace for Humanizer skills library",
"owner": {
"name": "Humanizer Contributors",
"email": "info@humanizer.dev"
},
"plugins": [
{
"name": "humanizer",
"description": "Skills library for humanizing code and improving readability",
"version": "2.2.0",
"source": "./",
"author": {
Comment on lines +12 to +14
"name": "Humanizer Contributors",
"email": "info@humanizer.dev"
}
}
]
12 changes: 12 additions & 0 deletions .claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
{
"name": "humanizer",
"description": "Skills library for humanizing code and improving readability",
"version": "2.2.0",
Comment on lines +2 to +4
"author": {
"name": "Humanizer Contributors",
"email": "info@humanizer.dev"
},
"homepage": "https://github.com/blader/humanizer",
"repository": "https://github.com/blader/humanizer",
"license": "MIT",
"keywords": ["skills", "humanizer", "readability", "code-quality", "best-practices"]
17 changes: 17 additions & 0 deletions .cursor-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
{
"name": "humanizer",
"displayName": "Humanizer",
"description": "Skills library for humanizing code and improving readability",
"version": "2.2.0",
Comment on lines +3 to +5
"author": {
"name": "Humanizer Contributors",
"email": "info@humanizer.dev"
},
"homepage": "https://github.com/blader/humanizer",
"repository": "https://github.com/blader/humanizer",
"license": "MIT",
"keywords": ["skills", "humanizer", "readability", "code-quality", "best-practices"],
"skills": "./skills/",
"agents": "./agents/",
"commands": "./commands/",
"hooks": "./hooks/hooks-cursor.json"
Comment on lines +14 to +17
21 changes: 15 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,20 +4,29 @@ A Claude Code skill that removes signs of AI-generated writing from text, making

## Installation

### Recommended (clone directly into Claude Code skills directory)
### Claude Plugin Marketplace (Recommended)

Register the marketplace and install:

```bash
claude plugin marketplace add https://github.com/blader/humanizer
claude plugin install humanizer-dev:humanizer
```

### Manual Install (Git Clone)

Clone directly into Claude skills directory:

```bash
mkdir -p ~/.claude/skills
git clone https://github.com/blader/humanizer.git ~/.claude/skills/humanizer
```

### Manual install/update (only the skill file)

If you already have this repo cloned (or you downloaded `SKILL.md`), copy the skill file into Claude Code’s skills directory:
### Cursor

```bash
mkdir -p ~/.claude/skills/humanizer
cp SKILL.md ~/.claude/skills/humanizer/
mkdir -p ~/.cursor/skills
git clone https://github.com/blader/humanizer.git ~/.cursor/skills/humanizer
```

## Usage
Expand Down
43 changes: 18 additions & 25 deletions SKILL.md → skills/humanizer/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,6 @@
---
name: humanizer
version: 2.2.0
description: |
Remove signs of AI-generated writing from text. Use when editing or reviewing
text to make it sound more natural and human-written. Based on Wikipedia's
comprehensive "Signs of AI writing" guide. Detects and fixes patterns including:
inflated symbolism, promotional language, superficial -ing analyses, vague
attributions, em dash overuse, rule of three, AI vocabulary words, negative
parallelisms, and excessive conjunctive phrases.
description: "Remove signs of AI-generated writing from text to make it sound more natural and human. Use when editing or reviewing content to eliminate AI patterns: inflated symbolism, promotional language, vague attributions, overused em dashes, AI vocabulary, and excessive hedging. Adds voice and personality to sterile writing."
allowed-tools:
- Read
- Write
Expand All @@ -19,18 +12,18 @@ allowed-tools:

# Humanizer: Remove AI Writing Patterns

You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This guide is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.
You are a writing editor that identifies and removes signs of AI-generated text to make writing sound more natural and human. This skill is based on Wikipedia's "Signs of AI writing" page, maintained by WikiProject AI Cleanup.

## Your Task

When given text to humanize:
When editing text to humanize it:

1. **Identify AI patterns** - Scan for the patterns listed below
2. **Rewrite problematic sections** - Replace AI-isms with natural alternatives
3. **Preserve meaning** - Keep the core message intact
4. **Maintain voice** - Match the intended tone (formal, casual, technical, etc.)
5. **Add soul** - Don't just remove bad patterns; inject actual personality
6. **Do a final anti-AI pass** - Prompt: "What makes the below so obviously AI generated?" Answer briefly with remaining tells, then prompt: "Now make it not obviously AI generated." and revise
1. **Identify AI patterns** Scan for the patterns listed below
2. **Rewrite sections** Replace AI-isms with natural alternatives
3. **Preserve meaning** Keep the core message intact
4. **Maintain voice** Match the intended tone (formal, casual, technical, etc.)
5. **Add personality** Don't just remove bad patterns; inject actual human voice
6. **Final audit** — Ask yourself: "What makes this obviously AI generated?" Answer briefly with remaining tells, then revise

---

Expand Down Expand Up @@ -393,27 +386,27 @@ Avoiding AI patterns is only half the job. Sterile, voiceless writing is just as
## Process

1. Read the input text carefully
2. Identify all instances of the patterns above
3. Rewrite each problematic section
4. Ensure the revised text:
2. Identify instances of the patterns listed above
3. Rewrite each problematic section for clarity and naturalness
4. Verify the revised text:
- Sounds natural when read aloud
- Varies sentence structure naturally
- Uses specific details over vague claims
- Maintains appropriate tone for context
- Uses simple constructions (is/are/has) where appropriate
5. Present a draft humanized version
6. Prompt: "What makes the below so obviously AI generated?"
7. Answer briefly with the remaining tells (if any)
8. Prompt: "Now make it not obviously AI generated."
9. Present the final version (revised after the audit)
6. Self-audit: "What makes this obviously AI generated?"
7. Answer briefly with remaining tells (if any)
8. Revise again if needed
9. Present the final version

## Output Format

Provide:
1. Draft rewrite
2. "What makes the below so obviously AI generated?" (brief bullets)
2. Remaining AI tells (brief bullets, if any)
3. Final rewrite
4. A brief summary of changes made (optional, if helpful)
4. Summary of key changes (optional)

---

Expand Down
Loading