What Are the Content Patterns (1-6) in Humanizer? A Complete Guide

Humanizer defines six content patterns (I‑1 through I‑6) under its "Rhythm by rule" section to identify mechanical writing habits, with I‑6 specifically targeting forced triads—superficial three-part groupings that add no meaningful distinction.

The Humanizer skill, developed by blader/humanizer, provides a structured framework for detecting and correcting robotic prose patterns. According to the SKILL.md source file, these patterns help editors recognize when text follows formulaic structures rather than serving genuine communicative purposes.

Understanding the Six Content Patterns in Humanizer

Humanizer organizes its content patterns into a numbered system prefixed with I‑ (indicating "Issues"). While the source analysis focuses on I‑6 Forced triads, the complete set spans I‑1 through I‑6 under the "Rhythm by rule" classification in SKILL.md lines 39–45【SKILL.md†L39-L45】.

The Pattern Structure

Each pattern follows a consistent definition format:

• Pattern name — a descriptive label for the mechanical habit
• Detection criteria — what triggers the pattern match
• Classification — whether the pattern is a "weak‑alone" tell or requires combination with other signals
• Recommended fixes — specific editorial actions to resolve the issue

I‑6 Forced Triads: Pattern Details

The I‑6 pattern represents the sixth and final content pattern in the Rhythm by rule category. It specifically identifies instances where authors group ideas in threes primarily for rhythmic completion rather than substantive distinction【SKILL.md†L41-L45】.

Detection Criteria for Forced Triads

Humanizer flags forced triads when it encounters:

• Single-sentence noun lists — three parallel terms conveying similar concepts (e.g., "innovation, inspiration, and insights")
• Redundant parallel examples — three illustrations that restate an identical point
• Non-contributing third items — two meaningful facts paired with a third that adds no new information before a concluding statement

Editorial Classification

Forced triads receive the weak‑alone designation. This means the pattern is not inherently problematic—triads are acceptable when the three items genuinely advance meaning. However, purely rhythmic triads should be removed or restructured.

Recommended Fixes

When Humanizer identifies a forced triad, editors should:

1. Merge redundant items — combine overlapping concepts into a single, stronger statement
2. Expand the strongest idea — develop one substantial point rather than three thin ones
3. Vary sentence structure — break the three-part rhythm entirely with different syntactic patterns

Code Examples: Correcting Forced Triads

Example 1: Single-Sentence Noun Triad

**Before**  
The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights.

**After**  
The event includes talks and panels, plus time for informal networking between sessions.

The original contains two consecutive triads. The revision collapses these into specific, non-enumerated details.

Example 2: Paragraph-Scale Structural Triad

**Before**  
A career can look promising and fail. A relationship can feel important and end. A skill can take years and remain useless. These decisions rarely explain themselves.

**After**  
A career can look promising and fail. So can a relationship that felt important and ended, or a skill that took years and remained useless. These decisions rarely explain themselves.

Here the three parallel sentences are restructured using subordination, eliminating the mechanical rhythm while preserving all substantive content.

Key Source Files in Humanizer

Understanding these patterns requires reference to the canonical source files in the blader/humanizer repository:

File	Purpose
SKILL.md	Definitive pattern reference including I‑1 through I‑6 definitions and remediation guidance
README.md	Skill overview with pattern category explanations
AGENTS.md	Configuration specifications for deploying Humanizer in editorial workflows

All pattern definitions, detection logic, and fix recommendations originate in SKILL.md【SKILL.md†L39-L45】.

Summary

• Humanizer defines six content patterns (I‑1 to I‑6) under the "Rhythm by rule" section in SKILL.md
• I‑6 Forced triads specifically targets superficial three-part groupings that serve rhythm over meaning
• Patterns classify issues as weak‑alone (flagged individually) versus combined signals
• Correction strategies include merging items, expanding substance, or structural variation
• Source authority resides in SKILL.md lines 39–45 with full documentation in the blader/humanizer repository

Frequently Asked Questions

What are all six content patterns in Humanizer?

The complete I‑1 through I‑6 patterns are documented in SKILL.md under "Rhythm by rule." While the source analysis confirms I‑6 as "Forced triads," the full sequence requires direct reference to SKILL.md lines 39–45 for patterns I‑1 through I‑5. The repository does not publish a standalone summary outside this file.

How does Humanizer decide when a triad is "forced" versus legitimate?

Humanizer applies the weak‑alone standard: triads are acceptable when three items convey genuinely distinct information. The pattern triggers when items are semantically redundant, rhythmically determined, or when the third element adds no substantive meaning beyond completing the three-part structure【SKILL.md†L41-L45】.

Can I use Humanizer patterns in automated editing workflows?

Yes. The AGENTS.md file contains configuration specifications for integrating Humanizer detection into agent-based editorial systems. Patterns like I‑6 can be programmatically flagged with corresponding fix suggestions for human or automated review.

Where can I find the complete pattern definitions?

All authoritative definitions reside in the SKILL.md file at the root of blader/humanizer. This file contains the canonical descriptions, detection criteria, and remediation instructions for patterns I‑1 through I‑6, with line references 39–45 covering the content pattern section specifically.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}