Fixing AI Writing at the Blueprint Layer, Not the Thesaurus

The Humanizer Market Chases Its Tail

The commercial AI humanizer industry—Grammarly’s Humanizer, WriteHuman, and the dozens of tools surveyed in recent roundups—operates mostly at the surface layer. Shorter sentences. Fewer em-dashes. Synonym swaps. The objective is to fool detectors like GPTZero by scrambling the statistical residue of training data. It is a cat-and-mouse game played with a thesaurus, and according to the research bundled inside sepia, it is largely futile.

The StoryScope study—Russell et al., 2026, covering 61,608 stories—found that a classifier using narrative-structure features alone detects AI fiction at 93.2% macro-F1. When humanizers edit only surface style, detection drops from 95.5% to 93.9%. The tells that survive are architectural: themes explained by the narrator rather than dramatized, causally tidy single-track plots, emotions rendered only as bodily sensation, a lack of real-world references, linear time, and endings resolved by protagonist growth and acceptance. You can swap “fundamentally transformed” for “changed” all day; the blueprint still screams LLM.

Editing the Blueprint

Sepia is built as a corrective to this misunderstanding. It is not a web app or a SaaS dashboard. It is an Agent Skill—a folder containing a canonical SKILL.md and reference files—designed to plug into Claude Code, Codex, Grok Build, and Antigravity. The skill performs four operations: write, review (diagnose only), refactor (minimal edits), and recreate (full rewrite). But its real work happens in three passes that target the layers where AI actually leaves fingerprints.

Pass one attacks narrative architecture. The skill instructs the agent to stop explaining the theme, loosen causal chains, back-load revelations, mix emotion modes, build sparse character networks, and name real things. Pass two addresses discourse flow: de-templating the paragraph-question sequence, fixing mid-story sag, varying rhythm and positions. Only pass three touches surface style—clichés, syntax templates, vocabulary, register—the layer where every commercial humanizer begins and ends.

For professional prose, the diagnosis is different. Release notes, PR replies, postmortems, tickets, and technical articles fail through filler that carries no information, hedging where judgment was needed, chatbot leftovers, and register that ignores the venue. Sepia applies a shared “slop” checklist and then thin domain-specific rule files: release notes must lead with user impact and artifact per claim; PR replies must answer first, cite file:line, and avoid reflex praise; postmortems must be blameless toward people and merciless toward mechanisms. The skill knows that a ticket title should describe an outcome, not a task, and that technical articles need one real dead end and one committed opinion.

The Skill Ecosystem Arrives

What makes sepia portable—and why its timing matters—is the Agent Skills format. Originally developed by Anthropic and released as an open standard, a skill is simply a folder with a SKILL.md file and optional resources. Agents load them through progressive disclosure: discovery at startup, full instructions only when the task matches. This keeps the context window light and the expertise on-demand.

The format is now quietly being adopted across the industry. OpenAI has added skills support to ChatGPT’s Code Interpreter and the Codex CLI, using a folder structure that looks, as Simon Willison noted, “very similar to Anthropic’s implementation.” Sepia ships one canonical SKILL.md with no per-platform forks. It runs inside Claude’s plugin marketplace, Codex’s plugin system, Grok Build’s installer, or a manual path for Antigravity. The same research-backed instructions run everywhere.

This is the genuinely special part: sepia is not a product locked to a single model or a proprietary API. It is domain expertise packaged as infrastructure. As the agent ecosystem moves from monolithic prompts to composable skills, sepia offers a template for how specialized knowledge—literary theory, software communication norms, empirical detection research—can travel with the user across tools.

Calibrate to Humans, Don’t Invert the AI

The governing principle inside sepia’s SKILL.md is worth pausing over: “calibrate to the human distribution, don’t invert the AI one.” Humans sit at moderate values. A story that applies every anti-AI rule simultaneously becomes a new fingerprint, just as rigid and detectable as the original machine output. So the skill selects three to five moves per story and leaves slack. It is a light touch, not a total rewrite.

This restraint separates sepia from the “re-humanize” button crowd. Tools like those surveyed in recent roundups promise to “beat GPTZero” through aggressive rewriting that often flattens voice and meaning. Sepia’s approach is closer to a developmental edit than a laundering service. It assumes the user wants to write well, not merely to evade detection.

Rough Edges and Open Questions

The project is young—version 0.2.0 for manual installs—and the ecosystem it depends on is still stabilizing. Agent Skills are gaining traction, but support varies: Claude Code and Codex have marketplace installers; Antigravity requires a manual install that clones a pinned release and aborts if paths already exist. The update story for Antigravity is entirely manual. These are not flaws so much as signs that the tooling around portable skills is still immature.

There is also the question of how well a skill can enforce structural changes when the underlying agent is itself an LLM with its own architectural biases. If Claude or GPT-5.2 tends toward tidy causality and explicit theme statements, a SKILL.md file is a suggestion, not a sandbox. The per-model fingerprint corrections (for Claude, GPT, Gemini, DeepSeek, and Kimi) acknowledge this, but they are corrections, not guarantees.

The Outlook

Sepia arrives at a hinge moment. The AI writing landscape is bifurcating: one path leads toward ever-more-sophisticated slop generators and the humanizers that chase them; the other leads toward agents that carry genuine domain expertise and apply it with precision. By grounding its protocol in peer-reviewed studies and packaging it as a cross-platform skill, sepia makes a bet that the second path is more durable.

If the Agent Skills standard continues its current trajectory—from Anthropic’s Claude to OpenAI’s Codex and ChatGPT—portable expertise like sepia could become the normal way users augment their agents. The repository is small, the code is nonexistent, and the value lives entirely in the research digests and the calibration rules. That is a strange kind of open-source project: not a library, but a lens. It does not run; it instructs. And in an ecosystem drowning in generated text, a well-instructed agent may be more valuable than a faster one.