Structural Humanizer logo

Structural Humanizer

Community
NulightJens
structural-humanizer

Remove the discourse-level (structural) signs of AI writing that survive surface editing: stated lessons and moral-of-the-story closers, tidy single-track arcs, embodied-emotion performance ("chest tightened"), vague allusions instead of named references, unbroken linear structure, and shape convergence across pieces. Grounded in the StoryScope study (Russell et al. 2026): narrative structure alone detects AI text at 93.2% F1, and professional stylistic rewriting moved detection only 1.6 points. Use as the SECOND pass after the humanizer skill (which handles words and phrasing) whenever writing or revising LinkedIn posts, course lessons, blog posts, essays, newsletters, or emails that must read as human. Triggers: "humanize", "de-slop", "AI tells", "make this sound human", "structural pass", "deep humanize".

Overview

PublisherNulightJens
Repositoryhumanizer-stack
Skill namestructural-humanizer
Stars
370
Forks
28
Bundled files
3
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by NulightJens on GitHub. Read the source before you install it.

Installation

Install the Structural Humanizer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/NulightJens/humanizer-stack/tree/main/skills/structural-humanizer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/NulightJens/humanizer-stack.git /tmp/humanizer-stack
mkdir -p .claude/skills
cp -r /tmp/humanizer-stack/skills/structural-humanizer .claude/skills/structural-humanizer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Structural Humanizer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Structural Humanizer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Structural Humanizer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

structural-humanizer

Read this first. The humanizer skill fixes words: "delve", em dashes, rule of three, negative parallelism. This skill fixes what survives that pass: the structure. The two are different jobs, run in sequence. Surface pass first, structural pass second.

Why this layer matters more. StoryScope (Russell et al. 2026, arXiv:2604.03136) classified 61,608 stories from humans and 5 LLMs using only discourse-level features, with all style features withheld: 93.2% detection accuracy. Then they ran AI text through LAMP, a professional span-level rewriting framework that removes cliche, purple prose, and redundant exposition (functionally, a surface humanizer). Detection dropped 1.6 points. Meanwhile the surface layer is decaying on its own: GPT 5.4 already slashed em-dash usage, and fine-tuning drops stylistic detection from 97% to 3%. The durable fingerprint is structural, and fixing it requires structural rewrites, not word swaps. Full findings with numbers: references/storyscope-findings.md.

The trap (same trap as unslop-ui)

Do not replace one default with another. If every piece now opens mid-scene, names three feelings, and ends unresolved, that is a new detectable cluster. The study's deepest finding is convergence: all five AI models occupy one tight region of structural space while humans are dispersed and rare. Rarity IS the human signal.

So: pick 1-2 structural interventions per piece, vary them across pieces, and be able to say why this piece got this shape. Never apply the whole menu at once.

The six audits

