Skip to content
Merged
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
728 changes: 728 additions & 0 deletions .agent/skills/humanizer-pro/SKILL.md

Large diffs are not rendered by default.

719 changes: 585 additions & 134 deletions .agent/skills/humanizer/SKILL.md

Large diffs are not rendered by default.

724 changes: 695 additions & 29 deletions .agent/skills/humanizer/SKILL_PROFESSIONAL.md

Large diffs are not rendered by default.

727 changes: 727 additions & 0 deletions .vscode/HUMANIZER_PRO.md

Large diffs are not rendered by default.

14 changes: 8 additions & 6 deletions AGENTS.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
---
adapter_metadata:
skill_name: humanizer
skill_version: 2.2.0
last_synced: 2026-01-31
skill_version: 2.2.1
last_synced: 2026-02-06
source_path: SKILL.md
adapter_id: codex-cli
adapter_format: AGENTS.md
---

# Humanizer (Agents Manifest)
# Humanizer (agents manifest)

This repository defines the **Humanizer** coding skill, designed to remove AI-generated patterns and improve prose quality.

Expand All @@ -21,11 +21,13 @@ The Humanizer skill provides a set of 25 patterns for identifying and rewriting
- **Standard** ([SKILL.md](SKILL.md)): Focuses on "Personality and Soul". Best for blogs, creative writing, and emails.
- **Pro** ([SKILL_PROFESSIONAL.md](SKILL_PROFESSIONAL.md)): Focuses on "Voice and Craft". Best for technical specs, reports, and professional newsletters.

Primary prompt: [SKILL.md](SKILL.md). Supported adapters live in the `adapters/` directory.

## Context

This file serves as the **Agents.md** standard manifest for this repository. It provides guidance for AI agents (like yourself) to understand how to interact with this codebase.

### Repository Structure
### Repository structure

- `src/`
- Modular fragments used to compile the skill files.
Expand All @@ -36,7 +38,7 @@ This file serves as the **Agents.md** standard manifest for this repository. It
- `scripts/`
- Automation for syncing fragments to these files.

### Core Instructions
### Core instructions

You are the Humanizer editor. Follow the canonical rules in `SKILL.md` or `SKILL_PROFESSIONAL.md`.

Expand All @@ -60,4 +62,4 @@ npm run sync

## Interoperability

Check for specialized adapters in the `adapters/` directory for specific tool support (Antigravity, VS Code, Gemini, Qwen, Copilot).
Check for specialized adapters in the `adapters/` directory for specific tool support (Antigravity, VS Code, Gemini, Qwen, Copilot).
45 changes: 20 additions & 25 deletions QWEN.md
Original file line number Diff line number Diff line change
@@ -1,25 +1,11 @@
---
adapter_metadata:
skill_name: humanizer-pro
skill_version: 2.3.0
last_synced: 2026-01-31
skill_version: 2.2.1
last_synced: 2026-02-06
source_path: SKILL_PROFESSIONAL.md
adapter_id: antigravity-skill-pro
adapter_format: Antigravity skill
---
---
name: humanizer-pro
version: 3.0.0
description: |
Professional AI Detection & Humanization.
Context-aware skill that applies specialized modules for Code (MISRA/SonarQube), Academic (Desaire/Citation), and Governance (ISO/NIST).
allowed-tools:
- Read
- Write
- Edit
- Grep
- Glob
- AskUserQuestion
adapter_id: qwen-cli-pro
adapter_format: Qwen CLI context
---

# Humanizer Pro: Context-Aware Analyst (Professional)
Expand Down Expand Up @@ -95,33 +81,42 @@ This module contains the core patterns for identifying AI-generated text in gene
### 18. Curly Quotation Marks
**Problem:** ChatGPT uses curly quotes (“...”) instead of straight quotes ("...").

### 19. Primary Single Quotes (Code-Style Quotation)
**Problem:** AI models trained on code often use single quotes as primary delimiters.

## COMMUNICATION PATTERNS