Run these one at a time (aspect-based checking found 95% of issues in the study's own pipeline vs 68% for one mega-pass). Numbers are human vs AI rates from the study.

1. Theme explicitness (the biggest tell)

AI states its lesson. Narrator explains the theme 77% of the time vs 52% for humans; themes are moralized ~20% harder; everything ties back to one central point. In content: the takeaway sentence, "What this means for you", the thesis restated at every section end, every example dutifully interpreted. Fix: state the point once, where it lands hardest. Cut every restatement. Let at least one example sit uninterpreted. Trust the reader.

2. Structural tidiness

AI writes single-track: unbroken causal chain, no subplots (79% vs 57%), everything resolved, protagonist-choice endings. Humans digress, loop, and leave threads open (thematically parallel tangents: 42% vs 21%; ambivalent endings far more common). Fix options: one tangent that only obliquely relates; one question raised and explicitly not answered; stop before the resolution.

3. Emotion mode (inverts "show don't tell")

The single largest gap in the study: AI performs emotion through the body and atmosphere 81% of the time vs 38% for humans ("chest tightened", "breath caught", "the lamplight dimmed"). Humans just name it: explicit emotion labels 29% vs 8%. Fix: say the feeling plainly ("honestly, it scared me", "I was pissed"). Reserve embodied detail for the one moment that earns it. Yes, this contradicts classic writing advice. Classic writing advice is now a machine signature.

4. Reference specificity

Humans name real things: specific texts, people, brands, places, prices (explicit named references 47% vs 24%). AI stays at vague allusion (72% vs 50%) and avoids naming real brands or works. Fix: "a popular productivity book" becomes "Deep Work". "An expert" gets a name. "Recently" gets a date. Add the price, the version number, the city.

5. Reader engagement

Humans acknowledge the reader (direct address 28% vs 7%; fourth-wall permeability 67% vs 39%). "AI writes as though no one is watching." Content marketing already uses "you" constantly, so the transferable move is acknowledging the writing itself: "I know how this sounds", "skip this section if you already run ads", "you're probably skimming, so here's the number". Use sparingly; it is a spice.

6. Shape convergence

Does this piece have the same skeleton as your last three? Same opener type, same arc, same closer? That is the cluster forming. Compare against recent pieces and break the pattern before publishing.

Workflow

  1. Extract the skeleton first. Outline the piece: beats in order, where the lesson is stated (and how many times), time structure (linear or not), what gets resolved, tangent count, emotion moments and their mode, named vs vague references. Audit the outline, not the prose. (This is the study's own method: structural tells hide from prose-level reading.)
  2. Run the six audits against the skeleton, one at a time.
  3. Choose 1-2 interventions from the menu below. Deliberate, genre-appropriate (see references/genre-calibration.md), different from the last piece.
  4. Rewrite structurally. Move sections, cut codas, delete restatements. Do not just polish sentences; that is the other skill's job.
  5. Scan: python3 scripts/structural_scan.py <file> catches the pattern-matchable slice (embodied-emotion cliches, takeaway markers, vague allusions, uniformity).
  6. Re-check for the trap. If the fix looks like the fix you applied yesterday, vary it.

Intervention menu (rotate, never all at once)

  • Outcome first. Open at the end state, then rewind. Payoff lands mid-piece, not in the close.
  • Cold open mid-scene. Start inside the story, loop back for context later.
  • Delayed reveal. Withhold the number/name/result the piece is built on until two-thirds through.
  • Recontextualization callback. Make an earlier detail mean something new: "Remember the $80/month from the top? That was the cheap part."
  • The oblique tangent. One paragraph that parallels the theme without serving it. Do not tie it back explicitly.
  • The open thread. Name a question you cannot answer yet and leave it standing.
  • Genuine ambivalence. End with both feelings intact instead of a resolved lesson.
  • The named thing. Swap every vague allusion for a real, checkable specific.
  • Plain emotion. Replace body-performance with the stated feeling.
  • Acknowledged reader. One moment that admits someone is reading this.
  • End hot. Stop at the spike instead of the quiet coda (see Claude fingerprint).

Model fingerprints (know what drafted the text)

Most drafts here come from Claude, whose fingerprint is the most distinctive of all five models. If the draft is Claude: flat event escalation (uniform intensity throughout; fix by varying stakes and energy across the piece), the epilogue habit (a wrap-up coda after the natural ending; cut it and end earlier), reverent, quiet endings (occasionally end on the spike or unresolved). GPT drafts over-index on distant retrospective framing ("years later, I realize") and social/gossip mechanics. Gemini produces the tidiest endings; kill the bow on top.

What this skill does not do

It does not fix vocabulary or punctuation (run humanizer). It does not impose a voice (that is jens-blog-writer / solo-scale-writer / the Nick Saraev templates). It does not make text undetectable; nothing does. And one honest caveat: StoryScope studied ~5,000-word fiction. The transfer to short nonfiction is an inference, but the core pattern (over-explanation, tidiness, linearity, convergence to one default shape) is exactly what independent analyses of nonfiction AI slop keep finding, and the short-text subset that transfers cleanly is audits 1, 3, 4, and 6.

References

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Structural Humanizer AI skill do?

Remove the discourse-level (structural) signs of AI writing that survive surface editing: stated lessons and moral-of-the-story closers, tidy single-track arcs, embodied-emotion performance ("chest tightened"), vague allusions instead of named references, unbroken linear structure, and shape convergence across pieces. Grounded in the StoryScope study (Russell et al. 2026): narrative structure alone detects AI text at 93.2% F1, and professional stylistic rewriting moved detection only 1.6 points. Use as the SECOND pass after the humanizer skill (which handles words and phrasing) whenever wri...

Why use Structural Humanizer on TypingMind?

Because you install it once and use it with any model. Structural Humanizer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Structural Humanizer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/NulightJens/humanizer-stack/tree/main/skills/structural-humanizer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Structural Humanizer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Structural Humanizer?

As many as you like. As long as a model supports skills, you can use Structural Humanizer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Structural Humanizer AI skill free?

It is published on GitHub by NulightJens. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