### 19. Collaborative Communication Artifacts
### 20. Collaborative Communication Artifacts
**Words to watch:** I hope this helps, Of course!, Certainly!, You're absolutely right!, Would you like..., let me know, here is a...

### 20. Knowledge-Cutoff Disclaimers
### 21. Knowledge-Cutoff Disclaimers
**Words to watch:** as of [date], Up to my last training update, While specific details are limited/scarce..., based on available information...

### 21. Sycophantic/Servile Tone
### 22. Sycophantic/Servile Tone
**Problem:** Overly positive, people-pleasing language.

## FILLER AND HEDGING

### 22. Filler Phrases
### 23. Filler Phrases
- "In order to achieve this goal" → "To achieve this"
- "Due to the fact that it was raining" → "Because it was raining"
- "At this point in time" → "Now"
- "In the event that you need help" → "If you need help"
- "The system has the ability to process" → "The system can process"
- "It is important to note that the data shows" → "The data shows"

### 23. Excessive Hedging
### 24. Excessive Hedging
**Problem:** Over-qualifying statements (e.g., "It could potentially possibly be argued").

### 24. Generic Positive Conclusions
### 25. Generic Positive Conclusions
**Problem:** Vague upbeat endings ("The future looks bright", "Exciting times lie ahead").

### 26. AI Signatures in Code
**Words to watch:** `// Generated by`, `Produced by`, `Created with [AI Model]`, `/* AI-generated */`, `// Here is the refactored code:`

### 27. Non-Text AI Patterns (Over-structuring)
**Words to watch:** In summary, Table 1:, Breakdown:, Key takeaways: (when used with mechanical lists)

## INSTRUCTION FOR CORE HUMANIZATION
1. Scan for the patterns above.
2. Rewrite identifying sections to sound natural.
Expand Down Expand Up @@ -270,4 +265,4 @@ This module applies governance frameworks (ISO 42001, NIST AI RMF, EU AI Act) to
* List specific violations found.

## GOAL
Produce text/code that passes linguistic detection, technical verification, and compliance checks.
Produce text/code that passes linguistic detection, technical verification, and compliance checks.
140 changes: 120 additions & 20 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ git clone https://github.com/blader/humanizer.git

## Usage

### Sync & Build (Cross-platform)
### Sync and build (cross-platform)

The repository use a modular fragment system to maintain consistency.

Expand All @@ -21,42 +21,142 @@ The repository use a modular fragment system to maintain consistency.
3. Compile and sync all versions: `npm run sync`
4. Validate metadata: `npm run validate`

This will rebuild `SKILL.md` (Standard) and `SKILL_PROFESSIONAL.md` (Pro) from the `src/` directory and sync them to all 11 adapter files.
This will rebuild `SKILL.md` (Standard) and `SKILL_PROFESSIONAL.md` (Pro) from the `src/` directory and sync them to all adapter files.

### Variants

- **Standard Version (Human):** `/humanizer` (via `SKILL.md`)
- **Professional Version (Pro):** `/humanizer-pro` (via `SKILL_PROFESSIONAL.md`)
- **Standard version (Human):** `/humanizer` (via `SKILL.md`)
- **Professional version (Pro):** `/humanizer-pro` (via `SKILL_PROFESSIONAL.md`)

## Capability Overview
## Capability overview

Detects 25 patterns including inflated symbolism, superficial analyses, vague attributions, and AI-signature comments.

### Key Adapters
### Global agent context

AI agents (Claude Code, Cursor, Windsurf, etc.) should use [AGENTS.md](AGENTS.md) for repository orientation and core instructions.

---

## Adapters (multi-agent)

`SKILL.md` remains the canonical source of truth. These adapters provide thin wrappers for other environments:

- **Agents manifest:** `AGENTS.md`
- **Gemini CLI:** `adapters/gemini-extension/`
- **Google Antigravity (skill):** `adapters/antigravity-skill/`
- **Google Antigravity (rules/workflows):** `adapters/antigravity-rules-workflows/`
- **Qwen CLI:** `adapters/qwen-cli/`
- **GitHub Copilot:** `adapters/copilot/`
- **VS Code:** `adapters/vscode/`
- **Antigravity:** `adapters/antigravity-skill/`

## Version History
### Sync process

- **2.2.0** - Modular refactor, Humanizer Pro, and Node.js build system.
- **2.1.0** - Added Pattern #25 (AI Signatures) and Pattern #26 (Non-text slop).

## Install & validate (Skillshare + AIX)

We provide simple validation steps to help contributors verify SKILL.md changes:
When `SKILL.md` is updated, run the sync script to propagate changes to all adapters:

```bash
# Quick local checks
npm install
npm run sync
# Run the validation script which runs a skillshare dry-run and optional AIX validate
scripts/validate-skill.sh
```

We also run `.github/workflows/skill-distribution.yml` on PRs to validate changes automatically.
This will automatically update version metadata and last synced timestamps across all adapter files.

## 25 patterns detected (with before/after examples)

### Content patterns

| # | Pattern | Before | After |
|---|---------|--------|-------|
| 1 | **Significance inflation** | "marking a pivotal moment in the evolution of..." | "was established in 1989 to collect regional statistics" |
| 2 | **Notability name-dropping** | "cited in NYT, BBC, FT, and The Hindu" | "In a 2024 NYT interview, she argued..." |
| 3 | **Superficial -ing analyses** | "symbolizing... reflecting... showcasing..." | Remove or expand with actual sources |
| 4 | **Promotional language** | "nestled within the breathtaking region" | "is a town in the Gonder region" |
| 5 | **Vague attributions** | "Experts believe it plays a crucial role" | "according to a 2019 survey by..." |
| 6 | **Formulaic challenges** | "Despite challenges... continues to thrive" | Specific facts about actual challenges |

### Language patterns

| # | Pattern | Before | After |
|---|---------|--------|-------|
| 7 | **AI vocabulary** | "Additionally... testament... landscape... showcasing" | "also... remain common" |
| 8 | **Copula avoidance** | "serves as... features... boasts" | "is... has" |
| 9 | **Negative parallelisms** | "It's not just X, it's Y" | State the point directly |
| 10 | **Rule of three** | "innovation, inspiration, and insights" | Use natural number of items |
| 11 | **Elegant variation** | "protagonist... main character... central figure... hero" | "protagonist" (repeat when clearest) |
| 12 | **False ranges** | "from the Big Bang to dark matter" | List topics directly |

### Style patterns

| # | Pattern | Before | After |
|---|---------|--------|-------|
| 13 | **Em dash overuse** | "institutions—not the people—yet this continues—" | Use commas or periods |
| 14 | **Boldface overuse** | "**OKRs**, **KPIs**, **BMC**" | "OKRs, KPIs, BMC" |
| 15 | **Inline-header lists** | "**Performance:** Performance improved" | Convert to prose |
| 16 | **Title case in headings** | "Strategic Negotiations And Partnerships" | "Strategic negotiations and partnerships" |
| 17 | **Emojis** | "🚀 Launch Phase: 💡 Key Insight:" | Remove emojis |
| 18 | **Curly quotation marks** | `said “the project”` | `said "the project"` |
| 19 | **Primary single quotes** | `stated, 'This is a pattern.'` | `stated, "This is a pattern."` |

### Communication patterns

| # | Pattern | Before | After |
|---|---------|--------|-------|
| 20 | **Chatbot artifacts** | "I hope this helps! Let me know if..." | Remove entirely |
| 21 | **Knowledge-cutoff disclaimers** | "While details are limited in available sources..." | Find sources or remove |
| 22 | **Sycophantic tone** | "Great question! You're absolutely right!" | Respond directly |

### Filler and hedging

| # | Pattern | Before | After |
|---|---------|--------|-------|
| 23 | **Filler phrases** | "In order to", "Due to the fact that" | "To", "Because" |
| 24 | **Excessive hedging** | "could potentially possibly" | "may" |
| 25 | **Generic positive conclusions** | "The future looks bright" | Specific plans or facts |

## Full example

**Before (AI-sounding):**
> Great question! Here is an essay on this topic. I hope this helps!
>
> AI-assisted coding serves as an enduring testament to the transformative potential of large language models, marking a pivotal moment in the evolution of software development. In today's rapidly evolving technological landscape, these groundbreaking tools—nestled at the intersection of research and practice—are reshaping how engineers ideate, iterate, and deliver, underscoring their vital role in modern workflows.
>
> At its core, the value proposition is clear: streamlining processes, enhancing collaboration, and fostering alignment. It's not just about autocomplete; it's about unlocking creativity at scale, ensuring that organizations can remain agile while delivering seamless, intuitive, and powerful experiences to users. The tool serves as a catalyst. The assistant functions as a partner. The system stands as a foundation for innovation.
>
> Industry observers have noted that adoption has accelerated from hobbyist experiments to enterprise-wide rollouts, from solo developers to cross-functional teams. The technology has been featured in The New York Times, Wired, and The Verge. Additionally, the ability to generate documentation, tests, and refactors showcases how AI can contribute to better outcomes, highlighting the intricate interplay between automation and human judgment.
>
> - 💡 **Speed:** Code generation is significantly faster, reducing friction and empowering developers.
> - 🚀 **Quality:** Output quality has been enhanced through improved training, contributing to higher standards.
> - ✅ **Adoption:** Usage continues to grow, reflecting broader industry trends.
>
> While specific details are limited based on available information, it could potentially be argued that these tools might have some positive effect. Despite challenges typical of emerging technologies—including hallucinations, bias, and accountability—the ecosystem continues to thrive. In order to fully realize this potential, teams must align with best practices.
>
> In conclusion, the future looks bright. Exciting times lie ahead as we continue this journey toward excellence. Let me know if you’d like me to expand on any section!

**After (Humanized):**
> AI coding assistants speed up some tasks. In a 2024 study by Google, developers using Codex completed simple functions 55% faster than a control group, but showed no improvement on debugging or architectural decisions.
>
> The tools are good at boilerplate: config files, test scaffolding, repetitive refactors. They are bad at knowing when they are wrong. I have mass-accepted suggestions that compiled, passed lint, and still did the wrong thing because I stopped paying attention.
>
> Mira, an engineer at a fintech startup I interviewed, said she uses Copilot "like autocomplete for boring code" but reviews every line before committing. Jake, a senior dev at a larger company, disabled it after it kept suggesting patterns from a deprecated internal library.
>
> The productivity claims are hard to verify. GitHub says Copilot users "accept 30% of suggestions," but acceptance is not correctness, and correctness is not value. The 2024 Uplevel study found no statistically significant difference in pull-request throughput between teams with and without AI assistants.
>
> None of this means the tools are useless. It means they are tools. They do not replace judgment, and they do not eliminate the need for tests. If you do not have tests, you cannot tell whether the suggestion is right.

## References

- [Wikipedia: Signs of AI writing](https://en.wikipedia.org/wiki/Wikipedia:Signs_of_AI_writing) - Primary source
- [WikiProject AI Cleanup](https://en.wikipedia.org/wiki/Wikipedia:WikiProject_AI_Cleanup) - Maintaining organization

## Version history

- **2.2.1** - Added Pattern #19 (Primary Single Quotes), unified Agents.md manifest, and addressed review feedback.
- **2.2.0** - Modular refactor and Humanizer Pro variant.
- **2.1.2** - Fixed YAML description (replaced "excessive conjunctive phrases" with "filler phrases").
- **2.1.1** - Fixed pattern #18 example (curly quotes vs straight quotes).
- **2.1.0** - Added Pattern #25 (AI Signatures) and Pattern #26 (Non-text slop).
- **2.0.0** - Complete rewrite based on raw Wikipedia article content.
- **1.0.0** - Initial release

## License

MIT
MIT
Loading
Loading